This agreement is part of the agreement between the salon that signs up to Groomtime (the Controller) and [LEGAL NAME], tax ID [NIF], [ADDRESS] (the Processor), under article 28 of Regulation (EU) 2016/679 (GDPR) and Spanish Organic Law 3/2018 (LOPDGDD). The Controller accepts it when signing up.
1. Subject
The Processor processes personal data on behalf of the Controller only to provide the Groomtime service: storing, syncing and showing the client and pet profiles, visits, incidents, photos, bookings, messages and payments, and the accounts of the salon's team.
2. Duration
For as long as the service lasts, including the read-only period in the terms.
3. Data and data subjects
| Data subjects | Data |
|---|---|
| The salon's clients (pet owners and their contacts) | Name, phone, email and other contact details; consents (photos, communications); notes; history of visits, bookings and payments; messages sent |
| The salon's team | Name, email, role, what each person did on each visit, activity log |
| Anyone who appears in a photo | Image (photos are of pets; a person can only appear by accident) |
Groomtime is not meant for special categories of data (GDPR art. 9). The Controller won't enter them.
4. The Processor's obligations
- Process the data only on the Controller's documented instructions, which are this agreement and the Controller's use of the app. If an instruction seems unlawful, it will say so.
- Ensure that the people authorised to process the data are bound to confidentiality.
-
Apply the security measures of GDPR article 32, among them:
- hosting in the European Union;
- encryption in transit (TLS) and at rest;
- isolation of each salon in the database (row-level security) and role permissions inside the salon;
- photos in private storage, with signed links that expire, and without location data;
- daily backups, also outside the main platform, and a tested restore procedure;
- a log of sensitive actions (deletions, downloads, team changes);
- error reports without names, phone numbers or emails.
- Not engage another processor without authorisation (section 6).
- Help the Controller respond to data subjects' requests. The app can download all of a client's data and erase it for good.
- Help the Controller with security, impact assessments and consultations with the authority, as far as the service is concerned.
- Notify the Controller without undue delay, and at most 48 hours after becoming aware of it, of any security breach affecting its data, with the information the Controller needs to notify the authority and the data subjects.
- When the service ends, let the Controller download its data and then delete it (copies included) within at most [90] days of the end of the read-only period, unless the law requires keeping it.
- Make available to the Controller the information needed to show compliance with this agreement, and allow reasonable audits, with notice and at the Controller's cost.
5. The Controller's obligations
- Have a legal basis to process its clients' data and inform them (the app includes a printable privacy notice).
- Ask for and record the consents that apply (photos, communications). The app sends no message to anyone who hasn't consented.
- Give access only to the team members who need it, with the right role.
6. Subprocessors
The Controller gives the Processor a general authorisation to use the subprocessors on the published list. The Processor will give at least 30 days' notice of any change to that list; if the Controller objects on reasonable grounds and there is no solution, it can cancel the service. The Processor imposes on each subprocessor the same data protection obligations as this agreement.
7. International transfers
The data is kept in the European Union. If a subprocessor accesses it from outside the European Economic Area, it does so with the safeguards of GDPR chapter V (standard contractual clauses or an adequacy decision).
8. Liability
Each party is liable for its own breaches under GDPR article 82. The rest of the terms of service applies.