Skip to content
Trust Center
Retention

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 27 June 2026

Retention by category

Retention period and deletion trigger by data category
Data categoryRetention periodDeletion trigger
Inventory state (current identities, role assignments, consent state)Until the next syncReplaced on each sync; fully removed on account deletion
Findings (UPR scores, recommendations)Recomputed each sync; history per tierSuperseded on recompute; removed on account deletion
Activity-log evidence (Azure ARM)Per-tier window — see /pricingRolls off at the tier window; removed on account deletion
Sign-in metadata (Entra ID sign-in activity)Per-tier window — see /pricingRolls off at the tier window; removed on account deletion
Audit logs (admin actions, sync history)Lifetime of the accountRemoved on account deletion (after the 30-day window)
Billing & tax records (invoices, Stripe identifiers)As required by lawSurvives account deletion — retained to meet legal and tax obligations
DPA-acceptance & deletion-audit recordsRetained for accountabilitySurvives account deletion — a minimal record that processing terms were accepted and that deletion occurred

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.

Two narrow categories survive that erasure, both noted in the table: billing and invoice records, retained to meet our legal and tax obligations, and a minimal audit record of the deletion itself, kept for accountability. Everything else tied to your account is removed. This mirrors the deletion window in our Terms of Service.