Erase a member on request

When someone in your community asks you to delete their data, you erase their member. Everything that identifies the person is deleted, and the member becomes an anonymous ID that keeps the points, completions and rewards it earned, so your totals, leaderboards and other members' referral rewards stay as they were.

You decide when to erase. Your organization is the controller of your members' data and Domino processes it for you, so a person asks you, not Domino, and there is no "delete my data" button for members. Erasing can't be undone.

Before you erase

Erasing waits while the member has something you still need to decide:

• An attempt waiting for a decision: one still being evaluated, or waiting for review. Approve or reject it first.
• A reward handover in progress: finish or cancel the handover first.
• Another member's attempt waiting for a decision with the same photo: decide it first, since that photo is deleted from both.

Erasing then refuses and changes nothing, and says which it waits for.

Erase the member

Erasing needs the Publish permission, and works in live and in test. Give a reason: it's recorded in the audit history and kept, so write why (for example, "Deletion request of 3 March") and leave out the person's name, email or handle.

In Console:

1. Open Members and select the member.
2. At the bottom of the member, select Erase member.
3. Read what is deleted and what is kept, type the reason, and type the member's display name (or its ID, if it has none) to confirm.
4. Select Erase member.

If an attempt still waits for a decision, Console shows why erasing waits and links to the member's attempts.

With the CLI:

domino members erase MEMBER --reason "Deletion request of 3 March"

The command shows what will happen and asks you to confirm. In a script, add --yes; without a terminal to confirm in, it refuses without --yes.

What is deleted

• Their profile: display name and avatar. An uploaded avatar leaves storage at once, or within the hour.
• Every way they sign in or are recognized: sign-in accounts, linked X, Discord, Telegram, Google, Apple and email accounts with their stored profiles and access tokens (Domino asks the provider to revoke the tokens), identities your app's login gave them, and their wallets.
• Their sessions: they are signed out at once.
• Their marketing consent and its history.
• Leaderboard aliases and their referral code.
• What they submitted: the photos, text, links and quiz answers of every attempt, and what Domino's checks read from them. Photos leave storage at once, or within the hour. Without an erasure, Domino deletes every member's submitted evidence 90 days after the decision unless your project keeps it longer; see how long evidence is kept.
• What their accounts posted: the stored text and content of every tracker record their accounts authored, such as their X posts and Discord messages. The records keep their counts, so quests and leaderboards that counted them stay as they are.
• Duplicate-photo fingerprints of their uploads, and what destination plugins (such as Klaviyo) remembered about them.

What is kept, with personal text removed

These stay, but the free text in them is removed or reads [erased]:

• Reasons people typed about the member: point adjustments, review decisions, withdrawals from quests and campaigns, cancelled redemptions, counter corrections, and a ban's reasons. A ban in force stays in force.
• The audit history of changes about the member, with names, handles, accounts and reasons replaced. An entry that also names another member, such as a referral, loses that text too.
• A test member's name.
• A member import's row for them loses the accounts and identity it named, and keeps your ref for the person. Reverting that import later passes over this member and changes nothing for them.

What stays as it was

Some identifiers stay because Domino needs them to keep a reward right:

• The Discord user ID on a Discord role reward the member earned, so Domino can still remove the role if you revoke that completion.
• A one-way fingerprint of a linked event pass, so the same pass can't be claimed twice.

The member ID and everything it earned: points and balances, completions, tier and badge awards, rewards and their deliveries, referrals in both directions, streaks, counters, leaderboard results, quest and campaign enrollments, and the attempts themselves with their decisions. Webhook deliveries already sent keep their bodies; no webhook event names a person, only the member ID.

Reading the member shows when it was erased, with no profile, accounts or identities. In Console, the members list, member search and the member's page show Erased member with its ID, and the page says when it was erased, by whom and why. The page keeps its points, completions, rewards and activity to read, and offers no changes, so it offers no ban either; a ban already in force still shows.

After erasing

• Nothing new reaches the member. Points, badges, group and campaign changes, consent and profile changes naming the erased member are refused, and records that name its ID count for no one.
• If the same person comes back, signing in makes them a new member with no history.
• Backups and logs age out. Database backups keep the erased data for up to 14 days, and Domino's workflow history keeps it for up to 3 days, before it is gone everywhere.
• Your own copies are yours to delete. Domino doesn't tell your app, webhooks or destinations (such as Klaviyo) that a member was erased. If you keep member data there, delete it there too.