Last updated 29 August 2026
You can remove your data from Rigel at any time. This page explains the three routes — disconnecting an advertising account, deleting your Rigel account, and sending us a written request — and exactly what each one removes. No sign-in is required to read it.
Use this when you want Rigel to stop reading a connected ad account and to delete what it retrieved from it, while keeping your Rigel account.
This immediately deletes the stored access token, removes the mapping between the ad account and your workspace, and stops all further retrieval. Data already retrieved from that account is deleted on the schedule in the table below.
If you are the sole owner of a workspace, deleting your account also deletes that workspace and everything in it. If a workspace has other owners, transfer ownership first or it will be retained by them. Deleting your account revokes every active session and every provider connection you made.
While Rigel is in pre-release, self-service account deletion may not yet be available in your workspace. If you do not see the option, use Route 3 — a written request is handled manually and reaches the same result within the same 30-day window.
Email [PRIVACY CONTACT EMAIL] from the address on your Rigel account, with the subject Data deletion request. Tell us whether you want:
We may ask one question to confirm you control the account before acting. We complete verified requests within 30 days and email you a confirmation when the deletion is done.
Disconnecting in Rigel deletes our copy of the token. To additionally remove Rigel's authorization on Meta's side:
Doing this alone stops Rigel from retrieving anything further, but it does not tell us to delete what we already hold — for that, use one of the three routes above.
| Data | When it goes |
|---|---|
| Advertising platform access tokens | Immediately on disconnect or account deletion |
| Ad account, campaign, ad set, ad and creative records | Within 30 days of the request |
| Performance metrics and normalized analytics | Within 30 days of the request |
| Raw platform responses held for troubleshooting | Within 30 days of the request, and in any case within their own 30–180 day retention window |
| Uploaded CSV import rows and import records | Within 30 days of the request. The uploaded file itself was never retained past parsing |
| Account profile, workspaces, members, invitations, settings | Within 30 days of account deletion |
| Sessions and sign-in history | Sessions immediately; history within 30 days |
| Backups containing the above | As backup media rotate, within [BACKUP ROTATION WINDOW] |
The security audit log. Rigel keeps an append-only record of security-relevant actions — who did what, to what, when, and with what result. It is enforced as append-only at the database itself, so it cannot be edited or deleted on request, including by us. This is deliberate: it is the record that would show whether anyone misused your data, and it would be worthless if it could be erased on demand. It holds identifiers, actions and timestamps. It does not hold your advertising data, your credentials or any access token.
Invoices and financial records. Retained for as long as tax and accounting law requires.
Both are minimized, access-controlled, and never used to rebuild a deleted account.
Anything unclear, or a request that does not fit the routes above: [PRIVACY CONTACT EMAIL]. Our full Privacy Policy explains what we collect and how long we keep it.