Hosted in the EU
The production service runs in Google Cloud's europe-west1 region. Model traffic can additionally be held inside an EU data boundary, which refuses any request it cannot serve within it rather than routing it elsewhere.
Security and trust
What we can prove, and what we cannot
Naski holds no SOC 2 report and no ISO 27001 certificate. What follows is what the product does, and the documents that commit us to it.
Secrets, encrypted
Connector credentials, remote MCP server credentials and two-factor secrets are encrypted at rest. MCP access tokens and OAuth authorization codes are stored only as hashes, passwords as Argon2 hashes, and stored files are served through short-lived signed URLs.
Single sign-on, on your terms
OIDC, configured by the organization. An email domain grants nothing until a DNS record under that domain proves you control it, and single sign-on grants membership without ever raising an existing role.
Two-factor, required by the company
An organization can require TOTP of its members. The requirement gates the company's shared space and its agents — not the person's own account, so nobody's personal work is held hostage by an employer's policy.
An audit trail you can export
Access grants and revocations, role changes, agent ownership and budget changes, credential settings, approval and review decisions, and document reads — each recorded with who, what and when, and downloadable as CSV.
Untrusted code stays untrusted
Agent code runs in an isolated realm with an empty global scope, a memory limit and a timeout; every value crosses as JSON, and credentials never enter it. Outbound calls are HTTPS only and are refused when the address resolves to a private network. Shared pages render in a sandboxed frame with no network of their own.
The documents
Published on the app domain, and kept in step with the code rather than with a sales cycle.
- Sub-processors →Every third party that processes data on our behalf, derived from the code that actually runs — including the entries whose region we cannot contractually pin, said plainly.
- Data Processing Agreement →An Article 28 DPA, with the technical and organisational measures set out in Annex II and thirty days' notice before a sub-processor is added.
- Privacy policy →What we process, on what basis, for how long, and how the EU data boundary changes where model requests are served.
If a claim here is not true, tell us
Every statement on this page is meant to be checkable in the product or in those documents. Write to [email protected] if one of them is not, and we will correct or remove it.