NineAuthDocs
GuideData Governance

Hard-Delete Application & Snapshots

Understand what happens during an application hard-delete, cascade cleanup guarantees, and how historical snapshots in application_snapshots preserve regulatory audit trails.

Hard-Delete Cascade Cleanup

Executing a hard-delete permanently purges the following entities associated with the application ID:

  • Active sessions and device bindings.
  • End-user credentials and password hashes.
  • License keys and custom entitlements.
  • Webhook delivery logs and active subscription links.

Immutable Snapshots in application_snapshots

Before irreversible deletion occurs, NineAuth writes a cryptographically sealed JSON snapshot into application_snapshots:

snapshot-schema.json
{
  "application_id": "app_9f8a3b...",
  "deleted_at": "2026-08-22T23:30:00.000Z",
  "deleted_by_user_id": "usr_adm_109283",
  "meta_summary": {
    "total_users_purged": 1420,
    "total_licenses_purged": 350
  }
}
Audit Compliance
Snapshot records are strictly read-only and preserved for legal compliance and accounting verification.
Concept: Application Tenant Isolation →
Read about application boundary rules and secrets.
Management: Applications API →
Inspect the DELETE /v1/mgmt/applications/:id endpoint.