Privacy & Security

What we hold, where it lives, and the two buttons that prove it

Niobe works because it knows you. That only holds if you can see exactly what it knows, take a copy, and destroy it — so this page ends with working buttons, not a promise to email someone.

What is stored, and where

Data	Where	Why
Account (email, sign-in)	Supabase (managed Postgres, encrypted at rest)	authentication
Onboarding answers	Supabase, row-level security — your rows are readable by your session only, enforced by the database (Postgres row-level security), with an automated probe checking the API's behavior hourly	they become your Niobe's brain
Notes, tasks, job history	Supabase, same row-level security	the work Niobe does for you
Your instance brain files	our operations server, isolated per customer directory	your Niobe's working memory
Chat messages	processed to answer you; the model provider (OpenRouter) processes but does not train on them per their zero-retention routing	conversation

What is NOT done

No selling or sharing of your data with advertisers or brokers — there is no ad layer here.
No training of any model on your content — not a shared model, and not a private one. Your instance is dedicated to you; what makes its answers yours is your own library, your profile and your corrections, used only for your instance.
Connected accounts are read with the narrowest scope that works (a mailbox is read-only: Niobe cannot send from it or delete in it), and every consequential action waits for your approval — the approval ledger is on your desk page.

Security, concretely

Transport is TLS everywhere; data at rest is encrypted by the storage providers.
Every code change ships through a gated pipeline: secret scanning (tree and full history), accessibility audit, workflow static analysis, dependency auditing, a signed SBOM with build provenance, and hourly behaviour checks against production — including a check that tries to read another tenant's data and must fail.
Security disclosures: see our security policy — acknowledgement within 2 business days.

Your copy, your delete

Signed in? These act on your account immediately.

Deletion removes your account and every row keyed to it in one cascading operation, and your instance files are reaped on the next reconcile pass. It cannot be undone. If a button fails, email hello@heyniobe.ai and a human does it.