Security at Nirvest

What we actually do to keep your workspace yours. No certifications we do not hold, and a plain list at the end of what we have not built yet.

Last reviewed 23 September 2026.

Your workspace is isolated in the database, not just in the app

Every table that holds workspace data carries the workspace it belongs to, and the database itself refuses to return a row from another workspace. This is enforced by the database engine on every query, so a mistake in application code cannot leak another firm's data.
The same rule applies to our own background jobs and to the AI. There is no query path that quietly sees everything.

You sign in with your Google or Microsoft work account. Nirvest never asks for, never receives and never stores a password for your workspace, so there is no password of yours for us to lose.
Your organisation keeps control: if your IT team disables an account or enforces its own multi-factor policy, that decision applies to Nirvest immediately.

The internal console is a separate application on a separate domain with its own accounts. It is not reachable from your workspace and shares no session with it.
Every internal account requires an authenticator app. Sessions are short and expire on their own.
Riskier actions require a written reason and a fresh authenticator code at the moment of the action. The most sensitive require a second administrator to approve before anything happens.
Every administrative action is written to an append-only log that records who did what, when, and the before and after values. Our staff cannot edit or delete that log.
When support needs to look at an account, that access is time-limited and returns counts and statuses only. It does not show your emails, documents or notes.

Data is encrypted in transit, and the database is encrypted at rest.
Authenticator secrets are encrypted in the database and backup codes are stored only as hashes, so neither can be read back out.
A stolen server key on its own is not enough to read internal sessions or the audit log: those tables deny access to the server role that application code uses.

Repeated failed sign-ins to the internal console lock the account and are rate-limited by address.
Content that reaches the AI from outside — an email body, a document, a web page — is treated as data, never as instructions. If something in it tries to give the AI orders, the request is refused rather than partly answered.

We would rather tell you this than have you assume it.

We do not hold a SOC 2 report or an ISO 27001 certificate. We have not been independently audited.
We have not commissioned an external penetration test.
You cannot yet choose which region your data is stored in, or bring your own encryption keys.
Nirvest is early. If any of the above is a requirement for you, tell us and we will be straight with you about timing.

Write to us and we will respond. We will not threaten a researcher who reports something in good faith.