Exporting data and closing an account or organization
Create portable personal-account or organization data exports as verified browser downloads, and understand the separate, recoverable process for closing a personal account or an organization without silent record loss.
Before you begin
- A signed-in and verified account.
- Organization ownership for organization-wide export or closure.
- A replacement owner before the only owner leaves a shared organization.
- Review of active support, billing-readiness, and retention notices.
Interface walkthrough
These annotated interface maps describe the current PMA controls. They do not replace a real record review in your workspace.
Separates personal account data from organization records and prepares the selected export directly in the signed-in browser.
Shows the audit state for each export. A blocked export can be retried from the same page; completed exports were delivered to the browser and are not stored as permanent public links.
Explains which identity or workspace is affected before a destructive request can be scheduled.
Preserves a controlled period in which an authorized request may be cancelled before permanent processing.
Step-by-step workflow
Choose the correct export scope
Use personal export for your account identity, PMA profile/preferences, memberships, policy decisions, request history, beta lifecycle history, and customer-visible support history. Use organization export for the workspace's collection records.
Prepare the browser download
Select the export in Data & Privacy. PMA prepares it in the current signed-in browser: personal export is a JSON package; organization export is a PMA Vault records-only archive with integrity verification. Organization export requires the workspace owner.
Retry an interrupted export
If generation or browser delivery is interrupted, Request history marks the export blocked and offers a retry. Successful exports are marked completed after browser delivery; PMA does not create a permanent public download URL.
Resolve ownership before closure
An organization owner must transfer ownership or close the organization intentionally. Leaving an organization does not automatically delete it.
Type the explicit confirmation
Closure requests require a deliberate confirmation and are separate from ordinary sign-out, membership removal, or plan downgrade.
Use the recovery period
Review the scheduled action and cancel it before final processing when the request was accidental or circumstances changed.
Expected result
A successful personal or organization export downloads to the signed-in browser and is recorded as completed in Request history. Interrupted exports remain auditable and retryable. Closure requests retain their separate ownership safeguards and recovery status.
Safety boundaries
- Plan upgrades or downgrades never delete customer data.
- Personal account closure and organization closure are different operations.
- The final organization owner cannot leave without transfer or deliberate organization closure.
- Exports may contain sensitive husbandry, customer, health, or team information and must be stored securely.
- Immutable audit and legally required records may remain subject to the documented retention policy.
Troubleshooting
Organization export is unavailable
Confirm you are the active organization owner or another role explicitly permitted to request the export.
I only want to stop using PMA
You may sign out, remove optional notifications, or leave an organization when ownership permits. Do not request permanent closure unless that is your intent.
The closure request is already scheduled
Open Data & Privacy and cancel it during the recovery period. Contact support immediately if the cancellation control is unavailable.