Privacy policy

This notice describes how Gen7 Labs, Inc., doing business as Cortex (“Cortex,” “we,” or “us”), handles information on our website and in the Cortex beta for iPhone and the web. We are incorporated in Delaware and operate from New Haven, Connecticut, United States.

Your conversations are private to your account and any explicitly assigned reviewer. “Private” does not mean inaccessible to the service operator: authorized administrators can access information when needed to operate, support, secure, or delete it.

1. Information we receive

• Invitation requests: your name, email, whether you are requesting for yourself or a teen as their parent or guardian, an optional message, and the date and privacy-notice version acknowledged. Please use the adult’s contact details and omit children’s information.
• Account information: sign-in identifiers, display details, invitation and device records, account permissions, and preferences. Google sign-in is separate from connecting Gmail or Calendar.
• Content you choose to provide: messages, photos, documents, saved library files, profile memories, voice transcripts, and feedback. Assistant replies, citations, conversation summaries, and approval records can contain this information too.
• Technical information: IP addresses, browser/device information, request timing, errors, and security signals used by our hosting and security services. Our invitation rate limiter stores a keyed, rotating network identifier rather than a raw IP address.

2. How we use information

We use information to review invitations, provide and personalize Cortex, answer requests, perform actions you approve, maintain continuity in conversations, provide support, and protect the service. An invitation request is not a marketing subscription and does not automatically create an account.

We do not sell personal information, use it for targeted advertising, or use private chats and connected Google data to train general-purpose AI models. Reviewing a conversation for support, debugging, or a user-requested accuracy check is different from training a model.

3. Where processing happens

Cortex’s model processing, chat history, uploaded content, and memories are handled on our privately operated server in the United States. Cloud infrastructure routes requests and real-time voice traffic. Data is encrypted in transit, but it is not end-to-end encrypted against Cortex as the operator.

The marketing website and private invitation queue use Vercel. Requests are also copied to our private server for administrator review. Google Workspace sends request notifications to our administrator and invitation emails after approval. Google Cloud supports the app gateway, and Tailscale provides a restricted connection to our server. Firebase/Google supports Google sign-in. Apple supports iPhone distribution and device speech features. These providers process information needed to provide their services; their own policies also apply.

4. Voice, research, and uploaded files

Speech recognition runs on the supported device or browser configuration; voice traffic is carried through our voice infrastructure. Cortex does not intentionally retain voice audio as recordings. Transcribed messages and assistant replies are retained in ordinary chat history. Microphone access depends on the mode you choose and your device/browser permissions.

When Cortex searches the web, selected search queries are sent to Brave Search or the relevant public data service, and source pages may be retrieved. Full chat histories and attachments are not sent as a search request. Queries can nevertheless contain details from your question; review any exact-query approval card presented after private context is used.

Photos and documents may be resized, rendered, or converted to extracted text for analysis. Files saved to Library can be reused in other chats on your account. Deleting a chat does not delete a separately saved Library item.

5. Optional Gmail and Calendar connections

Connecting Google is optional and requires separate Google consent. Cortex uses the permissions you grant to answer your requests and prepare supported email or calendar actions. Access and refresh tokens are stored encrypted on our server and are not placed in model prompts. Retrieved email or calendar details may appear in replies and remain in that conversation.

Connecting an account does not authorize every future write. Cortex presents supported changes for review before execution. You can disconnect in Connections & actions and revoke access in your Google Account. Disconnecting removes the active connection credentials and cancels its pending approvals; it does not erase information already included in chat history or backups.

Cortex’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We do not use Google user data for advertising or general-purpose model training.

6. Memories, conversation continuity, and access

You can ask Cortex to remember, update, or forget information in chat or use Profile & memory. Proposed persistent-memory changes require approval. Approved memories can be supplied to future conversations on your account. Forgetting a memory removes it from the active profile; the original chat or a previous reply may still contain the information until that content is deleted.

To continue long conversations, Cortex may create summaries of earlier messages and retain recent context. A summary can contain personal information and can be imperfect. It is not a separate guarantee that everything has been remembered or erased.

Other ordinary users cannot access your private history. A parent, guardian, or other reviewer can see history only when explicitly assigned that role; any such arrangement should be explained when access is granted. Do not assume a feature called Ghost or incognito is available unless the app explicitly enables it and explains its limits.

7. Retention and deletion

Website invitation records are scheduled for deletion after 90 days; expired rate-limit records are removed by the daily cleanup. You can request earlier removal by email. If an invitation leads to an account, the account and related correspondence have their own retention needs.

Ordinary app content remains available until you delete it or request account deletion. Chats moved to Recently deleted can be restored for 30 days unless you permanently delete them sooner; expired items are removed by the service’s cleanup. Library deletion and conversation deletion are separate controls. Previously generated replies may still quote a deleted file or memory.

Backups and security records may retain older data after removal from the active service. We do not promise immediate erasure from every backup. Contact us for account deletion, access or correction requests, and details of any residual retention. We may keep information needed to meet legal obligations, resolve disputes, or protect the service.

8. Cookies and browser storage

The marketing website does not run advertising trackers or third-party audience analytics. Hosting and bot protection use technical signals needed for delivery and abuse prevention. The separate Cortex app uses browser/device storage for sign-in, preferences, and local features. Clearing browser data or revoking permissions can sign you out or disable those features.

9. Teen access

The public beta is not offered to children under 13. Users aged 13–17 need a parent or guardian’s permission, with that adult requesting access and completing our follow-up before an invitation is issued. Do not submit a child’s personal details in the public form. If you believe we received information from a child under 13, contact us so we can investigate and remove it where appropriate.

10. Your choices and questions

You can edit memories, delete content, disconnect Google, manage device permissions, or stop using Cortex. Depending on where you live, applicable law may give you additional rights to access, correct, delete, or obtain your data and challenge our response. We will verify requests as needed and respond under applicable law without requiring you to publish private information.

For privacy requests, contact Gen7 Labs, Inc. d/b/a Cortex at sam@cortexinfra.ai. We may update this notice as the beta changes and will identify changes with the date above; material changes will be communicated as appropriate.