Anonymize a membership

Erase everything that identifies a member, on an erasure request.

Studio roles: "Owner" and "Administrator", and Studio users with the permission set "Community: manage".

An anonymized organisation membership keeps nothing that identifies the person: no member code, no names, no claims, no groups and no holder. It is kept only for the transactions that refer to it. Anonymizing cannot be undone.

Anonymize now, on an erasure request

When a person asks your organisation to erase their data:

Open "Members directory" and choose the member.
Choose "Anonymize now".
Type the member code to confirm, exactly as the member page shows it.
Enter a reason. It shows in the history, so describe the request, not the person: for example, "Erasure request by letter of 30 October".
Choose "Anonymize now".

The Studio then, in one step:

deactivates the membership first, if it is active, with the reason "erasure request";
erases the member code, the names, the claims, the groups, the membership start and the holder;
deletes the member code's checks from the check log, also those of the ways the code can be typed that the rate limits count as one code, such as in lower case or with leading zeros;
empties the before and after values of the membership's history, keeping only what happened, who did it and when;
anonymizes the member's redemptions: those of the membership, and those of applicants without a membership who gave the same member code, also in a spelling that counts as the same code. It removes the names, the email, the birth date, the member code, the redemption office's note and the text of the message to the partner. The reference, the dates, the voucher offer, the partner, the code and the status stay, for your statistics and the settlement with the partner.

You land on the members directory, which no longer lists the membership. Choose "Anonymized" under "Status" to see it. Its page now shows only the status "Anonymized", its dates and what is left of its history, without a holder: "Anonymized", with your reason, and "Deactivated" before it.

If the member code has changed since you opened the page, or someone else anonymized the membership meanwhile, nothing is erased: the page reloads and shows the membership as it is now.

What anonymizing leaves alone

Register entries. They belong to your register and stay as they are. An entry cannot be deleted in the Studio: deactivate it, and clear what you need not keep by editing it.
The frontend user. The person keeps their frontend user, with their own names and email, and can still sign in to your frontends, just not as a member. If the request covers that account too, it has to be deleted on its own: anonymizing does not delete it. The other way round, deleting a frontend user does not anonymize their membership: it loses its holder, and the next person to onboard with its member code takes it over.
A new onboarding with the same code. The anonymized membership is never handed on. Whoever onboards with the old member code later gets a new membership.

Anonymize now, on an erasure request

When a person asks your organisation to erase their data:

Open "Members directory" and choose the member.

Choose "Anonymize now".

Type the member code to confirm, exactly as the member page shows it.

Enter a reason. It shows in the history, so describe the request, not the person: for example, "Erasure request by letter of 30 October".

Choose "Anonymize now".

The Studio then, in one step:

deactivates the membership first, if it is active, with the reason "erasure request";

erases the member code, the names, the claims, the groups, the membership start and the holder;

deletes the member code's checks from the check log, also those of the ways the code can be typed that the rate limits count as one code, such as in lower case or with leading zeros;

empties the before and after values of the membership's history, keeping only what happened, who did it and when;

anonymizes the member's redemptions: those of the membership, and those of applicants without a membership who gave the same member code, also in a spelling that counts as the same code. It removes the names, the email, the birth date, the member code, the redemption office's note and the text of the message to the partner. The reference, the dates, the voucher offer, the partner, the code and the status stay, for your statistics and the settlement with the partner.

If the member code has changed since you opened the page, or someone else anonymized the membership meanwhile, nothing is erased: the page reloads and shows the membership as it is now.

What anonymizing leaves alone

Register entries. They belong to your register and stay as they are. An entry cannot be deleted in the Studio: deactivate it, and clear what you need not keep by editing it.

The frontend user. The person keeps their frontend user, with their own names and email, and can still sign in to your frontends, just not as a member. If the request covers that account too, it has to be deleted on its own: anonymizing does not delete it. The other way round, deleting a frontend user does not anonymize their membership: it loses its holder, and the next person to onboard with its member code takes it over.

A new onboarding with the same code. The anonymized membership is never handed on. Whoever onboards with the old member code later gets a new membership.