Myndo

Myndo AI Privacy Policy

Last Updated: September 18, 2026

Our Privacy Commitment

Myndo is designed with privacy as a core principle. We believe your data should stay private, under your full control, and portable. Your content does not go to our servers for storage. Clips and chat content are either stored locally in your browser or sent directly from the extension to your Google Drive. We designed Myndo to use the most limited permissions possible, and we only access content when you explicitly ask us to.

Scope

This policy applies to the Myndo browser extension and the myndoai.com pages that link to it. Third-party services you use with Myndo (such as Google) have their own privacy policies.

What We DON'T Collect

We never collect or store:

  • Your browsing history or websites you visit.
  • Your passwords or Google credentials (OAuth means we never see them).
  • Your chat content or clipped content on our servers.
  • Your document text or file contents on our servers.
  • Cross-site tracking data, cookies, ad identifiers, or fingerprinting data.

What We Do Collect

1) Authentication Information (Account Access Only)

Why: To keep you securely authenticated and ensure a consistent sign-in experience.

What we collect:

  • Google account identifier ("sub" / user ID).
  • Session tokens (encrypted locally in your browser).
  • Device identifier (random UUID stored locally).

What we do not store:

  • Your email address, name, or profile photo.

Note: During Google sign-in, Google may display or provide basic profile information (like name, email, and profile photo). Myndo does not store that information on our servers.

Where it's stored:

  • In your browser: encrypted session tokens and device identifier.
  • On our backend: minimal session/auth data required to keep you signed in (including only the Google "sub" identifier).

2) File Structure Metadata (IDs Only)

Why: To display your projects and notebooks in the extension UI using anonymous IDs.

What we collect (IDs only):

  • File IDs created by Myndo (Google's anonymous identifiers).
  • Folder relationships (e.g., which notebook belongs to which project).

Where it's stored:

  • File IDs and relationships: backend cache to sync across devices.
  • File names: used locally and via Google APIs for display, not stored on our servers.

3) Minimal Usage Telemetry (No Content)

Why: To identify reliability issues across browsers and platforms.

What we collect:

  • Action events like "login succeeded," "notebook creation failed," or "clip saved."
  • Basic error metadata (e.g., status codes) to improve reliability.

4) Saved Content (Local, or Direct to Storage You Own)

Why: To let you save and use content with your AI workflows.

What happens:

  • When you click Quick Clip, the extension reads the visible text on the page and stores it locally.
  • When you click Save to Memory, the content is sent directly from your browser to the destination you chose - your Google Drive, or a GitHub repository you selected - and may also be kept locally for the current session.
  • If you have connected an AI app as a save destination, the content is sent from your browser to that app.
  • In every case the content goes from your browser to the destination. It does not pass through, and is not stored on, Myndo's servers.

Optional Integrations You Set Up

These are off unless you turn them on. Myndo does not collect or store anything described in this section: credentials stay in your browser, and content goes straight to the service you chose.

GitHub storage. You can store notebooks in a GitHub repository instead of, or alongside, Google Drive. You supply a Personal Access Token you create and one repository you choose. Myndo writes your clips there and does not access any other repository. The token is encrypted in your browser's local storage, sent only to api.github.com, and never to our servers.

AI tools. You can run optional AI actions on a clip, such as summarizing it or pulling out key facts. You supply your own API key for a provider you already use (Google AI Studio, OpenRouter, Groq, OpenAI or Anthropic). The clip goes from your browser directly to that provider using your key, so it does not pass through our servers and we never receive or store it. Your key is encrypted locally and sent only to that provider. Without a key, Myndo sends nothing to any AI provider.

Saving into AI apps. Where you have connected one, Myndo can send a clip into an AI app such as ChatGPT or Perplexity. The clip goes from your browser to that app and is then covered by that app's privacy policy.

How We Use Your Information

✅ What We Do

  • Authenticate you with Google OAuth.
  • Save your clips directly to your Google Drive.
  • Store minimal local state to make the extension work.
  • Use minimal, non-content telemetry to improve reliability.

❌ What We Never Do

  • Sell data or share it with advertisers.
  • Track you across websites.
  • Read content without a user action.
  • Store your clips or document text on our servers.

Where Your Data Lives

