Configure how long departed member data is retained before anonymization, and understand how Sellfaster handles historical records for team members who have left.
When a team member leaves — either by being removed from the team or by deleting their personal account — Sellfaster does not immediately erase their data. Instead, it schedules anonymization after a configurable retention period. During this window, historical records (interactions, sales, activity feed entries) continue to display the departed member's name correctly, clearly marked as departed.
This approach balances two needs:
The Member data retention period setting is part of the GDPR Settings page, which is accessible to team owners only.
/home/[team]/settings/gdpr| Setting | Default | Minimum | Description |
|---|---|---|---|
| Member data retention period (days) | 90 | 1 | Number of days after a member leaves before their personal data is anonymized |
Enter the number of days and click Save.
A value of 90 days means a departed member's name and personal data remain readable in historical records for 90 days after they leave. After that period, the anonymization job runs and replaces their data with anonymized placeholders.
Anonymization is scheduled automatically in two situations:
After the retention period expires, the following personal data is anonymized for the departed member:
The interaction and sale records themselves are not deleted — only the attribution to the specific individual is anonymized. Historical counts, timestamps, and business data remain intact.
While a member's data is within the retention window (i.e., not yet anonymized), their name appears in historical records marked as departed. Profile links for departed members are disabled throughout the app — clicking a departed member's name does not navigate to a profile page.
After anonymization, their name is replaced with an anonymized placeholder in all historical records.
Member retention is separate from the GDPR Customer Requests tools (Search, Export, Erase), which are designed for responding to data subject requests from customers (leads). If a former team member submits a formal erasure request under GDPR Article 17, use the GDPR Customer Requests → Erase flow rather than relying on automatic retention.
See GDPR Settings & Data Protection for the full GDPR toolset.
| Action | Required Role |
|---|---|
| View Member data retention period setting | Owner only |
| Change Member data retention period | Owner only |