Security & data

Private by architecture,
not by policy.

Your research is your edge. In Basis it is encrypted with a key derived for your account alone, so the database, the files, and the backups are unreadable on their own. Policies can change. Architecture doesn't.

What you see Basis
GTLB · Q3 channel checks
GTLB· Expert call · Jun 24

More net-new ARR from Duo Code pushes on SaaS. Two partners flagged longer sales cycles in EMEA; renewals holding. CFO comp framing suggests FY guide is conservative…

What the database sees D1 · notes

The same note, as it's actually stored: unreadable without the key that belongs to your account alone.

The commitments

Four things that stay true,
no matter what we ship next.

  1. Encrypted per person, not per platform

    Everything you create in Basis (notes, ideas, contacts, calendar entries, chats, files, even file names) is encrypted with a key that exists for your account alone.

  2. Your key never sits next to your data

    The key that unlocks your research is never stored in the database or the backups. On their own, they're unreadable. To be useful, data and key have to meet, and that only happens when Basis is doing work for you.

  3. AI on a need-to-know basis

    AI features see only what the task in front of them requires: a question about one company pulls the notes that matter, not your whole account. And we never train models on your research.

  4. Recoverable by design

    Deleted notes rest in a 30-day trash, the database can be restored to any point in the last 30 days, and every account gets its own daily encrypted backup, kept for 45 days. Losing your work should be harder than keeping it.

30days
Trash retention for deleted notes
30days
Point-in-time database restore
45days
Per-account encrypted backups

Your data is yours

Your notes, transcripts, tasks, and the graph built from them belong to you. We don't sell data, we don't mine it, and we don't train models on your private research, ours or anyone else's.

Want the specifics?

Security reviews, DPAs, self-hosting, or a walkthrough of the encryption design: write to us and you'll get an engineer, not a form response.

hello@basisbook.io