How we secure your data

Hosting and data location

• Data is stored with Supabase (Postgres, authentication and file storage) in its Mumbai, India region.
• The application runs on Vercel, with server functions pinned to Mumbai, India.
• AI and other providers listed below may process data in the United States and other countries.

Encryption

• In transit: TLS on every connection. The web app sends HTTP Strict Transport Security and a Content Security Policy.
• At rest: database and file storage are encrypted by Supabase.
• OAuth tokens for connected accounts are additionally encrypted by Cortex with AES-256-GCM before they are stored.
• API keys are stored only as SHA-256 hashes. Passwords are stored only as hashes by our authentication provider.
• Not end-to-end encrypted. Cortex answers by retrieving over your material on our servers, so our systems can read it.

Access controls and isolation

• Row-level security with owner-only policies on user data tables. An automated check fails any release whose database migration creates a table without row-level security.
• The browser holds no database keys. It talks to our own server routes, and privileged database access happens only on the server.
• Organization data is keyed to one organization. Access to a teammate’s clone is authorized on organization membership and permission role on every request, so a removed member loses access immediately.
• Provenance firewall: material from connected accounts, devices and ambient capture is private to its owner by default and never used in public or teammate answers.
• Public clones are rate limited and protected by a Cloudflare Turnstile bot check.

Account security

• Email and password, or Google sign-in.
• Optional two-factor sign-in with a one-time code sent by email. You can mark a browser as trusted for 30 days, and revoke trusted browsers from Settings.
• API keys can be created and revoked by the account owner at any time.
• SSO and SCIM (SAML or OIDC single sign-on and automated provisioning) are available on request for enterprise customers. They are not self-serve today.

Staff access

Production access is limited to a small number of people. When Cortex staff change a user’s brain through our support tooling, the change is written to an append-only log that the user can read under Settings → Your data (“Cortex staff access”). It cannot be edited or erased from inside the product. Read-only access by staff is not logged there today.

AI providers and retention

• OpenAI is the primary model provider; Anthropic is used as a fallback.
• Every OpenAI chat request is sent with storage switched off (store: false), enforced in code on each request.
• We have not signed zero data retention agreements with OpenAI or Anthropic. Under their standard API terms they may retain request data for a limited period for abuse monitoring.
• We do not use customer content to train models, and neither provider trains on API data under its standard terms.

Subprocessors

• Supabase: database, authentication and file storage (Mumbai, India region)
• Vercel: application hosting and serverless functions (Mumbai, India region), and page performance metrics
• OpenAI: language models, embeddings, transcription and speech synthesis
• Anthropic: language models, used as a fallback when the primary model is unavailable
• ElevenLabs: voice cloning and speech synthesis, only if you create a voice clone
• Smallest.ai: voice cloning and speech synthesis, only if you create a voice clone
• Razorpay: payment processing and subscriptions
• Resend: account, security and billing emails
• Google: Google sign-in and read-only Google Calendar, only if you use them; Google Analytics for site usage
• Composio: read-only connections to third-party apps, only if you connect one through it
• Cloudflare: Turnstile bot check on public clones
• PostHog: product analytics and session recordings with form inputs masked
• Microsoft Clarity: site usage analytics
• FormSubmit: delivers waitlist form submissions to our inbox

Business customers get 30 days’ notice of a new subprocessor under our Data Processing Addendum.

Retention and deletion

• Content is kept until the user deletes it. Users can export everything as one file at any time.
• Account deletion locks the account and takes any public clone offline immediately. An hourly job permanently deletes the content 7 days later, including stored audio and the cloned voice at the voice provider. A scrubbed record that reserves the username, and billing records, are kept.
• When the last member leaves an organization, the organization and its company material are deleted.
• Managed database backups may hold deleted data for a limited period until they are overwritten.

Compliance status

• We do not hold a SOC 2 or ISO 27001 report today. If you need one for procurement, tell us; we answer security questionnaires directly.
• Our Privacy Policy covers GDPR, India’s DPDP Act and CCPA, and our DPA covers processing on behalf of organizations.

Incidents

If we become aware of a breach affecting your data, we will contain it, tell affected customers without undue delay, and notify authorities where the law requires. Business customers are notified within the time set in the DPA. Report a suspected incident to aashwin@makecortex.com or +91 99970 45800.