Data Processing Addendum (Annex 1 to the Terms of Use) (v1.0)
Effective date: 20 November 2026.
Controller: the Studio that accepted the Terms of Use ("Studio").
Processor: Mykola Zahorodnii, Karloveská 53, 841 04 Bratislava, Slovakia, mykolazahorodnii1@gmail.com ("Provider").
This Addendum applies when the Provider processes personal data on behalf of the Studio and is concluded when the Studio accepts the Terms of Use. It follows Article 28(3) of Regulation (EU) 2016/679 (GDPR).
1. Subject, duration, nature and purpose
1.1 Subject: booking, reminders and booking records for the Studio's End Clients.
1.2 Duration: for the period of the Studio's subscription or trial, plus the deletion period in section 10.
1.3 Nature and purpose: storing, displaying, transmitting to the Studio and deleting booking data, solely to operate the Service for the Studio. Details in Annex A.
2. Instructions (Art. 28(3)(a))
2.1 The Provider processes personal data only on the Studio's documented instructions. The instructions are these Terms, this Addendum, and the Studio's actions in the Service (creating, changing and deleting records).
2.2 If EU or Slovak law requires other processing, the Provider tells the Studio beforehand unless the law forbids it.
2.3 The Provider will not use the data for its own purposes, will not sell it, will not use it for its own advertising, and will not pass it to third parties except sub-processors under section 5.
3. Confidentiality (Art. 28(3)(b))
3.1 Everyone authorised to process the data (the Provider and any contractors) is bound by a confidentiality obligation or a statutory duty of confidentiality.
4. Security (Art. 28(3)(c), Art. 32)
4.1 The Provider applies the measures in Annex B and reviews them as the Service changes.
5. Sub-processors (Art. 28(2), 28(4))
5.1 The Studio gives general written authorisation for the sub-processors in Annex C.
5.2 The Provider tells the Studio by email at least 30 days before adding or replacing a sub-processor. The Studio may object on reasonable grounds within that period. If the objection is not resolved, the Studio may terminate the subscription.
5.3 Each sub-processor is bound by data protection obligations equivalent to this Addendum. The Provider remains responsible for the sub-processor's performance.
5.4 International transfers: EU data protection law, in particular the GDPR, applies to all processing under this Addendum, including processing by sub-processors, wherever they are located. The Service and its data are hosted in the EU. Where a sub-processor in Annex C processes personal data outside the EEA, the transfer is made only under Chapter V GDPR: on the basis of an adequacy decision of the European Commission (for a company in the United States, one certified under the EU–U.S. Data Privacy Framework) or of the standard contractual clauses adopted by the European Commission (Implementing Decision (EU) 2021/914).
6. Data subject rights (Art. 28(3)(e); Chapter III)
6.1 The Provider helps the Studio, by technical and organisational means, to answer requests from End Clients for access, rectification, erasure, restriction and portability. The Service gives the Studio tools to export and to delete or anonymise an End Client's data.
6.2 If an End Client contacts the Provider directly, the Provider refers them to the Studio.
7. Personal data breaches (Art. 28(3)(f); Art. 33)
7.1 The Provider informs the Studio by email, without undue delay and in any case within 48 hours after becoming aware of a personal data breach. The message describes the situation and the measures taken.
7.2 The Studio decides whether to notify the supervisory authority (in Slovakia, the Úrad na ochranu osobných údajov SR) and the End Clients. The Studio has 72 hours from becoming aware (Art. 33(1)).
8. Assistance (Art. 28(3)(f); Art. 32–36)
8.1 The Provider gives the Studio the information it reasonably needs for a data protection impact assessment or prior consultation with an authority.
9. Audits and information (Art. 28(3)(h))
9.1 The Provider provides the information needed to show compliance with Art. 28 and allows and contributes to audits.
9.2 Audits are done first by written documentation and answers to questions. An on-site or remote audit is possible only by agreement at least 30 days in advance, during business hours, not more than once a year, under an NDA and at the Studio's cost.
10. Return and deletion (Art. 28(3)(g))
10.1 After the subscription ends, or at the Studio's request, the Provider, at the Studio's choice, returns the data (export in CSV or JSON) or deletes it, within 30 days.
10.2 Existing copies are deleted too. Backup copies are overwritten in the normal rotation, in any case within 30 days.
10.3 The Provider may keep data only where EU or Slovak law requires it.
11. Liability and order of precedence
11.1 Liability is governed by the Terms of Use. If this Addendum conflicts with the Terms on data protection, this Addendum prevails.
Annex A — Description of processing
| Item | Content |
|---|---|
| Data subjects | The Studio's End Clients; the Studio's staff or owner (login contact) |
| Personal data | End Client: name, phone number, free-text comment, booking date, time and service, booking status. Owner: email, notification addresses (Telegram), push subscription, login records |
| Special categories | None intended. The Studio must not enter such data in free-text fields. |
| Frequency | Continuous, while the Studio uses the Service |
| Retention | Until the Studio deletes the data or the subscription ends, then section 10 |
Annex B — Security measures
- Encrypted connections (HTTPS/TLS) for all traffic.
- Logical separation of studios' data in the database (every record carries a studio identifier; queries are filtered by it); tests check that one studio cannot read or change another's data.
- Booking links use secret tokens; only a hash or a derived value is stored. Owner passwords are stored hashed (argon2).
- Access control and sessions with CSRF protection; rate limits and abuse controls on public forms.
- Daily database backups, each kept for at most 30 days; copies stored off the server are encrypted before upload.
- Content Security Policy and output escaping against script injection.
- The Provider's administrative tools give read-only access to a studio's data for diagnostics, and their use is logged.
- Regular updates of software and dependencies.
- A written breach handling procedure, and automatic alerts to the Provider on server errors and failed backups.
Annex C — Sub-processors
| Service | Role | Company and country | Data involved |
|---|---|---|---|
| Hosting and database | Servers, storage, backups | Mhost LLC, Georgia, registration number 447010314 (mhost.ee); server in a data centre in the Netherlands (EU) | All |
| Email delivery | Notifications and system emails | Sent by the Provider's own mail server on the same Mhost LLC server (no separate email company) | Owner email; notification content, which may include End Client name and phone |
| Off-server backup storage | Encrypted backups | Not in use yet; the provider will be named here before its first use | All, encrypted before upload; the provider cannot read it |
| Telegram | Owner notifications (if enabled by the Studio) | Telegram FZ-LLC, United Arab Emirates (transfer basis: section 5.4) | Notification content, which may include End Client name and phone |
| Web push services (Google FCM, Apple, Mozilla) | Delivery of push messages to the owner's device | Google LLC, USA (Android, Chrome); Apple Inc., USA (Safari on iPhone and Mac); Mozilla Corporation, USA (Firefox). The service is the one built into the owner's browser | Push payload encrypted end to end (the push service cannot read it) and delivery metadata |
Note: payments are handled by Paddle as merchant of record for the Studio's own subscription. Paddle is not listed above because it does not receive End Client data from the Service; it acts as an independent controller for the payment data the Studio gives it. The Provider's chat with the Studio (Telegram, Viber and similar) is used only for contact with the Studio, and End Client lists are not shared in it.