Security

How Necory protects what you tell it

A second brain only works if you can trust it. Here is exactly what we do — and one thing we deliberately don't, explained honestly.

Encryption, in transit and at rest

All traffic between the app and our servers uses TLS. Your data is stored on Google Cloud (Firebase), where it is encrypted at rest by Google's infrastructure. Uploaded files live in Firebase Cloud Storage under the same protections.

Per-account isolation, enforced on the server

Every record — every note, message, file, reminder, and ledger entry — is stored under your account ID, and server-side security rules make it impossible for any other user to read or write it. When the AI acts on your behalf, the server scopes every operation to your signed-in account; the AI cannot name a different account even if it tried.

The AI can act, but not lie about it

Necory's assistant is powerful, so we constrain it structurally:

  • Claim = proof. If the reply says "saved" or "deleted", the server verified that exact action happened in that turn.
  • Money math is server-only. Balances are computed from an append-only ledger on our servers. The AI records events; it never calculates or asserts a balance on its own.
  • Deletions go through a commit gate. Bulk deletion is executed by the server only after your explicit confirmation — the model has no ability to commit it alone.
  • Everything you saved is treated as data, not instructions. Text inside your files, images, and notes cannot re-program the assistant.

Sign-in security

  • One-time email codes (sign-in and password reset) are generated with a cryptographically secure generator, stored only as SHA-256 hashes, valid for 10 minutes, usable once, and rate-limited against brute force. Phone sign-in codes are delivered and verified by Firebase Authentication — we never see or store them.
  • When you set a password, we check it against known breach databases using the Have I Been Pwned range API — only the first five characters of a hash ever leave our servers, never your password.
  • Google and Apple sign-in use the platforms' standard flows with server-side nonce verification.
  • You can require Face ID / biometric unlock to open the app. Biometrics are checked entirely on your device and never sent to us.

App integrity

Production builds attest their integrity with Firebase App Check (Play Integrity on Android, App Attest on iOS), so our backend only answers genuine, unmodified copies of the app.

What we deliberately don't do — and why

Necory is not end-to-end encrypted. The assistant has to read your content to answer you — that's the product. Your data is encrypted in transit and at rest, and isolated to your account, but our systems (and the AI models we use) process it in readable form. If you need content that no service can ever read, an E2E-encrypted notes app is the right tool for that content. We'd rather say this plainly than imply otherwise.

Your controls

  • Export your entire vault as a downloadable archive from Settings, on any plan.
  • Delete individual items (30-day trash), whole conversations, all data, or your entire account — permanently, with a 30-day recovery window.
  • Review the AI's memory: every learned observation is listed in Settings where you can confirm, dismiss, or lock it.

Reporting a vulnerability

If you believe you've found a security issue in Necory, email support@necory.com with the details. We read every report and will respond as quickly as we can. Please don't access other users' data while researching.