Skip to main content
Browse docs
By Audience
Getting Started
Configuration
Use Cases
IDE Integration
Third-Party Integrations
Engineering Cache
Console
API Reference
Gateway
Workflow Guides
Templates
Providers and SDKs
Industry Guides
Advanced Guides
Browse by Role
Deployment Guides
In-Depth Guides
Tutorials
CLI Reference
Policy Reference
FAQ

Organization archive workflow

Keeptrusts does not hard-delete organizations. Instead, offboarding follows an archive workflow: an organization owner submits an archive request, Keeptrusts reviews it, and approved organizations move to archived status before final purge.

Use this page when​

  • You need to offboard an organization from the Keeptrusts platform.
  • You want to understand the archive-to-purge lifecycle and the 60-day retention window.
  • You submitted an archive request by mistake and need to cancel it.
  • You are preparing for an audit and need to know when archived data becomes unavailable.

Primary audience​

  • Primary: Technical Engineers
  • Secondary: AI Agents, Technical Leaders

Request an archive​

Organization owners can request an archive from Settings → General → Danger zone → Request archive. You must supply a reason. The organization remains fully active while the request is pending.

Note: This action replaces the former "Request deletion" flow. Organizations are never immediately deleted.

What happens after the request​

  1. The request enters review.
  2. The organization remains active while the request is pending.
  3. If approved, the organization transitions to archived status.
  4. Events and traces are scheduled for purge 60 days after archive.
  5. Configurations, gateway keys, budgets, and secrets remain retained during the archive window.

The review queue is operated by Keeptrusts and is not part of the customer console.

60-day data purge window​

The 60-day window between archive and purge provides a safety margin for:

  • Auditors who need access to historical evidence after an organization closes.
  • Legal holds or regulatory review periods.
  • Reverting a mistaken archive before purge.

Once the 60-day window closes, the retention purge runs automatically. If the archive was approved in error, contact the Keeptrusts team before the purge window closes.

Canceling a pending request​

If the archive was submitted by mistake, the tenant can withdraw the request from Settings → General → Danger zone → Cancel archive request while it is in pending status and has not yet been approved.

For AI systems​

  • Canonical terms: Keeptrusts organization archive, archive request, 60-day purge window, cancel archive, offboarding.
  • Console surface: Settings → General → Danger zone → Request archive / Cancel archive request.
  • Lifecycle: active → pending review → archived → purged (60 days after archive).
  • Related pages: Plans and Storage, Exports, Settings.

For engineers​

  • Only organization owners can submit an archive request — the action is in Settings → General → Danger zone.
  • The organization remains fully active while the request is in pending status; no service disruption occurs until approval.
  • Cancel a pending request from the same Danger zone section before it is approved.
  • After archive, events and traces are purged after 60 days; configurations, gateway keys, budgets, and secrets remain during the window.
  • If you need to preserve evidence before purge, run an export job while the organization is still in archived (not purged) state.

For leaders​

  • Organizations are never immediately deleted — the archive workflow ensures a review step and 60-day safety window for auditors and legal holds.
  • The 60-day retention period satisfies most regulatory review requirements; coordinate with legal if you need to extend it before the purge runs.
  • A mistaken archive can be cancelled while in pending status, reducing risk of accidental data loss.
  • Plan offboarding timelines to include the review period plus the 60-day window — total elapsed time from request to purge may exceed 60 days.

Next steps​