Privacy Policy

This Privacy Policy explains how the N6 Chrome Extension accesses, stores, and uses information when you use the extension together with N6, X, LinkedIn, supported web forms, and other supported browser pages.

The extension may run content scripts on supported N6 surfaces, supported third-party pages, supported forms, and broad http/https pages so it can detect connection state, page structure, form fields, or supported assistant contexts. Detection does not mean the extension uploads full page content by default.

The extension may also execute packaged extension scripts on supported pages when needed to complete a supported workflow, such as collecting a limited LinkedIn profile DOM snapshot as a fallback for user-initiated sync, interacting with page-native form behavior after you trigger Form Assistant actions, or marking already open N6 pages after install or update so those pages can detect extension state. These scripts are bundled with the extension and are not remotely hosted code.

Depending on the feature you choose to use, the extension may access your N6, X, or LinkedIn sign-in state, selected profile information, posts, connections, following or similar social data that you choose to sync, and the limited page context needed to complete the workflow you request.

For Form Assistant workflows, the extension may access structured fields, page URL and title, questions, answers, and, when needed, a sanitized page snapshot after you trigger analysis, generation, regeneration, fill, or save actions.

For Social Reply workflows, the extension may process post content, author information, platform information, reply style, generated replies, and replies you fill or save to generate suggestions and maintain related DataHub history.

The extension may also store local settings, sync progress or checkpoints, cached identifiers, monitoring status, limited auth helper state, Form Assistant analysis sessions, selected answers, Social Reply state, page metadata, and related operational metadata in your browser so your workflow can continue across sessions.

We use accessed information only to provide the extension features that you request, such as connecting your own accounts, syncing selected social data into N6, analyzing forms, mapping fields, generating AI-assisted answers or replies, and showing related status inside the extension.

Where a supported workflow requires it, we may execute packaged scripts on supported pages to capture a limited LinkedIn profile DOM snapshot for a sync request you start, dispatch page-level form events after your requested field binding or fill action, or write a stateless install or update marker on already open N6 pages so those pages can recognize the extension state.

After you bind and sync a supported X account, N6 may enable background monitoring for that account to check for new posts and maintain monitoring state. You can disable background monitoring from the extension UI at any time.

Some information is stored locally in your browser, including feature settings, sync checkpoints, cached identifiers, monitoring preferences, Form Assistant sessions, Social Reply state, selected candidates or answers, page metadata, and related feature state.

Some information is sent to N6 services when you trigger sync, analysis, generation, regeneration, fill, save, upload, reply assistance, or other assisted workflows. For example, selected profile, post, connection, or similar account data may be sent to complete a sync request; structured form fields or a sanitized page snapshot may be sent to analyze forms or generate answers; and Social Reply content may be sent to generate replies or save related DataHub history.

The extension may use Chrome cookie access to detect whether you are signed in to N6, X, or LinkedIn in the current browser profile, and to read the session data needed to connect the account that you choose to use on this browser.

For certain connection workflows, the extension may temporarily construct request headers or store limited auth helper state locally so the selected account can be connected or synced. We do not access cookies for advertising purposes, and we do not sell cookie-derived data to third parties.

Background monitoring is currently limited to supported X workflows inside the extension. After you bind and sync a supported X account, N6 may enable monitoring for that account so related features can check for new posts and keep monitoring state current.

When background monitoring is on, the extension may use background tasks to check for new posts and record monitoring state. You can disable background monitoring at any time from the extension UI.

We may process filtered diagnostic or error information, such as request identifiers, status information, or extension runtime context, to maintain the reliability and security of the extension.

Where monitoring tools are enabled, we make reasonable efforts to redact or filter cookies, authorization headers, full page content, and personal identifiers before data is sent to external monitoring systems. We do not use extension data for advertising and we do not sell extension data to third parties.

Local extension data remains in your browser until you clear it, disconnect accounts, disable a feature, or uninstall the extension, unless the data is rotated, expired, replaced, or overwritten earlier by product logic.

You can manage connected accounts, disable automatic sync, disable background monitoring, clear local browser data, or uninstall the extension at any time. The full public policy remains available from the public policy page.

If you have questions about this Privacy Policy or the N6 Chrome Extension, please contact privacy@n6.network or the support channel listed in the Chrome Web Store listing or on the N6 website.

If your request concerns a specific connection, sync, or form-analysis workflow, please include enough detail to help us identify the relevant account or feature.