
How to enable
Account deletion is available from the Close account page in member profiles. There is no separate toggle — if you want to prevent deletions, enable the Resignation module, which adds an approval gate before deletion becomes available.What the member sees
Path: Profile → Settings & Privacy → Close accountHow deletion works (with and without resignation)
If Resignation is enabled (recommended)
Members must resign and get approved before the delete option becomes available. This gives you two safeguards:Member can now delete their account
The Delete account button becomes active. They click it and confirm.
If Resignation is not enabled
Members can delete their account directly — one click and confirm. No admin approval, no reason captured, no opportunity to intervene.What data is kept vs removed
| Data | After deletion |
|---|---|
| Profile information (bio, photo, custom fields) | Permanently removed |
| Member directory listing | Removed — they no longer appear in search |
| Activity history (posts, comments, event attendance) | Removed or anonymized |
| Roles and permissions | Removed |
| Group and event memberships | Removed — their slot is freed |
| Name | Retained for legal records |
| Payment/transaction records | Retained for financial compliance |
Admin notifications
When a member deletes their account:- Administrators receive a notification
- The deletion is logged for compliance records
- The member’s slot in any groups, events, or waitlists is automatically freed
Common scenarios
A member deleted their account by mistake — can I restore it?
A member deleted their account by mistake — can I restore it?
No. Deletion is permanent and irreversible. The member will need to register again from scratch. This is why the confirmation step exists — and why enabling Resignation as a prerequisite is recommended (it adds a cooling-off period).
A member wants to leave but keep their data
A member wants to leave but keep their data
They should resign without toggling “Close my account”, or ask an admin to set their status to Inactive. Both options preserve their data while formally recording the departure.
I need to delete a member's account on their behalf (GDPR request)
I need to delete a member's account on their behalf (GDPR request)
If a member contacts you requesting data deletion but can’t do it themselves, an admin can access their profile and process the deletion. Document the request for your compliance records.
What if a member has unpaid fees?
What if a member has unpaid fees?
Their payment records are retained after deletion for financial compliance. Outstanding fees should be resolved through your normal billing process — account deletion doesn’t cancel debts.
Should I use deletion or just set them to Inactive?
Should I use deletion or just set them to Inactive?
Use Inactive when the member might come back, or when you want to keep their history for reporting. Use Deletion when the member explicitly wants their data removed (GDPR), or when you’re cleaning up abandoned accounts. When in doubt, use Inactive — it’s reversible.
GDPR compliance
Account deletion directly supports the right to erasure (GDPR Article 17):| GDPR requirement | How Orgo handles it |
|---|---|
| Members can request data removal | Self-service Delete account button |
| Data minimization after deletion | Only legally required data retained (name, payment records) |
| Admins are informed | Notification sent on deletion |
| Audit trail | Deletion event logged for compliance |
Related
- Resignation — Formal departure process (recommended prerequisite)
- User Statuses — Reversible alternative: Inactive or Suspended
- Privacy Settings — Control data visibility (less extreme than deletion)

