Data Processing Agreement
This is the document that makes the allocation of responsibility real. Without it, "the master is responsible" has no legal existence: Article 28(3) GDPR requires a written contract with specific content.
Forms part of the Terms of Service.
1. Parties and roles
Controller: you, the master using the Service.
Processor: Leonid Spitonev, IČO 05027152, Na vyhlídce 1302, 252 10 Mníšek pod Brdy, Czech Republic.
You decide why and how the personal data of your guests is processed. We process it only on your behalf. This split applies to guest data only — for your own account data we are the controller, and that is covered by the Privacy Policy.
2. Subject matter, duration, nature and purpose
Subject matter: providing the Banya Masters workspace. Duration: for as long as your account exists, plus the retention period in clause 10. Nature and purpose: storing and displaying records about your guests, producing letters to them, and keeping the money records of their visits — so that you can run your practice.
3. Categories of data subjects and data
Data subjects: your guests, and people they name (for example the person paying for a group session).
Ordinary personal data: name, contact details, language, visit history, programme and location of each visit, amounts owed and paid, your free-text notes.
Special category data (Article 9 GDPR): data concerning health — allergies, conditions, medication, injuries, pregnancy, and anything you record in the health fields or in your notes.
You decide what goes into these fields. We do not require you to record health data, and the Service works without it.
4. Your instructions
4.1. We process guest data only on your documented instructions. Your use of the Service, together with the Terms and this Agreement, is your instruction.
4.2. If we believe an instruction breaks data protection law, we will tell you.
4.3. We process guest data outside your instructions only where EU or Member State law requires it; in that case we will tell you beforehand unless the law forbids it.
5. Your obligations as controller
5.1. You must have a lawful basis for every piece of guest data you enter.
5.2. For health data you must obtain explicit consent from the guest before recording it, and you must be able to prove you obtained it. We give you a questionnaire template and a place to record that consent was obtained; we do not obtain it for you.
5.3. For a guest under 18, consent for health data is given by a parent or guardian.
5.4. You must inform your guests about the processing — who you are, why you keep their data, how long, and how to withdraw consent.
5.5. You decide how long to keep guest data and delete what you no longer need.
6. Confidentiality
Everyone who has access to guest data on our side is bound by confidentiality. Access is limited to the people who need it to run and support the Service, and the list is kept short — today it is the Provider and no more than three administrators.
7. Security
We take the measures required by Article 32 GDPR, in particular:
- data is isolated per master: one master's records are not reachable from another master's account, and this is enforced in the structure of the application, not only by settings;
- sign-in is protected against a stolen password, a fake site and brute force: the main method is a device key (face, fingerprint or PIN) bound to our domain, a second factor by authenticator app is available if you switch it on, and sign-in attempts are rate-limited;
- traffic is encrypted in transit; the database and file storage sit inside the European Union;
- backups are taken daily and kept for 30 days.
We review these measures as the Service changes.
8. Sub-processors
8.1. You give general authorisation for us to engage sub-processors. The current list is published at banya-masters.com/subprocessors and is today:
| Who | What they do | Where |
|---|---|---|
| Hetzner Online GmbH | server and database hosting | Germany (EU) |
| Cloudflare, Inc. | file storage and database backups (R2) | EU region |
| Kinde (KindeHQ) | sign-in and accounts | EU region |
| Resend (Plus Five Five, Inc.) | sending letters | sending from the EU; account data, logs and message metadata in the USA |
| Stripe | payments, subscriptions and invoices — your billing data only, never guest data | EU and USA |
| Sentry (Functional Software, Inc.) | error reports: your account number, the page address, the visitor's approximate location (city) and a technical description of the error — never email addresses, phone numbers or health data | EU region (Germany); company in the USA |
Analytics runs on Umami Cloud (Umami Software, Inc.), a cloud analytics service with data stored in the EU (Frankfurt). It sets no cookies and collects no personal data.
Stripe is listed before it begins. Payments are not taken inside the Service yet. We name it in advance because we owe you 30 days' notice before a new sub-processor starts, and we would rather be early than late. Until payments are switched on, Stripe receives nothing from us.
8.2-bis. If a provider must be replaced immediately — because it fails, loses its own legal basis, or presents a security risk — we may do so without the 30 days and will tell you as soon as we reasonably can, with the reason. The right to object in 8.3 then applies from the day you are told.
8.2. We will give you at least 30 days' notice by email before adding or replacing a sub-processor. If you object on reasonable data protection grounds, you may terminate your subscription before the change takes effect, and we refund the unused part of the period you paid for.
8.3. We impose on each sub-processor the same obligations we have under this Agreement, and we remain fully liable to you for their performance.
9. Transfers outside the EEA
9.1. Guest data is stored inside the European Union.
9.2. One transfer outside the EEA exists and we name it rather than hide it: Resend is established in the United States. Letters are sent from their EU region, but the account data, delivery logs and message metadata — which include the guest's email address and the subject line — are stored in the USA. That transfer is covered by Standard Contractual Clauses in Resend's processing agreement and by their participation in the EU–US Data Privacy Framework.
9.3. We do not transfer health data to Resend. Health data never leaves the Service and is never put into letters.
9.4. Sentry stores error reports in its EU region (Germany), but it is established in the United States and its processing agreement allows access from there. Error reports carry no guest contact details and no health data: email addresses, phone numbers and health fields are removed before a report leaves the Service. Any such access is covered by Standard Contractual Clauses in Sentry's processing agreement and by its participation in the EU–US Data Privacy Framework.
10. Return and deletion
10.1. You can ask for a copy of guest data at any time. We provide it in a machine-readable format within a reasonable time, free of charge.
10.2. When your trial or paid period ends without payment, your account becomes read-only. Guest data is kept for two years from that date and then permanently deleted, unless you ask us to delete it earlier or the law requires us to keep it longer.
10.3. Backups are overwritten on their own schedule — deletion from backups takes up to 30 days after deletion from the live system.
11. Helping you with your obligations
We help you, taking into account the nature of the processing and the information available to us:
- Data subject requests. If a guest contacts us directly, we will not answer on your behalf — we will forward the request to you without undue delay. If you need data in order to answer, we provide it.
- Security incidents. We notify you without undue delay after becoming aware of a personal data breach, with what we know: what happened, which data and how many people are likely affected, the likely consequences, and what we are doing. Notifying the supervisory authority and the guests is your duty as controller.
- Impact assessments. We give you the information you need for a data protection impact assessment or prior consultation.
12. Audit
You may ask us, once a year and on reasonable notice, for the information needed to show that this Agreement is being met. Because the Service is run by one person and is shared infrastructure, an on-site inspection is possible only where it is required by law or by a supervisory authority.
13. Liability
Each of us is liable for the damage caused by processing that breaks the GDPR, to the extent that the law provides. Nothing in this Agreement limits the rights of your guests or the powers of a supervisory authority.
14. Order of precedence
Where this Agreement and the Terms of Service conflict about personal data, this Agreement wins.
Version 1.3, effective 10 November 2026.
Revision 1.3 · 2026-11-10