Data controller
The centre using AESTRA is the data controller. Its official identifying details (legal name, VAT number, registered office and contacts) are configured in the platform settings.
The controller’s official identity and contact details are those in the centre’s contract documents and its AESTRA configuration.
Data processed during registration and sign-in
During registration and sign-in, AESTRA processes the centre’s sign-in details (username), the operator’s personal code and identifying details, the centre’s contact details and, where applicable, data about clients managed in the platform.
Centre passwords and operators’ personal codes are never stored in plain text. They are stored exclusively as cryptographic hashes with dedicated salt and pepper values.
Google authentication
If the centre enables Google sign-in, AESTRA receives only the Google account identifier and the email address verified by the provider, solely to recognise the centre and authorised operator. The operator’s personal code is still required for every Google sign-in.
Technical data and cookies
AESTRA uses session cookies required for operation, including a technical centre session on the workstation (an HttpOnly cookie inaccessible to JavaScript). No profiling cookies are used. The workstation identifier is stored as a cryptographic hash.
Purposes of processing
Data is processed to run the centre (appointments, clients, till, inventory and staff), authenticate users and control access, secure and trace sensitive actions in an audit log, and meet administrative and accounting obligations.
Data retention
Operational data is kept for the duration of the relationship with the centre and afterwards for the periods required by tax and accounting rules. Sign-in sessions are time-limited: up to 30 days for the centre, up to 12 hours for an operator, with a lock after 3 minutes of inactivity. Audit records are kept for security and traceability.
Your rights
Data subjects have the rights of access, rectification, erasure, restriction, portability and objection to processing, and may withdraw any consent given. Requests should be addressed to the controller’s privacy contact.
Send privacy requests using the controller’s official contact details in the contract documents or as provided by the centre.
