Security & Compliance
How PersivApps protects tenant data — isolation, access control, audit logging, encryption, and monitoring.
📋 SOC 2 Certification Status
PersivApps is built around SOC 2-aligned controls — the access control, audit logging, encryption, and monitoring practices on this page are live in the product today. We have not yet completed a third-party SOC 2 audit; formal Type II certification is in progress. Ask your PersivApps contact for our current security documentation and certification timeline.
Data Isolation
PersivApps is multi-tenant by design. Every organization's data — smarttables, entries, users, roles, and attributes — is scoped to that organization at the database level. There is no cross-tenant query path in normal application use.
Access Control
| Control | Description |
|---|---|
| Role-Based Access Control | Organization-scoped roles (System Admin, SmartTable Admin, User) with per-smarttable access grants, managed in Access Management |
| Entry-Level Access Control | Optional finer-grained rules per entry — restrict by creator, matching user attribute, specific users, or attribute value. See Access Management |
| Field-Level Visibility | Accordion sections within a smarttable can be restricted to specific users |
| Folder-Based Access | SmartTables can be grouped and access managed as a unit; see Folders |
| License Controls | Admins can suspend ("hold") or revoke a user's login without deleting their account or history |
Authentication
- Token-based authentication (JWT) — short-lived access tokens (24 hours) and rotating refresh tokens (30 days)
- Passwords are hashed, never stored in plaintext
- Multi-Factor Authentication (MFA) — optional TOTP-based two-factor login using any standard authenticator app (Google Authenticator, Authy, etc.). Once enabled on an account, a 6-digit code from the app is required in addition to the password at every login.
- Self-service password reset via emailed, time-limited link, plus admin-initiated resets
- Rate limiting on login and other sensitive/anonymous endpoints to reduce brute-force and abuse risk
Audit Logging
Every meaningful action is recorded — creates, updates, deletes, submits, attestations, approvals, and logins — with the acting user and structured detail, queryable per entry and per smarttable.
🔒 Tamper-Evident by Design
Beyond the queryable audit log, every event is also mirrored to a separate append-only log file. On supported deployments this file is hardened at the operating-system level so that even a compromised application process cannot rewrite or delete historical entries — only append to them.
Automated Security Monitoring
A recurring monitoring job watches for signals that typically precede or accompany an account compromise, and emails administrators when it sees:
- Account lockouts
- Password reset requests
- Failed logins across multiple usernames from the same source (a common credential-stuffing pattern)
- License revocations
- Organization deletions
Data Protection
| Control | Description |
|---|---|
| Encrypted Backups | One-click organization backup, encrypted with AES-256 and RSA key wrapping, delivered as a downloadable archive |
| Versioned Schemas | SmartTable schema changes are versioned rather than overwritten — historical entries stay linked to the schema version they were created under |
| Soft Delete | Entries are soft-deleted by default (recoverable) before any permanent deletion |
⚠️ Scope of This Page
This page describes technical controls implemented in the product. It is not a substitute for a signed audit report, penetration test, or your own security review. For enterprise procurement, request our current documentation directly rather than relying solely on this page.