Appendix: Clearing Personal Details¶
Upon leaving the company it is possible that employees may wish to have their personal details removed from the company records. In the EU the GDPR legislation makes this a right of the employee under the 'right to erasure' article.
Within the scheduling software there are a number of steps that may need to be taken to remove personal details, and these are documented below.
Warning
Please note that personal information should not be used as part of the primary key in any data. In particular, the ids of all resources and users should not contain any personal information.
Removing User Data¶
The only personal user data that is stored in the system is the user's name. This can be removed via the Users administration screen on the Scheduling Workbench (Administration -> Organisation -> Users), either by removing the name or by deleting the user entirely.
If the Schedule Archive Database is being used then user information may also appear here. The information may be in the audit data, or in one or more snapshots of the system database. Audit data will be deleted automatically by the Schedule Archiving Service, by default after a period of 30 days (this is configurable via the 'AuditRetentionDays' parameter).
Personal user data can be cleared from archive database snapshots using the 'Clear Personal Data' screen on the Scheduling Workbench (Data Capture -> Archive -> Clear Personal Data). Simply select the 'Remove User' option and enter the id of the user for whom personal data should be cleared. See the section in the Schedule Archive User Guide for full details.
Note
Note that user personal details should be removed from the system tables first, before removing details from the Schedule Archive.
Finally, user data will also be included in any exports of the system database, taken from the Import/Export screen in the Administration workspace. If it is necessary to keep older copies of these files then the files would need to be hand edited to remove personal details (the files can be opened using notepad or any other text editor). Otherwise the files can be deleted and replaced with an updated export of the system data.
Removing Resource Data¶
The Scheduling Database is only used for temporary storage of data. As such, when a resource leaves the company any data relating to this resource will be removed from the scheduling database in due course, provided that the resource is no longer included in any input data.
Note
The removal of historical data is carried out by the Scheduling Administration Service, based on the parameters 'InputRetentionSeconds' and 'OutputRetentionSeconds', which are both defaulted to one day.
If the Advanced Resource Planner is being used, then any resource data should be manually cleared, either by deleting the resource or by updating any attributes containing personal information. See the 'List of Attributes' section for a list of possible attributes.
Note
Please note that any deleted data is initially only 'soft' deleted from the database. However, the Resource Planning Service is set to permanently delete this data after a period of 7 days by default. These options are configurable via the parameters 'ManageARPDataOptions' and 'KeepDeletedARPDataHours'. Note that the cleaning takes place once per day at the time specified by the parameter 'ManageARPDataTimeOfDay'.
If the Schedule Archive Database is being used then user information may also appear here. The information may be in the audit data, reporting data, or in one or more snapshots of the system database. Audit and reporting data will be deleted automatically by the Schedule Archiving Service, by default after a period of 30 days for audit data and 90 days for reporting data (this is configurable via the 'AuditRetentionDays' and 'ReportingRetentionDays' parameters).
Personal resource data can be cleared from archive database snapshots using the 'Clear Personal Data' screen on the Scheduling Workbench (Data Capture -> Archive -> Clear Personal Data). See the section in the Schedule Archive User Guide for full details.
Note
Note that all resource personal details should be removed from both the scheduling input data and the modelling (ARP) database first, before removing details from the Schedule Archive.
Finally, personal details may appear in saved schedules and exported files. It is recommended that these are removed and replaced with updated versions once the resource personal details have been cleared.
List Of Attributes¶
The table below lists attributes within the schema that may contain personal data, and a suggested action for removing this data. These actions are carried out by the Schedule Archiving Service when removing personal data from the Schedule Archive Database.
| Type Of Data | Tables | Columns | Suggested Action |
|---|---|---|---|
| Users | Users | name | Clear data. |
| Resource | Resources RAM_Resource ARC_Resource | first_name surname memo contact_details description label (ARC_Resource) attribute_value1-4 (ARC_Resource) | Clear all data. For attributes, clear only those that contain personal data. |
| Resource home location(s) | Location RAM_Location ARC_Location | description name latitude longitude post_code_zip address_line1-6 city state region locality | Clear all data for related locations. |
| Private activities / unavailabilities for the resource | Activity RAM_Unavailability | description | Clear all data. |
| Attributes containing personal details | Additional_Attribute RAM_Attribute_Value | label_value value | Clear the value, replacing with a generic value, e.g. '-'. |
| Shifts | Shift RAM_Rota_Item RAM_Rota_Item_Comment | description comment | Clear data. |
| GPS fix data | Schedule_Event | Remove all events of type 'FIX' relating to the resource. | |
| Custom URLs | Custom_URL URL_String URL_Parameter Resource_Custom_URL | Remove all custom URL rows linked to the resource. | |
| Custom Exceptions | Custom_Exception Custom_Exception_Data | Remove all custom exception rows linked to the resource. |