...
Deactivated users’ data is automatically pseudonymised after a set period.
You can customise the delay (between 1 and 6 7 years) to suit your organisation’s needs.
...
1 years minimum: Covers scenarios like parental leave, allowing users to return if needed.
6 7 years maximum: Aligns with GDPR’s principle of limiting data retention to what is necessary.
| Info |
|---|
Note: You can manually psyhedponomise at anytime manually pseudonymise users at any time through the User Interface. |
...
Navigate to Company Settings > People > Data Protection.
Locate the “Automated Pseudonymisation” option.
Enable the setting and choose your delay period (between 1 and
...
7 years)
...
Optionally, select if 1-to-1s should be deleted when user is pseudonymised
Save your changes.
...
To manually pseudonymise a user:
Go to the user’s profile in the User Interface.
Select the
...
Anonymise User, and confirm.
...
How It Works
Delay Period: Pseudonymisation occurs after the deactivation date plus the configured delay period.
Timestamp: A confirmation timestamp is recorded once the pseudonymisation process is complete.
Aggregate Usability: The pseudonymised data remains usable for statistical and reporting purposes without compromising user privacy.
...
| Expand | ||
|---|---|---|
| ||
No, pseudonymisation is irreversible. Take care when configuring or manually applying pseudonymisation. |
| Expand | ||
|---|---|---|
| ||
No, pseudonymisation is irreversible. Take care when configuring or manually applying pseudonymisation. |
| Expand | ||
|---|---|---|
| ||
Yes. Pseudonymised data is stripped of personal identifiers but remains available for aggregate reporting and analytics. |
| Expand | ||
|---|---|---|
| ||
This range ensures compliance with GDPR and Learn Amp’s policies, striking a balance between protecting user privacy and meeting organisational needs. The minimum delay of 1 year accounts for scenarios such as parental leave, where some organisations deactivate accounts temporarily. This helps prevent accidental pseudonymisation of users who may return within this timeframe. |
| Expand | ||
|---|---|---|
| ||
Yes, you can manually pseudonymise any user at any time via the User Interface. This offers flexibility for immediate action. |
| Expand | ||
|---|---|---|
| ||
Anonymised: First Name, Last Name & Email Removed: Bio, Job Title, Profile Picture Optionally: 1-to-1s can be configured to be deleted when a user is pseudonymised. (This includes removing 1-to-1 comments, answers, notes and action points, reviewer responses and comments etc). |
| Expand | ||
|---|---|---|
| ||
The pseudonymisation process does not alter data stored in custom fields. Therefore, if you use a non-personal identifier (e.g., payroll ID or HRIS ID) as a custom field, this can be used to re-link the pseudonymised user data upon the employee’s return. It is important to ensure that this identifier cannot be used by Learn Amp to identify the user directly and does not qualify as personal data under GDPR. Always confirm that the identifier is unique to your organisation and does not, on its own, allow for re-identification by Learn Amp. |
| Expand | ||
|---|---|---|
| ||
Any identifiable information added to 1-to-1 responses will not be automatically pseudonymised, unless the setting “Delete a user's 1-to-1s when they are pseudonymised” is checked. If this setting has been checked, the related 1-to-1s records will be deleted, including all answers, notes, action points from both reviewee and reviewer etc. |
| Expand | ||
|---|---|---|
| ||
No; these 1-to-1s records will be completely deleted. |
| Expand | ||
|---|---|---|
| ||
No; these 1-to-1s records will be deleted, including all the information submitted by the reviewer. |
| Expand | ||
|---|---|---|
| ||
You can re-activate a pseudonymised user, but the fields impacted by the pseudonymisation will not automatically roll back to the original values. |