Privacy Policy

1. Google sign-in

Optional Google sign-in requests only openid, email, and profile. We receive your Google account identifier, email, verification status, name, and, where provided, Workspace domain to register, sign in, link accounts, and check eligibility.

We store the account identifier while linked, and the email and display name for a new account. Verification status and Workspace domain are checked during login or registration, not retained as separate profile fields. Other returned profile details are not used or saved.

We do not access your Google password, Gmail, Drive, contacts, or calendars through sign-in, or retain Google access or refresh tokens. We do not sell Google sign-in data, use it for advertising or AI training, or send it to model providers as task input. We follow the Google API Services User Data Policy, including applicable Limited Use requirements.

2. Information used by product features

• Accounts and connections: account, workspace, device, and configuration information supports setup and access. Separate provider connections may require storing their credentials.
• AI tasks: prompts, code, files, images, audio, and context go to the services used for your task. Responses, usage, and error records support results, history, billing, and troubleshooting. Optional local content logging retains task content on your device.
• Team work: enabled project, memory, backup, and handover features can store work content for authorized collaborators and devices. Optional AI assistance may process that content to organize or evaluate it.
• Sharing and remote access: a published conversation and subsequent discussion are accessible to people with the invitation link, according to the sharing mode. Remote access lets paired users view and act on permitted device content. Connection and activity information supports these features.
• Billing and support: we keep plan, usage, payment-status, invoice, and support records. Stripe handles payment details where offered; website inquiries send your submitted details to Google Forms.

We use this information to provide and support the service, manage access and charges, and address abuse. Sign-in alone does not upload local files or conversations.

3. Shared discussions and safety

Shares are invite-only: only people with the invitation link can join, and share pages ask search engines not to index them. Before anything appears in a share, visitor names, messages, dictated transcripts, the published conversation and its title, and AI answers are checked by an automated classifier (Llama Guard 3 on Cloudflare Workers AI). Content that fails the check is not shown or kept; we record only a participant reference, where it occurred, the category, a SHA-256 fingerprint, and the time, and delete that record after 30 days. While the check is unavailable, nothing new is published.

Visitors and sharers can report messages, participants, and AI answers. A report stores the reason, an optional note, a copy of the reported content of up to 2,000 characters with credentials and file paths removed, and references to the share and participant. Sharers see reports about their share without the reporter's identity. Codex Pass moderators review reports and may remove content, block participants, or suspend a share. Shared discussions follow our Content Guidelines.

Share pages keep your language choice, a random browser identifier, and messages you hide for yourself in your browser. We store only a one-way hash of the identifier, so a sharer's block also covers later visits from the same browser.

4. Who can access information

Providers process information needed for hosting, AI features, payments, and communications. Administrators, collaborators, and share recipients can access information permitted by their roles or sharing settings. Configured notifications can send activity to organization-selected destinations.

Authorized personnel may access data for support, operations, security, or legal obligations; moderators see reported content and its current state. We may preserve and disclose content where the law requires, such as reports of child sexual exploitation. We do not sell personal information. Providers and workspace operators have their own privacy practices; processing may occur outside your country.

5. Storage and retention

Settings and logs may stay on your device; hosted features store necessary data on service infrastructure. We use access controls and protected connections. Retention follows feature and workspace settings and operational or legal needs; ending a connection does not immediately erase records or backups. Reports are kept while they are reviewed and afterwards for safety, legal, and dispute purposes.

Browser storage supports preferences, activity counting, and sign-in. Website visits, referrals, engagement, and button events go to Google Forms. Hosting and font providers receive connection information such as IP addresses and browser details.

6. Your choices and deletion

Use available controls to manage logging, synchronization, and access; workspace content may require administrator help. Pausing a share may leave history readable; revoking it ends access through that share. Neither recalls recipients' saved copies. Sharers can also remove a message for everyone or block a participant, and visitors can hide messages for themselves.

Unlink Google in account settings after setting a password, or revoke access in Google Account connections. Unlinking removes the Google identifier, not your account, email, or display name. Revocation does not erase retained data or end existing sessions.

Contact us for access, correction, deletion, account closure, or stopping product emails. We may verify ownership and retain records required for legal, security, or dispute purposes. Uninstalling the app does not erase hosted data.

7. Changes

We will update this policy and provide notice or obtain consent where required before changing how we use your data.

8. Contact

Codex Pass is operated by FLOWNET TECH LLC. For privacy and data requests: support@cp.dev. Include your account email, never passwords or tokens. See also our Terms of Service.