Security & data handling
Last updated August 2026
Periance maintains a reconciled model of your operational state. That requires reading from the systems you connect — so how we read, store, and isolate that data is the product. This page states exactly how.
Read-only by default
Periance observes; it does not change your systems. Connectors request least-privilege read scopes only. The single exception is an actionyou explicitly approve (for example, revoking a former employee’s access) — which requires a separate, explicit write authorization at the moment you run it, and is recorded in full.
We don’t store your provider tokens
OAuth connections are established and vaulted by Nango; Periance stores only a connection reference, never the raw token. Token-based and public connections store a non-sensitive hint, never the secret. Disconnecting an integration revokes the vaulted credential.
Tenant isolation
Every record is scoped to one organization and enforced in the database with Postgres Row-Level Security: a tenant-scoped read policy on every table and a role-scoped write policy. Coverage is verified by an automated check across all org-scoped tables (npm run verify:rls) — 0 cross-tenant leaks. The most sensitive table (connection references) is reachable only by the service role, never by any user session.
Evidence, not assertion
Every operational fact carries its source, when it was first observed, when it was last verified, and a confidence grade. Nothing in the model is taken on faith, and your provider data never reaches the language model beyond the bounded evidence slice the analyst needs to answer a question.
Access control & audit
- Role-based access: owner / admin / operator / viewer.
- Every mutation, connection, action, and AI query is written to an immutable audit log.
- Actions carry a full lifecycle record — proposed, approved, executed, and verified.
Your data is yours
You can disconnect any integration at any time (which revokes its vaulted token), and an organization owner can permanently delete the organization and all of its data from Settings — one action that cascades across every record. There is no soft-retention.
Architected for SOC 2
We are not yet SOC 2 certified and don’t claim to be. The controls above — least privilege, token vaulting, tenant isolation, audit logging, and data deletion — are built as the foundation that certification formalizes. If you have specific security requirements for an early engagement, contact us.