Data TypeYour BrowserOur BackendYour Drive / GitHub
GitHub access token✅ Encrypted, local only❌ Never❌ No
AI provider API key✅ Encrypted, local only❌ Never❌ No
Clip content✅ Local only❌ Never✅ Yes (when saved)
File names✅ Local display❌ Never✅ Yes (Google stores)
File IDs (anonymous)✅ Yes✅ Yes (sync only)✅ Yes (Google assigns)
Session tokens✅ Encrypted✅ Yes (auth only)❌ No
Google account identifier ("sub")❌ No✅ Yes (sign-in only)✅ Yes (Google owns)

Sharing & Service Providers (No Advertising)

We do not sell your data and we do not share it with advertisers. We may use service providers to operate Myndo (for example, database hosting, authentication/session infrastructure, and basic error monitoring). These providers process limited data on our behalf only as needed to run the service. We do not send or store your clipped content or document contents on our servers.

Why We Need Permissions

We only request permissions required to make Myndo work.

Required Permissions

`activeTab`

  • We can only read the current tab when you click Save/Clip.
  • We cannot access your other tabs or your browsing history.

`storage`

  • Stores local settings, session tokens, and local Quick Clips in your browser.
  • We do not access other browser storage.

`identity`

  • Enables Google OAuth sign-in. We never see your password.

`scripting`

  • Injects the clipping UI only when you use Myndo.

`alarms`

  • Runs background maintenance tasks required for stability.

`unlimitedStorage`

  • Prevents local storage limits from breaking your saved data.

Google Drive Scope (Most Limited)

`https://www.googleapis.com/auth/drive.file`

  • We can only access files Myndo creates in your Drive.
  • We cannot see or access the rest of your Drive files.

Optional Permissions (Require Your Approval)

Access to AI tool websites (ChatGPT, Claude, Gemini, Perplexity, Grok, NotebookLM)

  • Only requested if you enable integrations.
  • Used to inject the Myndo widget button on those sites.
  • We do not read chats without you clicking Save/Clip, and content is handled the same way as described above (local, or direct to storage you own).
  • If you use an AI app as a save destination, this permission also lets Myndo send the clip to that app when you ask it to.

Access to AI provider APIs (Google AI Studio, OpenRouter, Groq, OpenAI, Anthropic)

  • Only requested if you enable the optional AI tools and add your own API key.
  • Used solely to send your request directly to the provider you configured.
  • Never requested, and never used, if you do not enable AI tools.

Access to GitHub (api.github.com)

  • Only requested if you choose GitHub as a storage destination.
  • Limited to the single repository you selected, as described above.

Legal Basis for Processing

Where applicable (for example, for users in the European Union, United Kingdom, or other jurisdictions with similar laws), we process the limited data described in this policy based on one or more of the following:

  • Providing the service you request: sign-in, syncing IDs, and saving content to your Drive.
  • Your consent: where you enable optional features or integrations.
  • Legitimate interests: to keep Myndo reliable and secure (for example, basic non-content error reporting).
  • Legal obligations: where required by law.

Your Privacy Rights

Depending on where you live, you may have rights related to personal data, including the right to request access, correction, deletion, or to object to certain processing.

Because Myndo does not store your clipped content on our servers, you control most of your data directly:

  • You can delete saved content in your Google Drive at any time.
  • You can clear local extension storage by clearing extension data or uninstalling the extension.

If you want help with account/session deletion or have a privacy request, contact us at support@myndoai.com.

International Data Transfers

The limited data we process (for example, authentication/session data and non-content operational metadata) may be processed or stored in the United States or other jurisdictions. These locations may have different data protection laws than your country.

Children's Privacy

Myndo is not intended for children under 13, and we do not knowingly collect personal data from children under 13. If you believe a child has provided personal data to us, contact support@myndoai.com and we will take steps to delete it.

No AI Training

We do not use your clipped content, chat content, or Google Drive files created through Myndo to train AI or machine-learning models.

Chrome Web Store / Platform Compliance

We follow Chrome Web Store and browser extension platform user-data rules. We request only the permissions needed to provide Myndo's features, and we use data only as described in this policy.

Data Retention & Deletion

  • Local Quick Clips remain in your browser until you clear extension data or uninstall the extension.
  • If you uninstall Myndo, Chrome removes all extension storage automatically.
  • Your Google Drive files remain yours unless you delete them.

Security

We use reasonable, industry-standard measures designed to protect the limited data we process.

Third-Party Services

Google Services (Required)

Myndo Backend (Required)

  • Used only for session management, file ID sync, and minimal telemetry.

Optional Integrations

If you enable GitHub storage, AI tools, or saving into an AI app, your data is handled by that service under its own terms. See "Optional Integrations You Set Up" above.

Contact Us

For questions about this policy or our data practices: support@myndoai.com