Trust
What we do to keep your data safe, and what is still open
This page states the controls that exist today and the gaps that remain. Our security is hardened and under review, not certified. We list the open items on this page rather than hide them.
// Tenant isolation
Every workspace's data is kept apart
-
Row-level separation
Every record belongs to one workspace. Every request is limited to the workspace of the signed-in session or API key, and every query filters by it. The workspace is never taken from what a client sends.
-
Two kinds of sign-in kept apart
Customer tokens and staff tokens are signed with different keys and carry a platform claim. A customer token is refused by the staff API, and the other way round.
-
Roles checked on every call
Inside a workspace there are two roles, owner and member. Owner-only actions, such as approvals, read the role from the database on each call, so a change of role takes effect straight away.
-
Dedicated database: designed, not offered
Workspaces share the platform database today, separated at row level. A dedicated-database option is designed for large tenants but is not offered yet.
// Logging and secrets
Requests are logged. Secrets are kept out of the logs.
-
Request logging
The platform logs requests so a fault can be traced. Public operations are rate limited.
-
Secret redaction
Secrets and signed links are removed from traces and logs. The redaction catches recognisable shapes, not every possible secret, so we also advise against pasting secrets into prompts.
-
Keys and credentials
API keys are stored only as hashes and shown once, when created. Credentials for connected systems are held in a secrets store, not in code or in workflow definitions.
-
Outbound calls are guarded
When a workflow calls a web address, the platform blocks requests aimed at internal networks.
// What is audited
You can see what happened and who decided
-
Run traces
Every workflow run is recorded step by step, so an owner can see what an AI employee did and why.
-
Audit log
Sensitive changes in a workspace are written to an audit log that owners can read.
-
Approvals
When a step waits for an owner, the decision and who made it are kept with the run.
-
Usage and spend
Usage is recorded per workspace. Spend caps and per-key model limits can be set.
// Data handling
What happens to the data you give us
-
Your documents serve your AI employees only
Documents you upload to a knowledge base are used to answer questions for your own workspace and are not shared with other workspaces.
-
Model providers
To write an answer, the text of a conversation and the passages retrieved for it are sent to the language-model providers we use. Do not send data you are not allowed to share with a model provider.
-
AI drafts, people decide
Anything involving money, promises or records can wait for a named owner to approve before it happens.
// Hardening in progress
Recent work, and the review that continues
-
Done recently
Encoded (compressed) request bodies are refused. Servers run a current Node.js release. HTTPS-always and TLS 1.2 are set on our main domains.
-
Under review
We are working through the findings of an internal security audit. We describe our security as hardened with the review in progress.
// Open items
What is not done yet
Stated plainly, so you do not have to find out later.
-
No penetration test
A third-party penetration test has not been done.
-
No certifications
We hold no security certification, such as SOC 2 or ISO 27001. This page carries no badges for that reason.
-
Dedicated-database backups
Backup and disaster-recovery tooling for the dedicated-database option is in progress. It is the largest open gap.
-
No personal-data tooling
We do not yet have automated tools for personal-data export or erasure requests.
-
No published data-processing terms
We have not published a data-location statement, a data processing agreement or a subprocessor list yet.
-
Upload limits
Size limits for the unpacked content of uploaded documents are not in place yet.
-
No uptime commitment
We do not publish an uptime figure or a service-level agreement yet.
Have a security or privacy question?
Ask us. We will answer from what exists today and say so when the answer is no.