Lynx AI

Privacy Policy

Last updated: June 13, 2026

This Privacy Policy explains how Lynx AI handles information across the website, desktop app, cloud services, connected integrations, and support experiences.

Product Scope

This Privacy Policy applies to Lynx AI websites, the Lynx desktop app, Lynx cloud services, connected integrations, billing, support, and related product experiences.

Lynx AI helps you see, understand, and act inside software using local app context, integrations you connect, and AI model providers you choose or use through Lynx.

Lynx Helper Chrome extension privacy details are covered in the Lynx Helper Extension Privacy Policy.

Information We Collect

  • Account information, such as your name, email address, workspace details, authentication identifiers, billing status, and support communications.
  • Product configuration, such as app settings, connected accounts, permissions, model preferences, automation settings, and integration choices.
  • Task content you provide or authorize Lynx to use, such as prompts, messages, files, screenshots, recordings, software context, browser context, calendar content, email content, Drive file data, Docs content, Sheets content, and outputs generated during a task.
  • Device and usage data, such as app version, operating system, diagnostics, crash reports, logs, feature usage, performance data, security events, and approximate region inferred from network or account context.
  • Payment and subscription data processed by our payment providers, such as plan, invoice, payment status, and limited billing identifiers.

Google Workspace And Gmail Data

When you choose to connect a Google account, Lynx uses OAuth through self-hosted Nango to request only the Google scopes shown on the consent screen. You can choose not to connect Google, disconnect Google from Lynx, or revoke Lynx access from your Google Account settings.

Depending on the Google features you enable and the scopes you approve, Lynx may process Google account profile information, Gmail messages and mailbox state, Calendar calendars and events, Drive file metadata and file content, Google Docs content, and Google Sheets spreadsheet data.

Lynx uses Google user data only to provide user-facing features you request, such as searching, reading, summarizing, drafting, sending, labeling, archiving, creating, editing, organizing, or automating Gmail, Calendar, Drive, Docs, and Sheets workflows.

OAuth access tokens and refresh tokens for Google integrations are stored by Nango. The Lynx desktop app stores only local connection metadata such as connection ID, provider key, account label, approved scopes, status, and timestamps unless a feature you use stores task history or user-authorized task content.

When you ask Lynx to use AI features with Google data, selected task content may be processed by Lynx AI services or model providers you select or configure only to complete the user-requested task. Google Workspace API data is not used to train generalized AI or machine learning models.

Google API Limited Use

Lynx's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google Workspace API data is not sold, used for personalized advertising, transferred to data brokers, used to determine creditworthiness or lending eligibility, or used for purposes unrelated to the user-facing Lynx features you request.

We do not allow humans to read Google Workspace API data unless you ask for support and give permission, the review is necessary for security or abuse investigation, or the review is required to comply with law.

How We Use Information

  • To provide, operate, maintain, secure, and improve Lynx products and services.
  • To complete tasks you initiate, including AI-assisted reading, writing, summarization, automation, search, retrieval, and software actions.
  • To sync settings, preserve task history, process payments, manage subscriptions, provide support, and communicate product or service notices.
  • To detect abuse, troubleshoot reliability, enforce terms, protect users, and comply with legal obligations.

How Information Is Shared

We share information with service providers that help us operate Lynx, including hosting, storage, analytics, payment, customer support, security, operations, and communication providers.

When a task uses AI models or connected integrations, selected task context may be sent to Lynx AI services, model providers selected or configured in Lynx, and the integration providers needed to complete the requested task.

Google Workspace API data is shared only as needed to provide and secure user-requested Lynx features, comply with law, protect against abuse, or work with service providers acting on our behalf under appropriate confidentiality and security obligations.

We may disclose information if required by law, to protect users or the service from abuse, or as part of a business transfer with appropriate user notice or consent where required.

Data Use Limits

We use personal data only to provide, secure, maintain, support, and improve Lynx products and services.

We do not sell personal data, use personal data for personalized advertising, transfer personal data to data brokers, or use personal data to determine creditworthiness or lending eligibility.

Human review of task content is limited to cases where you ask for support, give permission, report abuse or safety issues, or where review is required for security, legal, or compliance reasons.

Storage And Retention

The Lynx desktop app may store local settings, task history, logs, files, and authorized context on your device according to app behavior and settings.

Connected integration credentials, including Google OAuth access tokens and refresh tokens, are stored by Nango. Lynx may retain local or server-side connection metadata and task content needed to provide the connected integration features you request.

Lynx cloud services may retain account data, billing records, support records, logs, task history, authorized integration metadata, and user-authorized task content for as long as needed to provide the service, satisfy legal obligations, resolve disputes, maintain security, and enforce agreements.

When you disconnect a Google integration from Lynx, Lynx deletes the local connection mirror and asks Nango to delete the corresponding connection credentials. You can also revoke Lynx access from your Google Account settings.

You can request deletion support by contacting us. Some records may be retained where required for security, fraud prevention, legal compliance, accounting, or backup integrity.

Security

We use technical and organizational measures designed to protect personal data, including access controls, encrypted transport, monitoring, and least-privilege operational practices.

Off-device transmission uses HTTPS, WSS, or equivalent modern encrypted transport. Local app data remains on your device unless a Lynx feature, connected integration, cloud service, or model provider requires transmission to complete a requested task.

Your Choices

  • Control which integrations, permissions, and model providers you connect or use with Lynx.
  • Disconnect Google or other connected accounts from Lynx and revoke OAuth access from the provider account settings.
  • Adjust app settings, delete local task data where product controls are available, or uninstall Lynx from your device.
  • Contact us to request privacy support, account deletion help, or data deletion help.

Contact

For privacy questions about Lynx AI, contact us at [email protected].