Data processing agreement
The agreement about your clients’ and your team’s data, under article 28 of the GDPR. Part of the terms of service. Version of 15 November 2026.
The parties
This agreement is between the studio that uses Prenuvio (‘the studio’, the controller) and the company below (‘Prenuvio’, the processor). It is part of the terms of service and applies as soon as the studio creates an account, without a separate signature.
- Company name
- Prenuvio
- Country
- The Netherlands
- [email protected]
Prenuvio is being registered with the Dutch Chamber of Commerce. The registration number, VAT number and address will be shown here as soon as they exist.
1. What Prenuvio processes data for
Prenuvio processes personal data only to provide the studio with the service in the terms: online booking, the calendar, client cards, e-mails to clients, notifications to the studio, AI help at the studio’s request, downloading and deleting data.
This lasts as long as the studio uses Prenuvio, and after that until the data is deleted (article 10).
2. Whose data and which data
- The studio’s clients: name, e-mail address, phone number, language, appointments (treatment, extras, team member, location, time, price, status), the answer to the studio’s question, discount codes used, what was paid and how, receipts if the studio uses Receipts and sales, notes on the client card, consent to news and offers (when and how it was given), newsletter sign-ups and unsubscribes, and the e-mails Prenuvio sends them on the studio’s behalf.
- People who message the studio through its contact form: name, e-mail address, phone number, message and replies.
- The studio’s team members: name, role, photo if the studio adds one, working hours, breaks, days off with their note, and with their own sign-in their account details.
- People the studio names on its page, such as the name with a review the studio puts there itself.
Prenuvio is not meant for special categories of data, such as health data. If the studio still notes something like that, for example an allergy, it does so only with a legal basis, and as briefly as possible.
3. Only on the studio’s instructions
- Prenuvio processes the data only on the studio’s instructions. The instructions are what the studio sets and does in the app, this agreement and the terms. Other instructions the studio gives by e-mail.
- If Prenuvio thinks an instruction breaks the law, Prenuvio says so at once.
- If the law requires Prenuvio to hand over data, for example to the police or a regulator, Prenuvio tells the studio first, unless the law forbids that.
- Prenuvio does not use the data for its own purposes, does not sell it and does not use it for advertising.
4. Who at Prenuvio has access
Only the owner of Prenuvio and the people he appoints in writing to run the service have access to the server and the database. Each of them is bound by confidentiality.
People at Prenuvio look at a studio’s data only when needed: to answer a question from the studio, to fix a fault or to stop abuse.
5. Security
These are the measures in Prenuvio today:
- Encrypted connections: all traffic goes over https, through Cloudflare, with a valid certificate on the server itself. Browsers are told never to connect unencrypted (HSTS, one year). Plain http requests are redirected to https.
- A shielded server: from outside, only the ports for https, http and management over SSH are open. The database has no port to the outside and the app listens only internally. Operating-system security updates install by themselves. The secret keys are in a file only the management user can read.
- Passwords: stored only as a hash (PBKDF2), 12 to 128 characters. Reset links work for one hour and once, confirmation links for 48 hours. Of both we keep only a hash.
- Sessions: a cookie that only travels over https, cannot be read by scripts and is not sent with requests from other sites. A session expires 30 days after its last use. Changing your password signs out other devices. Forms are protected against forged requests (CSRF).
- Limits: at most 10 failed sign-in attempts per quarter of an hour per e-mail address and 100 per IP address, and limits on other requests per IP address. A password asked for a sensitive action counts as a sign-in attempt.
- Roles: a team member sees appointments and clients, but no revenue, settings or exports, and cannot erase clients. Anything not explicitly opened to team members is for owners only.
- Studios kept apart: every record belongs to one studio, and the database enforces that appointments, clients and payments cannot point to another studio. An account sees only studios it is a member of.
- Logs: the app writes no submitted request data into its logs, and passwords, names, addresses and messages are filtered out of them. Logs are erased when they reach a fixed size.
- Keeping little: e-mails lose their content, address and subject after 90 days. Files the studio has the AI read are not kept.
- Complete deletion: when a studio is deleted, every row of that studio goes from every table, and its photos and receipts from the disk. An automated test checks that nothing of the studio remains.
Backups: every night a copy of the database and the uploaded files, and before each update a copy of the database. They are on the same server and are erased once they are more than 14 days old. No copies are stored outside the server at this moment.
Prenuvio adapts these measures when technology or risks call for it, and never makes them weaker.
6. Sub-processors
The studio allows Prenuvio to use these companies. Prenuvio gives them the same obligations as this agreement.
| DigitalOcean | The server with the app, the database and the uploaded files. All the data above. Data centre in Amsterdam (AMS3). Contracting entity: DigitalOcean, LLC (United States). According to DigitalOcean its data processing agreement is part of its terms of service; for transfers to the United States it relies on the EU-US Data Privacy Framework, and otherwise on standard contractual clauses. Source · 15 November 2026 |
|---|---|
| Cloudflare | Domain names, security and passing on all traffic to prenuvio.com, app.prenuvio.com and studios’ addresses. Sees IP addresses and what goes over the connection. Contracting entity: Cloudflare, Inc. (United States). According to Cloudflare its data processing addendum is part of the subscription agreement. Cloudflare runs data centres around the world and may process this outside the European Economic Area too; it relies on the EU-US Data Privacy Framework, and otherwise on standard contractual clauses. Source · 15 November 2026 |
| Resend | Sends every e-mail: to clients on the studio’s behalf, and to the studio itself. Receives the address, the name and the content of each e-mail, such as the appointment. Contracting entity: Plus Five Five, Inc. (United States), the company behind Resend. According to Resend its data processing agreement is part of its terms of service. The e-mails leave from Ireland; otherwise Resend processes mainly in the United States, where the data about the e-mails and the logs are also stored. Resend relies on standard contractual clauses and the EU-US Data Privacy Framework. Source · 15 November 2026 |
| Google (Gemini API) | Only the AI help, only when someone at the studio asks: the studio’s public details, treatment names and prices, a price list or receipt the studio has read, and its own notes for a newsletter. Never clients’ data from the database. Prenuvio uses the Gemini API under Google’s terms for paid services. Contracting entity for it in the Netherlands: Google Cloud EMEA Limited (Ireland). Under Google’s terms, Google processes this under its data processing terms and does not use prompts and responses on paid services to improve its products. Google may process this in any country where it or its sub-processors have facilities, and relies on the EU-US Data Privacy Framework, and otherwise on standard contractual clauses. Source · 15 November 2026 |
Not sub-processors
These parties are close to Prenuvio but receive no personal data of the studio:
- GitLab holds the source code and builds the app. No data of studios or clients is there.
- Push services of browsers and phones (for example Apple, Google or Mozilla) deliver notifications to the studio’s phone. The content is encrypted; they cannot read it.
- Mollie (payments) and VIES (checking VAT numbers) receive only data about the studio as Prenuvio’s customer, not about its clients. Prenuvio itself is responsible for that; see the privacy statement.
- Analytics on request: if a studio asks us to switch on measuring its booking steps with its own Google Analytics, that happens in its own account, only with the visitor’s consent and without names or contact details. That is an arrangement between the studio and Google.
7. A new sub-processor
- If Prenuvio wants to add or replace a sub-processor, Prenuvio e-mails the studio at least 30 days ahead and updates the list above.
- If the studio has a reasonable ground to object, we look for a solution together. If that fails, the studio may cancel before the change applies and gets back what it paid in advance for the months after.
- Transfers outside the European Economic Area happen only on a basis from the GDPR. The basis each sub-processor names is in article 6: the EU-US Data Privacy Framework and the European Commission’s standard contractual clauses.
8. Help with clients’ requests
The studio can handle most requests itself in Prenuvio:
- Access: the client card shows details, appointments, payments and notes. The ZIP under Settings › Business details holds all clients, appointments and payments as files.
- Correction: the studio edits the client card.
- Erasure: the studio erases a client. Name, e-mail address, phone, notes and consent go, from the appointments too; appointments and payments stay without a name for the books; e-mails about the client are emptied and the client’s messages deleted.
- Withdrawing consent: every newsletter has an unsubscribe link, and the studio can switch consent off on the client card.
If a request reaches Prenuvio, Prenuvio passes it to the studio within five working days and does not answer it itself. Where the studio needs more help, Prenuvio helps as far as reasonable.
9. Data breaches
- If Prenuvio discovers a security breach that affects the studio’s data, Prenuvio tells the studio without undue delay and within 48 hours of discovering it, by e-mail to the owners.
- The notice says what happened, which data and how many people are affected as far as known, what the consequences may be and what Prenuvio does to limit them. Prenuvio adds what it learns later.
- The studio decides whether to report the breach to the regulator and to its clients. Prenuvio helps with that.
- Prenuvio keeps a record of every breach, small ones included.
10. When the agreement ends
- Before the end, the studio downloads its data as a ZIP.
- If the studio deletes its studio itself, Prenuvio deletes everything of that studio at once.
- If the subscription ends without the studio being deleted, the studio is locked and the data is kept, so the studio can download it or carry on later. Prenuvio deletes a studio that has been locked for twelve months, after telling the owners by e-mail 30 days ahead, unless the law requires Prenuvio to keep something.
- What is still in backups disappears as article 5 says.
11. Audits and the regulator
- Prenuvio gives the studio the information needed to show that this agreement is kept, and answers questions about it by e-mail.
- The studio may have an independent expert bound to confidentiality check this, at most once a year, with 30 days’ notice, at its own cost and without disturbing the service for others.
- Prenuvio helps the studio as far as reasonable with a data protection impact assessment and with questions from the regulator.
12. Other provisions
- For liability, the limits in article 12 of the terms of service apply.
- If this agreement and the terms conflict, this agreement prevails as far as personal data is concerned.
- Dutch law applies to this agreement, as to the terms.
- Send questions about this agreement to [email protected].