Your account

Open Account from the Account menu beside Docs at the bottom of the sidebar, or in the header on small screens. It is also linked from the page shown when you have no open organisation. Only you can delete your account, in your own session; a staff member viewing or acting as you cannot.

To receive a copy of the personal data the hub holds about you, ask Common Measure; there is no self-serve export yet.

Deleting your account

Type your email address and choose Delete account.

What stops a deletion

If you are the only owner of an organisation that is still open, the hub refuses and names each such organisation. For each one, either:

• make another member an owner on Team, or
• close the organisation under Retention (Closing the account).

The hub never transfers ownership or closes an organisation for you. A closed organisation does not block the deletion.

What deletion ends

In one step, the hub:

• signs you out of every session, including any a staff member held while viewing or acting as you, and any you held as staff;
• revokes the clients you connected and deletes unused sign-in links. Refresh tokens stop at once. An access token already issued is checked by the hosted edge without asking the hub, so it keeps working there for up to an hour and a minute after it was issued;
• revokes every API key you minted by hand or revealed, and every edge enrolled for you, with its supplier authorisations. The edges stop signing and delivering;
• cancels enrolment tokens minted for you or by you that have not been used;
• replaces your whole email address with deleted account in the names of API keys, edges and enrolment tokens. An occurrence that could also be another account’s address, such as a quoted one when that account exists, is kept;
• deletes invitations sent to your address and revokes pending ones you sent. Invitations you sent that were accepted stay on the record;
• removes you from every organisation and deletes your email address, name and Google sign-in link.

Other members’ edges and API keys keep working, including edges enrolled from a token you minted for them.

What stays

• Audit records of what you did, custody records and Extension Studio history stay under your account’s internal identifier, a pseudonym. The email address they recorded is replaced with deleted account. Nothing in the hub links the identifier to your address or name. How long these records are kept is stated in the hosted service’s terms once those exist; the hub does not delete them on a timer.
• Signed registration records (instance bindings) carry that identifier inside their signature and stay unchanged as long as the custody record they belong to, so they still verify.
• Organisation data such as policy, reports and telemetry belongs to the organisation and stays with it.
• Backups: a copy can remain in a database backup for up to seven days after the deletion, until that backup expires. Before the first outside user, a restore from backup is a reset, not a replay.

Suppliers and edges

The confirmation page and the answer to the deletion list the supplier connections you created or that were authorised to your edges. After the deletion you are signed out and the list is shown once; note it before leaving the page. Each supplier holds its own records of that account under its own terms; ask the supplier to delete them. A connection you created stays with its organisation: if its credential is your own supplier account, ask an owner to rotate or revoke it, or rotate it at the supplier.

Records on an edge belong to the edge’s operator. An edge your organisation runs may keep your hub user id (an opaque identifier, not your name or email address) in its access policy and in its records of requests made with your access. Deleting your hub account does not remove them from the machine.

API reference

Request	Answer
GET /api/v1/account/deletion	email, last_owner_of (the organisations that block the deletion), suppliers (organization, provider, label, connected_by_you, kept; label is null on a connection someone else made)
POST /api/v1/account/delete with {"email": "…"}	200 {"deleted": true, "suppliers": […]} and a cookie that clears the session; 409 {"code": "last_owner", "organizations": […]}; 400 if the address does not match

Both need your own browser session; an API key is refused. A repeated request after the deletion answers 200 with already_deleted and changes nothing.