Your memory. Your data.
Conxt captures your most sensitive professional context. This page explains exactly how your data is protected, who can access it, and what we can and cannot see.
- Encrypted in transit and at rest
- You own your data
- Never sold or used to train AI
- Secrets blocked before storage
- You choose what is captured
What Conxt can and cannot see
#This is the most important question for any memory product. Here is a precise answer.
What we can see
What we cannot see
Who can access production data:only Conxt's operators, and only to run, secure and support the service. Conxt is a small team; we do not yet have a separate approval and audit process for that access.
You control what is captured
#The Chrome extension (version 1.3.0 and later) lets you decide what leaves your browser. Each control works inside the extension, so what it holds back reaches Conxt only if you later let it.
Review before saving is off unless you turn it on. Without it, the extension sends each conversation as replies arrive, as described below.
How your data flows
#Every piece of data Conxt touches follows this exact path.
The Chrome extension reads the conversation on Claude, ChatGPT, Gemini or Grok and sends its text to the Conxt engine over TLS. It does not filter the text in the browser. You can pause capture, or review each chat before it is sent (see You control what is captured).
Before anything is stored, the engine checks the conversation for recognised secrets: API keys, access tokens, private keys and database connection strings. If it finds one, the conversation is not stored and nothing is extracted from it; only the kind of secret is logged. Card numbers and social security numbers are removed before storage. Email addresses and phone numbers are kept, because they are how a memory names a person. Memories an AI tool saves through Conxt are checked the same way.
The conversation text is sent to Claude through the Anthropic API to extract structured memories. Memory text is sent to OpenAI to build the search index. Neither trains its models on data sent through its API.
Extracted memory records are stored in Supabase on AWS in Oregon, United States. All data is encrypted at rest using AES-256, which protects against stolen disks and backup files but not against someone with database access. Every request is authenticated, and the engine scopes every query to your account and the teams you belong to.
The conversation text is deleted as soon as memories are extracted from it. If extraction fails, it is kept so it can be retried, and deleted after 30 days at most. Only the structured memory records persist. You can delete individual records or your entire account at any time: a deleted memory is removed at once, and an archived one 30 days after it was archived. The audit trail records that a change happened, never what the memory said.
Infrastructure and security
#Data residency
#All Conxt data is currently stored in AWS us-west-2 (Oregon, United States). Other regions are not available yet.
United States
AWS us-west-2
Available nowEuropean Union
AWS eu-central-1
PlannedAsia Pacific
AWS ap-southeast-1
PlannedIf you need your data in another region, contact us at hello@conxt.dev to discuss data residency requirements.
Encryption roadmap
#What is in place today, and what we plan to add. Planned items have no committed date.
One limit, stated plainly. Conxt has to read a memory's text to do its job: to extract memories from a conversation, make them searchable, keep secrets out of them, and give them to your AI tools. Encrypting memories so that Conxt cannot read them would stop all of that, so Conxt is not zero-knowledge and we do not plan to claim it. What we can offer instead is control over who holds the keys, and where Conxt runs.
All data stored in Supabase, including backups, is encrypted at rest using AES-256. This protects against stolen disks and backup files. It does not stop someone with database access, which includes Conxt's operators.
All communication between your browser, the extension, and the Conxt engine uses TLS 1.2 or higher.
Memory text encrypted with a key held in your own cloud key service. Conxt uses it only to serve a request; revoke the key and your stored memories become unreadable, to Conxt as well.
For teams that need Conxt never to hold their data: the engine and database run in your own cloud account, with your own model provider keys. Your memories stay in your infrastructure, under your access controls.
Your data rights
#You have full control over your data at all times.
How to delete your data
#You can delete your data at any level — individual records, all memories, or your entire account.
Delete a single memory
Export then delete all memories
Delete your account
We respond to all deletion requests within 48 hours. For GDPR or CCPA requests, contact hello@conxt.dev and we will process your request within the legally required timeframe.
What we will never do
#Larger teams
#Today every team gets the same controls: owner and member roles, a review queue for shared memory, and an export of everything you wrote. SSO, a separate database per customer, custom retention and other regions are not available yet. Tell us what your organisation needs and we will say plainly what we can do.
Security review
We will answer your security questionnaire as it applies to Conxt today.
Model agnostic by design
#Conxt is infrastructure for AI memory — not tied to any single AI vendor or platform.
Questions about data privacy?
We answer privacy and security questions by email.