Personal data
A SCADA system has to record who operated the plant. YTCC therefore keeps personal data about its users. This page lists it for the data protection assessment of the operator of the plant (for example under the Turkish KVKK or the GDPR); the legal basis and the notice to the employees are the operator's responsibility.
What is kept
| Data | Where | Kept |
|---|---|---|
| User account: user name, full name, description, language, profiles, enabled, created, last sign-in, failed attempts | The project's user file in the data folder of the projects server | Until the user is deleted |
| Password | Only as a bcrypt hash, with the hashes of the last passwords for the history rule | Until the user is deleted |
| Sessions: browser identification and client address | The project's session file | Until the session has expired and the next sign-in tidies the file |
| User audit log: user name, client address, action | A file in the data folder | About 10 MB in total (see Audit logs) |
| Display and table preferences: theme, blinking, column choices, filters | A preference file per user in the data folder | Until the project is deleted |
| Event list: sign-in, sign-out, pages and popups opened, confirmations with value, the computer | The history database | 1825 days by default |
| Commands with the user, alarm acknowledgements with user and comment | The alarm archive | Two years |
| Configuration changes with the user name and comment | The project database | For the life of the project |
Deleting a user
Deleting a user in the Users activity removes the account and its password hashes, ends the user's sessions and removes the user from the server administrators of an upgraded server. It does not remove or anonymise:
- the user name in the user audit log, the event list, the command log, the alarm history and the configuration audit;
- the user's preference file.
These records are kept on purpose: they document who operated the plant. They disappear with their retention (see the table) or when the project is deleted.
Recommendations
- Name in the employee notice which actions are recorded and for how long.
- Set the retention of the event list to what your operating rules require; see Archive tables and assignments.
- Restrict access to the data folder and the databases of the server to the administrators.
- Use personal accounts; a shared account cannot show who acted.