Privacy Policy

4. Google user data

Some Crux features optionally connect to Google APIs via OAuth. Each integration (Google Drive, Gmail, Google Analytics) is a separate connection with its own scopes. You start the connection yourself from Settings or the relevant import flow. We do not access Google user data until you complete Google’s consent screen. You can disconnect at any time in Settings. We request only the narrow read-only scopes needed for each feature.

The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements. See section 4.5.

4.1 What Google user data we access

• Google Drive (scope https://www.googleapis.com/auth/drive.readonly, via the Google Drive API). After you connect, we may list and search files you can already access in My Drive and shared drives, and read file metadata only for that list (name, type, last modified time, and a link to open the file in Drive). We download or export file content only for files you explicitly choose to import (for example Google Docs, Sheets, Slides, PDFs, Word documents, and similar research files). Native Docs/Sheets/Slides are exported to a portable format (such as PDF or CSV) so they can be stored in your Crux project. We do not create, edit, move, share, or delete Drive files. We do not scan Drive in the background or access file content you have not imported.
• Gmail (scopes gmail.metadata, userinfo.email): your Google account email address and message metadata / headers only (for example From, To, Cc, Subject, Date, and related headers). We do not request or access Gmail message bodies or attachment contents.
• Google Analytics (scope https://www.googleapis.com/auth/analytics.readonly, via the Google Analytics Admin API and Analytics Data API). After you connect, we list the GA4 properties you can access so you can choose one. We then run read-only aggregate reports you request — fixed presets such as audience, acquisition, top pages, key events, and device/browser split, and the same class of aggregate report when you ask a question in Crux. We do not request user-level or personally identifying Analytics dimensions, and we do not edit properties, audiences, or measurement settings.

4.2 How we use Google user data

We use Google user data only to provide or improve user-facing features that are visible in Crux, specifically:

• Showing an in-app Drive file list/search so you can find research files, then importing and indexing only the files you select into your project
• Matching and surfacing project-related email metadata against filters you configure (addresses, subject keywords, or labels)
• Importing GA4 aggregate reports you request into Research tables, and answering your in-product questions from those same aggregate reports
• Running AI features you initiate on content already in your project (for example summarising an imported Drive document). We do not use Google user data to train or improve a machine-learning model other than a feature you run on your own project

We do not use Google user data for advertising, retargeting, personalized or interest-based ads, selling data, data brokerage, credit scoring, lending decisions, or any purpose unrelated to providing or improving these Crux features.

4.3 Sharing, transfer, and disclosure of Google user data

We do not sell Google user data. We do not share Google user data with third parties for their own advertising or unrelated purposes. We do not transfer Google user data except:

• To subprocessors that process it solely on our behalf to provide or improve the Crux features described above, and only with the access needed for that work
• For security purposes (for example investigating abuse)
• To comply with applicable law
• As part of a merger, acquisition, or sale of assets, only after obtaining explicit prior consent from you where required

Those subprocessors currently include:

• Neon — database hosting for project data, imported file records, and encrypted Google connection tokens
• Vercel — application hosting and infrastructure
• AI model providers (for example Google Gemini API and OpenAI API) — only when you use an AI feature that needs the relevant project content as input. Those providers process data under their API terms and do not use it to train models for Crux customers
• Clerk — authentication and account management

4.4 How to revoke access

• In Crux: open Settings → External sources and disconnect the Google integration. That removes the stored refresh token for that connection so Crux can no longer call Google APIs on your behalf.
• In your Google Account: remove Crux at any time under Third-party apps with account access.

Disconnecting stops further Google API access. Copies you already imported into a Crux project stay as project content until you delete them, delete the project, or delete your account (see 4.7).

4.5 Limited Use compliance

The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

Crux’s use and transfer of information received from Google APIs also adheres to the Google API Services User Data Policy, including the Limited Use requirements.

4.6 Storage, protection, and human access

• OAuth refresh tokens for Google connections are encrypted at rest.
• Data is transmitted over encrypted connections (HTTPS / TLS).
• Project data is scoped by user and organisation (tenant isolation). Cross-tenant access is not possible by design.
• We apply least-privilege scopes and do not request Google data we do not need for the connected feature. Drive, Gmail, and Analytics are authorised separately.
• Humans do not read Google user data, including imported file contents and Analytics reports, except: with your affirmative agreement for a specific support case (for example helping you recover access); where the data is aggregated and anonymized for internal operations; where necessary for security investigations or abuse prevention; or to comply with applicable law.

4.7 Retention and deletion of Google user data

• Google OAuth tokens are retained only while that Google connection remains active.
• Disconnecting a Google integration (in Crux or via your Google Account) ends ongoing API access. We delete the stored refresh token for that integration.
• Drive metadata used to render a file list is not kept as a standing copy of your Drive. File content is stored only for files you import. Imported Drive files and imported Analytics reports remain as project content until you delete them, delete the project, or delete your account.
• Gmail metadata synced for project matching is retained while needed for that feature and is removed when you disconnect Gmail, clear the relevant project mail data, delete the project, or delete your account, subject to short-lived backups and operational logs.
• You may export or delete project data from Crux. Deleting a project removes associated project content, files, embeddings, and related AI interaction history.
• To request deletion of Google user data or account-related data, contact simon@crux-hq.com. We will complete deletion requests for Google user data we hold, subject to legal retention duties and short-lived backups.