Current public version published on the date shown.
AuraOne / Legal / Data deletion
Account and data deletion
How to request deletion of an Aura Capture or AuraOne account, what is deleted, what is retained and why, and how long each step takes.
Public version 1.0 · Effective October 10, 2026
Document record
- Version
- Public version 1.0
- Effective
- Effective October 10, 2026
Document summary
Overview
- How to request deletion of an Aura Capture or AuraOne account, what is deleted, what is retained and why, and how long each step takes.
- Security controls, data handling, and deployment governance for enterprise AI programs.
Request deletion in the app
Contributors can delete an Aura Capture account from inside the app without contacting support.
- Open Aura Capture and go to the Profile tab.
- Under Privacy and rights, select "Delete my account".
- The app shows the date the account will be deleted, where the request has reached, and the trace identifier for the request.
A deletion request enters a 30-day grace period. After grace the purge proceeds and cannot be reversed.
Request deletion without the app
Anyone who cannot access the app can request deletion by writing to [email protected] from the email address on the account, or through support. AuraOne verifies control of the account before acting on the request, which protects an account from deletion by someone else.
Verified requests are acknowledged within 30 days and follow the same grace period and purge sequence as an in-app request.
What is deleted
After the grace period ends, AuraOne purges the following from its own systems, including object storage and reviewer tooling.
- Account and profile information, including name, email address, and phone number.
- Captured media and its derived artifacts, including segments, embeddings, captions, and semantic index entries.
- Device and session records associated with the account, including push registration tokens.
- Support ticket content submitted from the account, except where an open legal matter requires retention.
Capture-object deletion and buyer or training recall are operator-assisted. They remain pending until per-object and per-recipient receipts are verified.
Deletion status is reported per destination rather than as a single claim, so a destination that is still processing or that failed is visible rather than reported as complete.
What is retained and why
Some records are retained after an account is deleted because law or an existing obligation requires it. AuraOne reports these as retained rather than describing them as deleted.
- Payout and transaction records, retained to meet tax and accounting obligations for the period the applicable law requires.
- Records under an active legal hold, retained until the hold is released. The deletion status reports these as blocked rather than deleted.
- Records inside a contractual retention window, retained until the window expires and then purged.
- Aggregate and de-identified statistics that cannot be re-associated with an individual.
Timing
Grace period: 30 days from the request. Purge and propagation begin when grace ends. Each destination reports its own progress, and slower downstream cleanup can finish after the purge starts.
Derived packages already delivered to a buyer follow the retention terms in the applicable agreement; the deletion record traces each delivery so the obligation is auditable.