...
Archived users
Reservations
Visitors
| Note |
|---|
Be aware when using customization. If additional fields and objects are created or updated concerning data that is also being anonymized, those customization parts are likely not included by default. Also avoid the use of field specific logging. If, for instance, specific reservation fields are logged (each change to the field is saved in an ‘objectHistory’ object), an administrator can always see the creator of that logged change, even after the reservation itself is anonymized. |
Archived users
Setup
Via ‘Client settings’ -> ‘Authentication’ tab, it is possible to indicate that all users who have been archived must be anonymized automatically X days after being archived.
...
How does this work?
All personal data from the system user (e.g., the username), contact (e.g., the email address), and person (e.g., the first- and last name) will be either replaced by a '*' or removed.
  |   |
Reservations
Setup
Via ‘Module settings’ -> ‘Reservations’ tab, it is possible to indicate that reservations must be anonymized automatically X days after the end time of the reservation.
...
Replacing the subject and description with a '*'
Changing all the contact fields of the reservation and the linked objects (e.g. tasks) to the general system administrator
All visitors or participants linked to the reservation are decoupled from the reservation
If the reservation is part of a recurring reservation, the recurring reservation is anonymized once the last reservation of the series is anonymized
 
 | 
|
Visitors
Setup
Via ‘Module settings’ -> ‘Visitors’ tab, it is possible to anonymize visitors automatically X days after departure or canceled visitors.
...