Privacy Policy

How Flywheel handles extension and workspace data

This policy explains how Flywheel handles data for the OPC Marketing — Cookie Import development extension, the Flywheel Assistant extension, and related Flywheel workspace services. It is written for Chrome Web Store review and for users who want to understand what data is used and why.

Effective date
June 16, 2026
Chrome extension
OPC Marketing — Cookie Import / Flywheel Assistant
Contact
support@mktflywheel.ai

Single purpose

The extension has one purpose: helping a signed-in Flywheel user connect supported social channels to a Flywheel workspace so publishing credentials can be created, refreshed, and checked.

  • The extension does not provide unrelated browsing tools, advertising features, or general web tracking.
  • The extension acts only after the user opens the side panel and chooses to connect, import, refresh, or disconnect a channel.

Data we collect

Depending on the user's action, Flywheel may process workspace identifiers, connection status, account display names returned by supported platforms, and authentication information needed to connect a channel.

  • Authentication information may include supported platform session cookies when the user explicitly imports or refreshes a channel connection.
  • Extension storage may contain non-sensitive state such as backend URL, workspace ID, workspace display name, locale, and recent connection status.
  • We do not intentionally collect health information, financial payment information, personal communications, precise location, browsing history, keystrokes, mouse movement, or unrelated website content through this extension.

How cookies are used

The extension requests the Chrome cookies permission so it can read only the required session cookies for supported platforms after explicit user action.

  • Cookies are used to create or refresh publishing credentials in the user's Flywheel workspace.
  • Raw platform cookies are not stored in Chrome extension storage.
  • Cookies are not used for advertising, user profiling, or selling user data.

How extension storage is used

Chrome extension storage is used to keep the connector experience reliable between sessions without storing raw platform credentials.

  • Stored values may include workspace ID, workspace name, backend URL, locale, and recent connection state.
  • Users can disconnect the workspace from the extension UI, which clears the extension's local workspace connection state.

Sharing and transfer

Flywheel does not sell user data. Data is transferred only as needed to provide the extension's single purpose and operate the user's Flywheel workspace.

  • Channel connection data is sent to Flywheel APIs controlled by the user's workspace session.
  • We do not transfer user data to third parties for advertising, creditworthiness, lending, or unrelated purposes.
  • We may use infrastructure providers to host and secure Flywheel services, subject to confidentiality and security obligations.

Retention

Flywheel keeps channel connection records only for as long as needed to operate the user's workspace and provide publishing workflows.

  • Users can disconnect a channel or workspace to stop using the associated credential.
  • Workspace records may be retained when required for security, audit, abuse prevention, or legal obligations.

Security

Flywheel limits credential handling to the connection workflow and applies access controls around workspace-scoped APIs.

  • The extension does not execute remote JavaScript or WebAssembly code.
  • Network requests are limited to Flywheel APIs and supported platform connection workflows.

User choices

Users control when the extension connects, imports, refreshes, or disconnects social channel credentials.

  • You can choose not to import a channel connection.
  • You can disconnect a platform binding or clear the extension's workspace connection state.
  • You can uninstall the Chrome extension at any time from Chrome's extension management page.

Changes to this policy

We may update this policy when Flywheel or the extension changes. The effective date above reflects the latest version.

  • Material changes will be reflected on this page.
  • Continued use of the extension after an update means the updated policy applies.
Privacy Policy | Flywheel