Last Updated: September 17, 2026
BeanPool has no central account server. Your identity is a cryptographic keypair held on your own device, and your data lives on the community nodes you chose to join. That shapes how deletion works: most of it you can do yourself, immediately, from inside the app.
If you connected a publishing account so your public posts appear in your community's Pulse feed, there are two levels of removal.
In the app: Settings → Channels & showcase, find the platform card, and tap Disconnect.
This immediately deletes the platform access token from your device and clears the channel's verified status on the node. No further posts are retrieved. Posts already listed in the feed remain visible until you delete them or the channel, or until newer posts from the same channel push them out under the retention limit described below.
In the app: Settings → Channels & showcase, open the platform card, and tap Delete.
This is the complete removal. The node immediately scrubs the channel record and every feed item imported from it — the post URLs, titles, captions and thumbnail URLs are overwritten to NULL in the database, not merely hidden. What remains is each item's identifiers (the platform name and the platform's post identifier, and your member public key), its publication date and category, and timestamps, which exist only so that other nodes replicating the deletion converge on it.
The node also keeps a cached copy of each post's preview image so the feed loads quickly. It stops serving those images the moment the channel is deleted. Each cached image file is then removed from the node's disk the next time it is requested, or when it is displaced from the size-limited cache (100 MB per node). Deleting an individual post from the feed removes its cached image immediately.
Independently of anything you do, the node keeps only the 20 most recently published items from each channel. Older items beyond that are pruned automatically, with the same scrubbing applied. Items are not removed on age alone, so a channel that stops posting keeps its last 20 items until you delete them or the channel.
In the app: Settings → Reset / Wipe Identity, and confirm by typing your callsign.
This erases the identity keypair from your device and, on the community node, scrubs your profile: your callsign, avatar, bio and contact details are cleared, your listings are cancelled, and your member record is reduced to an anonymous placeholder. Connected channels and every feed item imported from them are scrubbed in the same operation, so deleting your account also removes your syndicated Instagram or TikTok posts. Their cached preview images stop being served at once and are cleared from the node's disk as described in section 1.
Any remaining balance is settled to your community's Commons Pool, since a mutual credit ledger has to stay in balance when a member leaves.
For the same reason, ledger entries recording trades between you and other members are retained in the community's transaction history. Those entries are what keep other members' balances correct, and erasing them would silently alter the record of trades other people made in good faith. They carry no profile data once your account is purged.
One condition: the node will refuse to purge an account with a trade still in escrow or a cross-node settlement in flight, because doing so would strand the other party. Complete or cancel those first, then purge.
Deleting data held by BeanPool is separate from revoking the authorisation you granted the platform. You can do that on the platform directly, and we recommend doing both:
If you no longer have access to your device or your identity keypair, you cannot authenticate to the node, and the in-app routes above will not be available to you. In that case, email admin@beanpool.org with the community node you joined and the callsign or platform username you used.
We will action verified requests within 30 days. Please note that each community node is operated independently; where a node is run by a local operator rather than by us, we will pass your request to that operator and confirm to you when it has been actioned.
Section 6 of our Privacy Policy sets out exactly what is stored when you connect a publishing account, and what is not.