Isolation in the database
Tenant separation is enforced where the data lives, so no screen can skip it.
Data isolation, permissions, approvals and audit built into the platform, not bolted on.
AI enforces who can see and change what in the database itself, so every screen, report, export and AI answer follows the same rules. Sensitive changes need a second person, every important action is recorded, and AI can be limited or stopped. This page describes controls that exist in the product; it makes no claim about third-party certifications.
Tenant separation is enforced where the data lives, so no screen can skip it.
Makers cannot check their own work, including through delegation.
The audit log refuses updates and deletes from every role.
Kill switches halt agents and in-flight model calls.
Destroying a person's key erases their sensitive data.
Search or filter. Planned items are labelled; everything else is available now.
Each company's data is separated by the database, not just by application code.
6 featuresFine-grained rights per hub, role, field and record.
11 featuresSensitive changes need a second, different person.
7 featuresStrong identity with controls you can tune.
7 featuresA trustworthy record of who did what.
6 featuresRespect data subjects and lawful basis.
7 featuresEven the vendor and AI work within limits.
9 featuresContinuous detection and proof.
5 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to Security & Trust.
Security-sensitive configuration, SoD waivers, support access and agent approvals route through the shared workflow with separation of duties.
Access, sign-in and agent activity are available as governed datasets.
Datasets
Dashboards
Audit entries, users and roles are readable over the API; sign-in and provisioning use standards.
/v1 audit entries, platform users and roles
Events
Connectors
Not applicable.
Remote wipe, device vault, certificate pinning and biometric re-lock protect the app; see the Mobile page.
By row-level security enforced in the database, backed by automated isolation tests.
No. Sensitive fields stay hidden until explicitly granted, and support access is time-limited, approved and logged.
No. AI acts as the signed-in person with field exclusions you set, and hidden fields are never sent.
Not by any role. Updates and deletes are refused.
This page makes no certification claim. Ask for current attestations.
No. Approval and sensitive changes need a different person.
Yes for sealed sensitive data, subject to legal holds and open disputes.