Data Protection & Encryption Policy
What kinds of data PersivX holds, how each is protected in transit and at rest, how customers are kept apart, and how encryption keys are looked after.
| Policy owner | Persiv Technology |
|---|---|
| Approved by | Harsh Jain and Ankit Kumar |
| Effective from | 1 November 2026 |
| Reviewed | At least once a year, and after any significant change or incident. Next review: 1 November 2027 |
Data Classes
| Class | Examples | Handling |
|---|---|---|
| Secrets | Datasource passwords and API keys, server settings, encryption keys, two-step secrets | Encrypted or hashed at rest; never shown back in the browser; never in source control or tickets |
| Customer data | Data read from datasources, uploaded files, reports, visuals, comments | Kept to its organization; reaches outside services only as listed in Vendors |
| Personal data | User names, emails, sign-in times, network address and browser of each sign-in | Kept for the periods in Retention; deleted on request |
| Internal | Source code, internal documents | Access limited to Persiv Technology employees |
In Transit
- All traffic to PersivX is served over HTTPS (TLS 1.2 or later). On a production server (
ENV=prod) PersivX redirects plain HTTP to HTTPS and sends HSTS for one year by default, so browsers refuse plain HTTP afterwards. - Connections from PersivX to databases and APIs use TLS wherever the source supports it. The only exception is an on-premises database reached over a private network.
- Report pages carry a Content Security Policy that blocks inline script, and only the sites a customer lists may embed a report in a frame.
At Rest
- Datasource secrets (passwords, keys, tokens) are encrypted in the database with the installation's
DATASOURCE_SECRETS_KEY(Fernet: AES-128 with HMAC). The browser receives a placeholder, never the stored value. - User passwords are stored as bcrypt hashes (cost 12). Sign-in, setup and reset tokens are stored only as hashes. Two-step verification secrets are encrypted with a key derived from the server's
SECRET_KEY. - Disks. Database and file storage on Persiv-run servers is encrypted at the disk or volume level by the cloud provider's default encryption at rest.
- Backups are encrypted, as set out in Backup & Business Continuity.
Keeping Customers Apart
- Each organization's files live in their own folder (
datasets/orgs/<id>/), and withWORKSPACE_ISOLATION=enforce(the default) a request's in-memory queries can read only its own organization's folders. - Every request that names a report, visual, datasource or other object is checked against the caller's rights and organization. Changing an id in a request doesn't reach another customer's content.
- Python written by report authors runs only in a throwaway container with no network, a read-only file system and an import allowlist. It is off unless the operator turns it on (
ALLOW_USER_PYTHON_CODE). - Addresses users can set (API datasources, webhooks, flow triggers) are fetched through a guard that refuses the server's own address and cloud-metadata addresses, and private networks unless the operator allows them. Persiv-run multi-tenant servers set
ALLOW_PRIVATE_NETWORK_TARGETSto0. - Answers written by AI are shown in a sealed frame that can't reach the user's session.
Data Sent to AI
AI features send report data to the AI provider listed in Vendors. They are off by default for a new organization, and every AI request checks both that the organization allows AI and that the user holds an AI licence, including scheduled and server-side runs.
Key Management
- Keys and secrets live only in each server's settings file (
.env), readable only by the account that runs PersivX. They are never committed to source control; every push is scanned for secrets. - Each installation has its own keys. Keys are never reused between customers or between test and production.
- Keys are rotated every 12 months, when someone who knew them leaves, and immediately if exposure is suspected. Rotating
SECRET_KEYrequires every user to set up two-step verification again; rotatingDATASOURCE_SECRETS_KEYmeans re-encrypting stored credentials withencrypt_datasource_secrets. Losing that key means re-entering every datasource credential, so it is backed up separately from the database. - Secrets found in older source history are treated as exposed and must be rotated. Status: the licence-signing key and the Google service-account keys have been rotated.
