Quiet on the surface, careful underneath.
Your second brain holds private thinking. The platform that holds it should act like it. Here’s how tentus does that.
How we secure your data.
tentus runs on Supabase and Vercel, two platforms with SOC 2 Type II and ISO 27001 controls in place. Every workspace is isolated by row-level security at the database layer — even a misconfigured query can’t cross workspace boundaries.
Production credentials live in a managed secret store, rotated on a ninety-day cycle. No engineer has direct database access; all reads and writes go through audited application paths.
Where your data lives.
Workspace data is stored in Supabase’s US-East region. Long-form attachments — PDFs, audio, images — sit in object storage inside the same region, scoped to your workspace.
Background jobs run through Inngest with payloads ephemeral by default. We don’t mirror your data to third-party analytics warehouses.
Encryption.
Everything in transit is encrypted with TLS 1.3. Everything at rest is encrypted with AES-256, including database volumes, object storage, and backups.
OAuth refresh tokens for connected integrations are encrypted with a per-workspace key before they touch our database. A stolen database dump on its own would not give an attacker access to your connected accounts.
Lumi privacy.
Lumi only knows what you’ve told it. It reads across the sources in your workspace, cites them whenever it surfaces something, and admits when it doesn’t know.
Lumi’s reasoning runs through Anthropic and Google’s model APIs under data-processing agreements that explicitly exclude training on customer content. Your captures are never used to improve a third-party model.
Access controls.
Sign-in is handled by Supabase Auth with passwordless email links and OAuth via Google and Microsoft. Sessions expire on a rolling window with refresh tokens that you can revoke from settings.
Two-factor authentication is on the roadmap for Pro and Team tiers. Admin-side, every production action is logged and reviewed.
Incident response.
If something goes wrong, you’ll hear from us first. Our incident playbook commits to notification within seventy-two hours for any incident that could affect your data, with a written post-mortem published once the cause is understood.
Responsible disclosure.
Found a vulnerability? Email security@tentus.io with a description and reproduction steps. We acknowledge reports within one business day and aim to resolve confirmed issues within thirty days.
We don’t run a paid bounty yet, but we credit researchers publicly with their permission, and we’re happy to send a small token of thanks for valid reports.