Data-retention schedule
For each category of data, how long we keep it and what triggers its deletion. No indirection — the schedule itself, reconciled with our account-closure deletion window.
Last updated 21 November 2026
Retention by category
| Data category | Retention period | Deletion trigger |
|---|---|---|
| Inventory state (current identities, role assignments, consent state) | Until the next sync | Replaced on each sync; fully removed on account deletion |
| Findings (UPR scores, recommendations) | Recomputed each sync; history per tier | Superseded on recompute; removed on account deletion |
| Activity-log evidence (Azure ARM) | Per-tier window — see /pricing | Rolls off at the tier window; removed on account deletion |
| Sign-in metadata (Entra ID sign-in activity) | Per-tier window — see /pricing | Rolls off at the tier window; removed on account deletion |
| Audit logs (admin actions, sync history) | Indefinitely | Kept after deletion as a security record. User links, free text and other personal details removed on erasure. Entries written before this change keep the user's email and directory ID. |
| Billing & tax records (invoices, Stripe identifiers) | As required by law | Survives account deletion — retained to meet legal and tax obligations |
| DPA-acceptance records | Retained for accountability | Survives account deletion — a minimal record that processing terms were accepted |
| Closure record | Indefinitely | Survives account deletion. Domains removed on request to privacy@permafrostepm.com |
Tier-specific numeric windows for logs and findings are published at permafrostepm.com/pricing. The categories and triggers above are canonical here.
What happens when you close your account
On account closure your access is suspended and a 30-day frozen deletion window opens. You can request immediate deletion at any point in that window. At the end of it, all customer-scoped data is erased.
The records marked in the table as surviving deletion are kept. Billing and invoice records are kept for legal and tax obligations.
When an account is closed and its data erased, we keep a closure record. It holds whether the account was hosted or self-hosted, a primary domain (for hosted accounts, the default domain of the earliest connected tenant that has one; for self-hosted, the registration email's domain), the default domains of its connected tenants, the number of tenants, the deletion date, whether the customer, Permafrost or an automatic process started the deletion, and a reason category. The record holds no names, email addresses or postal addresses. We keep it indefinitely as a record that the account existed and was closed. To have the domains removed, write to privacy@permafrostepm.com. We remove them all together and log it.
We keep the audit log indefinitely as a security record. Entries for actions by Permafrost staff keep the staff member's ID, email, IP address and browser string.
When an account is erased, entries for its users' actions keep the action, the time, and technical details such as record IDs, counts and page paths.
The link to the user is deleted, and free text and other personal details are removed.
Entries written before this change took effect still hold the user's email address and directory ID in the fields the log's integrity check covers. We do not change those fields.
This mirrors the deletion window in our Terms of Service.
Related
What we read & why
The categories above, with the purpose for reading each one.
Related
Privacy Policy
The full policy this schedule is the canonical retention source for (§5).
If you run Permafrost yourself
You own your database and its retention, backups and deletion. Licence enforcement never deletes data in your database. The hosted retention schedule describes data held by the hosted service. Read about self-hosted Permafrost.
