Exporting your data
How to request a signed copy of what the platform holds about you, what it contains, how to download it and how to check its signature.
On this page
You can ask for a copy of the data the platform holds about your account. The copy is a signed JSON file, with a CSV form as well. The Export tab of Your data is where you request it and download it.
How long exports and other data are kept is on Retention and deletion. What is collected, and why, is on Privacy. This page does not repeat their numbers.
What the export contains#
The page lists it as: your profile, email addresses, credential metadata (never secrets), sessions, consents, memberships and your own audit events. In more detail the file holds:
| Section | What is in it |
|---|---|
| Account | Your account identifier, its kind and status, and when it was created. |
| Profile | Display name, username, bio, language, time zone, the address of your profile picture, and which email is primary. |
| Notification preferences | Your two optional email choices. |
| Email addresses | Each address, whether it is verified and whether it is primary. |
| Credentials | For each password, passkey, authenticator app or token: its kind, status, label and when it was created, last used and revoked. Never the secret itself. |
| Linked accounts | The provider and your identifier there, and when you linked it. |
| Devices | Each device's name, trust label and when it was first and last seen. |
| Sessions | Each session's device, sign-in methods, network address, approximate place, and its start, last activity and expiry times. |
| Consents | The apps you currently allow, with their scopes and when you allowed them. An access you already revoked is not listed. |
| Memberships | Each organization, its status and your join date. |
| Audit events | Your own events: when, what kind, the organization, how it relates to you, and your address. |
What it leaves out#
- Password hashes, authenticator secrets, recovery code hashes, passkey public keys, token hashes and session secrets.
- The detail inside each event, and what other people did on your account. Your events list only that something happened to you or that you did it.
- Anything about other people.
Limits#
Every list in the file is capped so the file stays a reasonable size. A section named truncated says which lists were cut, so a short list and a capped one can be told apart. In the CSV form that section is called truncated as well. If an account is so large that the file would be too big, the request ends as Could not be prepared.
Request an export#
- Open Your data in the account navigation, then the Export tab.
- If you have not confirmed a second factor recently, the tab says Confirm it is you to see this page. Confirm with a passkey or an authenticator code. On a session you opened with a passkey, Other ways to confirm also offers your Account password.
- Select Request a data export. The page says Export requested. It is prepared automatically, normally within 24 hours.
- Your request appears under Export requests as Being prepared. You are emailed when it is ready.
- When the state is Ready, download it. See the next section.
Requesting needs a second factor you used in the last 30 minutes. You can have one export at a time: while one is Being prepared or Ready, the request button is not shown, and the platform refuses a second request. The page then says Your export is being prepared. Check back in a few minutes. or An export is already available. Download it or wait until it expires.
Requesting sends a security alert email to your verified addresses.
An account that has only a password cannot export until it adds a second factor. See Security and passkeys.

- Request a data export. The list below it is empty until you make a request, and then shows each request and its state.
States of a request#
| State | What it means |
|---|---|
| Being prepared | The export is built automatically. |
| Ready | Shows Ready until, the end of the download window. The files can be downloaded. |
| Could not be prepared | It could not be built. You can request it again. |
| Expired | Its download window ended. You can request a new one. |
| Cannot be downloaded | The file can no longer be verified. Request a new export. |

- The state of the request, here Ready, with Ready until.
- Download signed JSON.
- Download CSV signature, next to Download CSV.
Download#
When the state is Ready, the row has Download signed JSON, and the two CSV buttons when a CSV was produced for that export.
| Button | File | What it is |
|---|---|---|
| Download signed JSON | export.json | The authoritative copy. |
| Download CSV | export.csv | The same data as spreadsheet sections. |
| Download CSV signature | export.csv.sig | A small file that signs the CSV. |
The list's footer says: "The signed JSON is the authoritative copy. The CSV carries no signature of its own; its hash is signed in the JSON and in the CSV signature file." and that downloading needs a second factor used in the last 30 minutes. If your confirmation is out of date, a Confirm it is you dialog opens instead of saving an error page as the file.
Each download is recorded in your activity as Data export downloaded, and appears in your security feed with a Review badge, so you can see whether anyone else fetched it.
The CSV#
The CSV is made of sections. Each starts with a line beginning # and the section name, then a header row, then the rows, then a blank line. Lines end in CRLF and the text is UTF-8. Cells that begin with a character a spreadsheet would treat as a formula are prefixed with an apostrophe, so opening the file in a spreadsheet cannot run anything.
Check the signature#
The JSON file is an envelope with four parts: its format name, your data under document, a signature, and a signing_key with the key's identifier and public key. The signature commits to a hash of your data, so any change to the file is detectable. The CSV signature file repeats the same signature and adds a hash of the CSV.
To check a file yourself, look up the signing key by its identifier in the platform's published key set rather than trusting the copy inside the file, then verify the signature over the hash of the data. You do not have to do this. It is there so that you, or an auditor you give the file to, can show the file is unchanged.
If the file can no longer be verified, the request moves to Cannot be downloaded, and you request a new export.
What can go wrong#
| What you see | What it means |
|---|---|
| Confirm it is you to see this page | The page needs a second factor from the last 30 minutes. |
| No Request a data export button | You already have one being prepared or ready. |
| Could not be prepared | Something went wrong while building it. Request again. |
| Expired | You did not download it within its window. Request again. |
| This export can no longer be verified and has to be requested again. | Request a new export. |
If you cannot sign in at all, Retention and deletion says how to reach the security contact.
Related#
- Activity
- Closing your account: export first, because after closing you cannot sign in to request one.