Guides

Export your data, delete your account

Taking everything out, and the delete that means it.

Export

tigby export start --out tigby-export.zip

One archive of everything Tigby holds for the Org: a manifest, the account as JSON, and per Identity the Mailbox as mbox with a byte-offset manifest beside it. The mbox is the whole mailbox, not the Inbox the REST read shows – Junk, Trash, Drafts and Sent included – and each entry in the manifest names the folder its message was in. --identity @orderbot narrows it to one Identity; an Identity Key exports its own without asking.

Vault values stay out unless --include-secret-values says otherwise – Org scope only – and the manifest says which it was either way.

The archive is built asynchronously (--wait sits until it is ready, tigby export list shows every run), sealed under the Org's own key while it waits, and deleted when it expires. Export is self-serve Art. 15 and 20 – no ticket, no support queue.

Delete an Identity

tigby identity delete @orderbot

Tears down everything the Identity owns – keys first, then Connectors (revoked at the platform), Tunnel, Mailbox, card. The Handle stays reserved for all time; nobody inherits a mail address that once received your mail.

Delete the account

tigby export start --out everything.zip   # first, if you want the data
tigby account delete anna@example.com

Art. 17, and the end of everything: every Identity in turn, then the account itself, its Vault key with it. Confirmed by typing the account's own email address, irreversible, and every credential stops working the moment it is accepted. A deletion survives even a backup restore: the record of it is replayed, and the data deleted again.