Security by subtraction
The strongest control we ship is the data we never collect. Mnem keeps your memories on your device by architecture, so most of the questions a security review asks simply have no attack surface to point at.
What we protect — and how
Memories stay on-device
Everything Mnem remembers is stored locally on your Mac or Windows PC. There is no server-side memory store, no sync copy, no "encrypted at rest in our cloud" — the data isn't in our cloud at all.
Tokens never travel
API tokens and settings are kept locally on the device. Mnem's cloud cannot read them, and neither can we — recovery, migration, and backup all happen on hardware you control.
A cloud too small to breach interestingly
Per user, our server-side footprint is an email address, subscription state, license and device records, and — only if you write to us — your contact-form message. Short enough to audit in one sitting; the full table is below.
No telemetry, period
No analytics code exists in the app to turn on. Its network traffic: license verification on activation and when you refresh, an update check, a one-time embedding-model download on first run, and — only if you enable capture — distillation calls to the LLM provider you configured. Your network team is welcome to put a proxy in front of it and look.
Where your data lives
Every category of data, its location, and who can read it.
| Data | Where it lives | Who can read it |
|---|---|---|
| Memories | Your device only | You, and the AI tools you connect |
| Settings & API tokens | Your device only | You |
| Email, subscription state, license & device records (device IDs and the names you give them), Stripe customer ID | Our cloud (Cloudflare) | Us, for billing and licensing only |
| Sign-in magic-link tokens (stored hashed, single-use, short-lived) | Our cloud (Cloudflare) | Us, for authentication only |
| Contact-form submissions (name, company, email, seat count, message) | Our cloud (Cloudflare); a copy is emailed to us via Resend | Us, to answer you |
| Payment card details | Stripe | Stripe (PCI DSS Level 1) — never us |
| Telemetry, analytics, usage data | Nowhere — none is collected | Nobody |
Why it's built this way
Most AI-memory products are a database of your conversations in someone else's cloud. Every one of those databases is a breach target, a subpoena target, and a compliance liability for the customer. We decided the honest fix is structural: if the sensitive data never leaves the device, the whole class of failure disappears. We can't leak what we don't have, and we can't be compelled to hand over what was never sent to us.
This is local-first by architecture, not by policy toggle. There is no server flag that turns memory syncing on — the code path doesn't exist.
Platform integrity
- macOS: no kernel extensions, no background installers. Developer ID signing and notarization are in progress and will ship before general availability; current preview builds are unsigned, so verify the download came from this site.
- Windows: silent-install-friendly package for MDM deployment. Authenticode signing is in progress on the same schedule; current preview builds are unsigned.
- Downloads are gated by license and served through signed links that expire after 15 minutes.
The cloud, in one paragraph
Identity, billing, and license issuance run on Cloudflare Workers with a D1 database and R2 artifact storage. Sign-in uses magic links — we never store passwords, so there are no password hashes to steal. Transactional email (magic links, contact-form copies) is delivered through Resend. Payments are handled end-to-end by Stripe; card numbers never touch our systems. This website itself makes zero third-party requests and ships a strict Content-Security-Policy, self-hosted fonts included.
Compliance & SOC 2
Our infrastructure subprocessors hold the audits your security team will ask about: Stripe is PCI DSS Level 1 certified and SOC 2 attested, Cloudflare's platform is SOC 2 Type II audited, and Resend, which delivers our transactional email, publishes its own SOC 2 attestation. Mnem's own architecture keeps the highest-sensitivity data — your memories — entirely out of any auditable cloud scope, because it never leaves your hardware.
We're glad to walk security teams through the architecture, complete questionnaires, and provide our DPA. The data-processing appendix is short — the table above is the inventory. Write to [email protected].
Reporting a vulnerability
If you believe you've found a security issue in Mnem, the website, or the licensing cloud, email [email protected] with the subject "Vulnerability report". We read every report, respond quickly, and won't take legal action against good-faith research.
Last updated: September 11, 2026 · See also the privacy policy and Mnem for Business.
Put it in front of your security team.
We'll answer the hard questions — there aren't many left when there's no data lake.