Data subjects: salon end-clients; salon employees/stylists; suppliers and contacts the Controller records.
Categories of personal data: contact details (name, email, phone), identifiers (client number), appointment history, services, invoices, payments, notes, photos, preferences, gift-card and loyalty balances, email/WhatsApp communication, reviews, and the AGB code (Vektis) of the practice and of staff members as care providers, for display on the receipt, and the telephone number of staff members.
Staff telephone number - The Controller can record a telephone number per staff member. End-clients do not see that number by default. If the Controller switches on 'Show staff phone number to clients' while end-clients can choose a staff member themselves, the Controller instructs the Processor to show the number of a staff member on the public booking page to the visitor who chooses that staff member, and to include the number of the staff member of the appointment in the confirmation, the change email and the reminder to the end-client. The Controller ensures a valid legal basis and informs the staff member about this.
Special categories (Article 9 GDPR) - such as health notes (allergies, medication, skin conditions, pregnancy) - are stored in a dedicated encrypted vault, separated from regular client notes. The Processor applies the following additional safeguards:
• AES-256-GCM envelope encryption using a per-tenant data key, which is itself wrapped at rest with a platform master key.
• The master key is held exclusively in environment variables, separate from database backups; loss of the key renders all vault data permanently unreadable.
• Access to the vault: the Controller's admins have access automatically; other staff only if an admin grants them that right through a dedicated permission flag (can_view_health_notes), recorded per staff member. There is never access via platform impersonation.
• Immutable access log: every read, write, download and deletion is recorded with actor, IP address and timestamp, and retained for 24 months.
• Retention: a note is kept until 12 months after the end customer's last appointment that took place (cancelled appointments and no-shows do not count), and in any case until 12 months after it was recorded or imported; the Controller can extend a note individually. After consent is withdrawn, the note is deleted after 30 days. A deleted note is permanently erased after a grace period of 30 days.
• Platform impersonation is technically blocked on the health-data routes (defence-in-depth).
The Controller remains responsible for establishing and documenting the appropriate legal basis under Article 9(2) GDPR (typically explicit consent or vital interests). The Processor provides the technical facility to record, prove and withdraw such consent through a separate consent-event log. See the "art9-health-data-vault" runbook for technical details.
Carry-over when switching - If the Controller imports health data from a previously used system, it may carry over the explicit consent of the data subject given there. With every import the Controller confirms that this consent was given for the end customers concerned and that it can demonstrate this (Article 7(1) GDPR); responsibility for the accuracy of that confirmation and for the evidence lies with the Controller. The Processor records the confirmation (user, time, wording and version of the confirmation, the previous system and the import run) and carries over consent only for end customers whose health data is recorded in that import. Consent that was previously withdrawn is not restored; no health data of those end customers is carried over. Without confirmation, and when access takes place via platform impersonation, the Processor does not carry over any health data.