Security
Every customer gets their own environment: their own database, their own backend and their own storage. Nothing is shared between customers, so one customer's data cannot reach another's through a missed filter.
Inside that environment, every request is checked against what the person or agent may do, every change goes through a declared action with its own approval rule, and each change is recorded where the running system cannot rewrite it.
Separate environments
Each customer has their own PostgreSQL database, backend processes and storage, which we operate. A second customer is a second environment, not another row in a shared table.
Your identity provider
People sign in through your identity provider, with single sign-on and multi-factor authentication through WorkOS. Membership is read live rather than copied.
One role each
Every member is a member, operator, admin or owner. Admins manage people and settings but cannot change operational records; that takes an operator.
One way to change data
People, agents and automations change data through the same declared actions. An action can require approval, and the approver must be someone other than the person who asked.
A record that stays
Every change records who made it, under what authority and what changed. The running system cannot edit or delete those records, and a copy goes to separate write-once storage.
Models without keys
A model call is one request and one answer, with no tools, no browsing and no credentials. What a model proposes is applied only through the same actions and approvals as any other change.
Secrets by reference
Secrets live in a secrets manager. Code, deployment files, logs and API responses hold references to them, never the values.
Checked releases
A release takes traffic only as an exact signed commit on a pinned image, with its database permissions verified and its monitoring and backups in place.
Audited
Bijection holds SOC 2 Type 2 and is HIPAA and GDPR compliant. The rest of this page describes what the system enforces, which is not the same as what an auditor has examined.
- SOC 2 Type 2
- Zero data retention available
- HIPAA compliant
- GDPR compliance
- Single sign-on (SSO/SAML)
- Dedicated single-tenant deployment
Questions
Is Bijection multi-tenant?
No. Each customer runs in a separate environment with its own database, backend processes, storage and identity-provider organization. There is no shared data plane to select a customer from.
Can Bijection run in our own cloud account?
Not today. Bijection is a managed service: we provision and operate every environment, and we do not deploy into a customer's cloud account or on premises.
Can an AI agent change our systems on its own?
An agent can read what its authority allows and prepare a change. To apply it, it calls the same action a person would, under the same approval rule, and the same record is written. An agent never has more authority than the person or automation that started it.
What does a model provider receive?
The request for that one call, sent with provider-side storage disabled, no tools and no credentials. Nothing in it leads back to your database or your connected systems.
We train no models. Zero data retention is available on the provider accounts we use; what a provider keeps is governed by that account's policy, not by a promise from us.
Who can delete a record?
Ordinarily nobody. When erasure is legally required, it needs a second administrator who has just signed in again, and it adds a redaction to the history rather than removing it silently. Agents cannot request it.
What could still go wrong with the record?
Someone controlling both the database administrator account and the separate archive administrator account could destroy or rewrite records without being detected. Closing that gap would need an outside notary, and we do not have one.
Do you have a SOC 2 report?
Yes: SOC 2 Type 2, and we are HIPAA and GDPR compliant. Ask us for the report and for anything else your review needs.