social.grain.server.deleteAccount
Deletes the asking account's grain data a part at a time, as knotless's dev.knotless.deleteAccountData does. Asked by the web's session cookie, from a page of the site, it deletes the account's records in every social.grain.* collection at its PDS with the session grain keeps for it, up to `limit` records a call, and answers whether it is done; the web asks again until it is, and a run cut short carries on where it stopped. Once nothing is left, grain drops what it indexed from the account, as for one deleted at its PDS, with its preferences, notification state, push tokens, mutes, story views and space invitations, keeping its takedowns, the labels given out and the reports about it; and it ends the account's web session, revoked at its PDS, logging the browser out of it. Asked with a service token, as the apps ask once they have deleted the records at their own PDS, committing the plans social.grain.server.getAccountDeletionPlan answers until one comes back empty, it deletes nothing, and forgets the account only once its PDS lists no social.grain.* collection. The atproto account itself, and other apps' records in it, a Bluesky cross-post among them, are untouched. Only the account itself can ask.
Details · procedure
| Kind | procedure |
|---|---|
| Authority | server.grain.social |
| Commit rev | 3n2ui2e6oubxx |
| Indexed |
Procedures don't store records of their own, so there is no record activity to show.