Most privacy pages make one promise and leave you to assume it covers everything. This one goes feature by feature, because that is the only way the promise can be checked.
“Private” is easy to say about a product and hard to say about a feature. The interesting question is never whether a company intends to be careful — it is what each part of the app actually sends, what it keeps, and who holds the key to it. Those answers differ feature by feature, so here they are, one at a time.
Chat
Your question goes to the AI. Your identity doesn’t.
Every message goes through Secure AI first. The AI receives what you asked — not your name, email address, account, or other information that identifies you.
On the web, chats disappear when you leave. They aren’t saved to your account or synced to another device. For conversations you want to keep, use Secure AI on iPhone or Android.
Memory
Your memory is encrypted before it leaves your phone.
Memory is the most personal thing Secure AI knows — what you’re working on, your preferences, and the things you’ve asked it to remember.
That’s why it’s encrypted on your device before it’s stored. Our servers receive encrypted data, not readable memories. And your memory is never available through the web.
Notes
Your notes are encrypted before they leave your phone.
A note is written on your device and encrypted there. What reaches our servers is ciphertext — we hold the storage, not the key.
Tasks
Your tasks are encrypted on your device.
Ask Secure AI to create a reminder and your device handles it — including the notification that reminds you later.
Projects
Your projects carry context. Not your identity.
Projects let Secure AI remember how you want something done — your instructions, preferences, and the context needed to keep working.
When AI is needed, it receives the context required to answer. It doesn’t receive your name, email address, or account identity. Projects are available only in the iPhone and Android apps.
Files
Your files are used for the answer. Not kept.
A document is read on your device and reduced to the text needed to answer. The original bytes are not uploaded and not stored.
The pattern
Two mechanisms do all the work above. Identity is stripped before a request reaches a model, so what the AI answers is your question without the person who asked it. And anything stored is encrypted on your device first, so what our servers hold is ciphertext rather than your notes.
The web client is deliberately the weakest of these, and that is the honest way round: a browser cannot hold a hardware-backed key, so rather than pretend otherwise, the web app keeps nothing worth taking. Memory, notes and projects live in the iPhone, Android and desktop apps, where the key can be kept properly.