Data Retention & Deletion Policy
How long each kind of data is kept, what deletes it, and how customers get their data removed.
| 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 |
Principle
Data is kept only as long as it is needed to provide the service, meet a legal duty or investigate a security event, and is then deleted. Where PersivX does not delete something automatically, the period below is enforced by a scheduled cron job on each server.
Retention Schedule
| Data | Kept for | How it is deleted |
|---|---|---|
| Sign-in sessions and API tokens | Until they expire or are revoked, then 30 days | purge_auth_tokens, run daily by cron |
| Account setup and password reset links | 7 days (setup) or 30 minutes (reset), then 30 days | The same job |
| Activity log (sign-ins with network address and browser, report activity, delivery history) | Indefinitely | Not deleted |
| Security log file or syslog | 12 months | The server's log rotation: logrotate, weekly, keeping 52 weeks |
| Geocoding cache (place names to coordinates) | 1 month after last use | Automatic |
| Deleted reports | In Trash until restored or removed | Not removed automatically. The user or an organization admin empties Trash. |
| Report images and files sent to the public upload server | 30 days | Not deleted by PersivX. A daily cron job on the upload server deletes older files. |
Report screenshots for emails (assets/mail/) | 30 days | A daily cron job deletes older files. |
Datasource copies and query cache (datasets/, cache_query/) | While the organization is a customer | PersivX has no way to delete a datasource, so these are removed with the organization's data (below) |
| Pre-upgrade password hashes | Until the upgrade is confirmed | purge_legacy_password_hashes --yes, run on each server right after a successful upgrade |
Database backups made from inside PersivX (datasets/dumps/) | 30 days | Not deleted by PersivX. A daily cron job deletes older files. |
| Backups | 30 days | See Backup & Business Continuity |
When a Customer Leaves
When a contract ends, the customer can export their reports first (Export & Import). As soon as the customer asks, Persiv then deletes the organization's data from Persiv-run servers: database rows, its folder under datasets/orgs/, published report versions and cached files. Backups holding it expire on their normal schedule, within 30 days. Persiv confirms the deletion in writing.
Requests About Personal Data
A request to see, correct or delete a person's data is sent to support@persivx.com and answered within 7 days. An organization admin can block a user's account at any time, which ends their sessions immediately. Removing the account and its personal data is done by Harsh Jain or Ankit Kumar, and the request and its outcome are recorded.
