Terms and conditions and data processing agreement — plevry

Version 2026-09.4 · in force from 23 September 2026

Machine translation. The Dutch text is authoritative: /nl/terms

This translation is provided for understanding only and creates no rights or obligations of its own. Part II of this document is a data processing agreement that an Operator may need to give to their own clients as evidence of GDPR compliance. If there is any difference between the two texts, the Dutch text prevails, and the Dutch version should always be used whenever this document is relied on or passed to a third party.

This document consists of two parts. Both are contracts between the same two parties — plevry and the Operator — and are accepted at the same moment: when a business is created in the app.

• Part I — Terms and conditions: use of the Service.
• Part II — Data processing agreement: the processing of End Customers' personal data. The GDPR (art. 28(9)) requires a written agreement for this; that is why this is a full contractual part and not an informative annex.

Order of precedence. In case of conflict between the two parts, Part II prevails, to the extent it concerns the processing of End Customers' personal data (see Part II, art. 12.5). For everything else, Part I prevails. The limitation of liability in Part I, article 13 applies to both parts together: there is one maximum, not two.

Part I — Terms and conditions

Article 1 — Definitions

In these terms and conditions:

• plevry — the plevry service, operated by Falley B.V., Chamber of Commerce no. 91810760, Oder 20, 2491 DC The Hague, the Netherlands, trading under the trade name plevry registered with the Dutch Chamber of Commerce. Where "plevry", "we" or "us" is used below, this means Falley B.V.; the capital letter is merely the way the brand name is written and does not affect the registered trade name.
• Operator — you: the self-employed person, salon or business that uses plevry to manage appointments. In the data processing agreement this same party is called the "Client" and the "Controller"; that is the same party as the Operator here.
• End Customer — the Operator's customer who books an appointment through plevry.
• Service — the plevry platform: the operator app, the calendar, the public booking page at book.plevry.app/<name>, the emails that go with it and the related features.
• Treatment Agreement — the agreement about the treatment itself, between the Operator and the End Customer. plevry is never a party to it.
• Transaction Fee — the fixed amount that the Operator can set in the app themselves, which is charged to the End Customer on top of the treatment amount for an online payment (Article 8.8). That amount belongs entirely to the Operator.
• Free — the no-cost variant of the Service (Article 6.3).
• plevry Pro — the paid subscription to the Service, which is billed through Apple's App Store or through Google Play and not by plevry itself (Article 6).
• Agreement — the agreement between plevry and the Operator about the use of the Service, of which these terms and conditions form part.

Article 2 — Who these terms apply to

2.1 These terms apply to every use of the Service by the Operator.

2.2 The Operator acts in the exercise of a profession or business. These are not consumer terms. The End Customer's consumer rights arise from the Treatment Agreement with the Operator; plevry is not a party to it (Article 5.1).

2.3 The Agreement also includes:

• the data processing agreement — about the processing of End Customers' personal data;
• the privacy and cookie statement — about the data plevry processes as its own controller, and about cookies.

2.4 Order of precedence. In case of conflict, the following applies in order: (1) the data processing agreement for everything concerning the processing of personal data, (2) these terms and conditions, (3) the privacy and cookie statement, which is informative.

2.5 Terms and conditions of the Operator are expressly rejected, unless plevry has accepted them in writing.

Article 3 — How the Agreement comes into being

3.1 The Agreement comes into being at the moment the Operator creates a business in the app and in doing so accepts these terms and conditions, the privacy statement and the data processing agreement.

3.2 plevry records, per document and per version, when the Operator accepted it. That is the evidence of the Agreement and of the written data processing agreement the GDPR requires (art. 28(9) GDPR).

3.3 The Operator provides accurate information when creating the business and keeps it up to date.

Article 4 — What the Service is

4.1 plevry offers the Operator software to manage appointments: a calendar, a public booking page, the creation of appointments, confirmation and reminder emails to the End Customer, notifications to the Operator and an export of bookings for their own records. Which of these features are available to the Operator depends on the variant they use (Article 6).

4.2 plevry grants the Operator, for the duration of the Agreement, a non-exclusive, non-transferable right to use the Service for their own business.

Article 5 — What the Service is not

5.1 plevry is not the provider of the treatment. The Treatment Agreement comes into being solely between the Operator and the End Customer.

5.2 plevry is not a payment service provider, not a payment institution and not an intermediary for payments. See Article 9.

5.3 plevry does not provide tax, legal or business advice.

Article 6 — What use costs: Free and plevry Pro

6.1 The Service has two variants: the no-cost variant (Free) and the paid subscription (plevry Pro). For Free, plevry charges the Operator nothing: no usage fee, no invoice and therefore no payment term.

6.2 plevry's revenue consists solely of the Operator's plevry Pro subscription. plevry charges the End Customer nothing and receives nothing from the End Customer's payment (Article 9).

6.3 What Free includes. On Free the Operator can accept a maximum of 30 bookings per calendar month. Once that number is reached, new bookings are refused for the rest of that calendar month, both in the app and on the public booking page; if a booking is cancelled, that space becomes available again within the same month. Appointments already made always remain visible and manageable. Not available on Free: online payment and deposits, automatic reminder emails to End Customers and exporting bookings.

6.4 What plevry Pro adds. With plevry Pro the monthly booking limit is removed and the following become available: online payment and deposits (Article 9), automatic reminder emails to End Customers and the export of bookings. plevry may add features to plevry Pro; Article 7 applies to a change in what is paid for.

6.5 Price and billing. plevry Pro costs 9.99 € per month. The subscription is not billed by plevry, but through the App Store or Google Play, on the account the Operator uses the app with. The App Store or Google Play shows the price that applies to the Operator's country before confirmation; that displayed price is decisive. plevry does not send an invoice for the subscription, does not receive payment details from the Operator and does not collect anything itself.

6.6 Term, renewal and cancellation. plevry Pro is a monthly subscription that automatically renews until the Operator cancels it. The Operator cancels themselves, in the subscription settings of the App Store or Google Play. plevry cannot cancel, change or refund the subscription on behalf of the Operator and has no access for that purpose; a request for a refund also goes through the App Store or Google Play and is assessed by Apple or Google respectively. The terms of Apple or Google respectively also apply to billing, renewal, cancellation and refunds.

6.7 If the Operator cancels, plevry Pro remains available until the end of the period already paid for. After that the account moves to Free, with the consequences of 6.9.

6.8 14-day trial period. When creating a business, the Operator automatically receives 14 days of plevry Pro, free of charge and without needing to provide a payment method. This trial period is granted by plevry itself and is not a trial subscription of the App Store or Google Play. The Operator sees in the app how many days remain. The trial period ends automatically by operation of law: no automatic payment and no subscription follows. If the Operator wants to keep plevry Pro afterwards, they take out a subscription themselves as described in 6.5 and 6.6.

6.9 What happens when plevry Pro ends. If the trial period ends or the subscription ends, the account moves to Free. This only changes what the Operator can do from that moment on; it changes nothing about what already exists. plevry does not delete any data in doing so: treatments, opening hours, bookings, the Mollie connection and the configured deposits and Transaction Fees remain stored unchanged. If the Operator later takes out plevry Pro again, the associated features are immediately available again without them having to set anything up again. This is separate from deleting the account, where data is permanently deleted (Article 15.5).

6.10 Failed renewal. If a renewal at the App Store or Google Play fails, the Operator keeps plevry Pro during the recovery period that Apple or Google respectively applies for that case. If payment still succeeds within that period, the subscription continues; if it does not, the account moves to Free, with the consequences of 6.9.

6.11 Change to the price or the subscription terms. If plevry changes the price of plevry Pro or the terms of the subscription, plevry announces this at least one month before the effective date by email to the address known for the account or in the app, stating the change and the effective date. If the change is to the Operator's disadvantage, they may terminate free of charge until the effective date: they cancel the subscription under 6.6 and may terminate the Agreement under Article 15.2. A price change only takes effect from the first renewal on or after the effective date; plevry never charges retroactively.

6.12 Costs that third parties charge the Operator are for the Operator's account. These are in particular Mollie's transaction fees, and the costs of their own internet, device and app store account.

Article 7 — New and changed paid features

7.1 plevry may introduce new paid features or subscription forms, and may move a feature that is offered free of charge at that moment into a paid variant.

7.2 plevry announces this in writing at least one month before the effective date (by email to the address known for the account, or in the app), stating which feature it concerns, what must be paid for it and from which date.

7.3 The Operator may terminate the Agreement free of charge and with immediate effect until the effective date (Article 15.2). If they have a plevry Pro subscription, they additionally cancel it themselves under Article 6.6.

7.4 Until the effective date, a feature that was offered free of charge remains free of charge. Without an announcement as referred to in 7.2, a feature offered free of charge does not become paid.

7.5 plevry never charges retroactively.

7.6 [Repealed.]

Article 8 — The Operator's obligations towards their End Customers

8.1 The Operator is themselves responsible for the Treatment Agreement: the treatment, its performance, the quality, the safety and all statutory obligations that go with it.

8.2 The Operator establishes their own cancellation, rescheduling and no-show policy, makes it known to the End Customer before booking and handles it themselves. plevry has no role in this and does not decide on it.

8.3 Whether the treatment amount is refunded is a decision for the Operator. A refund through plevry can cover the full amount paid by the End Customer, including the Transaction Fee set by the Operator (Article 8.8): plevry withholds nothing from a refund (Article 9.8).

8.4 The Operator ensures accurate and complete information on their booking page: treatments, duration, prices including VAT, opening hours and contact details.

8.5 The Operator complies with the consumer law applicable to their own services.

8.6 The Operator is the controller for the personal data of their End Customers. See the data processing agreement.

8.7 The Operator does not record special categories of personal data (such as health data) in free-text fields such as notes, unless they have a legal basis for doing so. See the data processing agreement, §3.

8.8 Transaction Fee. The Operator can set a fixed Transaction Fee amount in the app, which is added to the amount payable for an online payment. plevry sets a single technical upper limit for this (1.00 € per booking) and shows the amount as a separate line to the End Customer before payment. The amount belongs entirely to the Operator; plevry receives none of it.

The Operator is themselves responsible for ensuring that the amount they choose is permitted and not higher than what they may charge on under consumer law. plevry does not assess this: the upper limit of 1.00 € is a technical restriction and not a judgment that any amount below it is lawful. If the Operator sets an amount higher than their actual payment costs, that is their choice and their risk; Article 14 (indemnification) applies to it.

Article 9 — Payments: the Operator's own Mollie connection

9.1 Online payments run through Mollie B.V. The Operator concludes their own agreement with Mollie for this, accepts Mollie's terms and is themselves responsible for the identification and verification Mollie requires (KYC), for the accuracy of the information provided and for keeping their own Mollie account up to date.

9.2 plevry is not a party to the payment, is not a payment service provider and does not hold any funds. plevry has no access to End Customers' account or card details.

9.3 The Operator connects their own Mollie account to plevry through the Mollie connection in the app (OAuth). In doing so, the Operator authorises plevry, within the requested rights (scopes), to do the following on their Mollie account:

• create and read payments and payment links for bookings made through plevry;
• create refunds resulting from a cancellation through plevry;
• read the organisation, profile and onboarding status needed to make the connection work.

9.4 The rights of the connection are fixed at the moment of connecting. If plevry adds a right needed for a new feature, the Operator must re-establish the connection; until that moment that feature will not work. plevry informs the Operator about this in the app.

9.5 The End Customer pays the treatment amount, increased by the Transaction Fee set by the Operator themselves (Article 8.8), directly into the Operator's Mollie account. The Operator receives that full amount, less the costs Mollie itself charges them. plevry receives nothing from that payment.

9.6 Those Mollie transaction costs are not set by plevry and do not go to plevry. They follow from the Operator's own agreement with Mollie and depend on the chosen rate, the payment method and the volume. plevry can therefore not state an amount for them. The Operator finds their own rates in their Mollie dashboard and in their agreement with Mollie.

9.7 [Repealed.]

9.8 On a refund, plevry withholds nothing. If an appointment is cancelled and the Operator decides to refund it (Article 8.3), the refund can cover the full amount paid by the End Customer.

9.9 If an automated refund fails (for example because the Mollie connection has been broken or a right is missing), plevry reports this to the Operator and the Operator refunds the End Customer themselves.

9.10 The Operator is themselves responsible for their own VAT remittance, pricing and bookkeeping, including for payments made through plevry.

9.11 Online payment requires plevry Pro (Article 6.4) and a working Mollie connection. If either is missing, online payments are not available. The Operator can then use their booking page, in consultation with plevry, without online payment. plevry switches on this mode — the Operator cannot choose it themselves — because a booking page without a working payment method could otherwise arise by accident (for example through a broken Mollie connection) without anyone having decided that.

Article 10 — Availability, maintenance and warranties

10.1 plevry makes efforts to keep the Service available and reliable, but gives no guarantee of uninterrupted availability, error-free operation or a specific uptime. There is no SLA.

10.2 plevry may temporarily take the Service out of use for maintenance, updates or security. plevry tries to do this outside busy periods and to announce it if the interruption is expected to last longer than a brief outage.

10.3 plevry may change, add or remove features. plevry announces at least one month in advance a change that materially limits the core of the Service for the Operator; the Operator may then terminate (Article 15).

10.4 The Operator is themselves responsible for their own device, internet connection and email address. plevry is not responsible for outages at third parties, including Mollie, app stores, email providers and internet providers.

10.5 The Operator is advised to regularly make an export of their bookings through the app (available with plevry Pro, Article 6.4), and not to rely solely on plevry as the source of their records.

10.6 The exclusions in this article do not affect plevry's obligation to take appropriate technical and organisational security measures (see the data processing agreement, §5) or the liability arising from a failure to do so.

Article 11 — Personal data

11.1 For the personal data of End Customers, the Operator is the controller and plevry is the processor. This is set out in the data processing agreement, which forms part of the Agreement.

11.2 For the data of the Operator's own account, plevry is itself the controller. This is set out in the privacy statement.

Article 12 — Intellectual property

12.1 All rights to the Service, the software, the design, the texts and the plevry brand rest with plevry or its licensors. The Operator only receives the right of use under Article 4.2.

12.2 The data and texts the Operator enters themselves remain the Operator's. The Operator grants plevry the right to use that data to the extent necessary to provide the Service.

12.3 The Operator may not replicate, decompile, resell or offer the Service under their own name, except to the extent the law mandatorily permits.

Article 13 — Liability

13.1 plevry is liable for direct damage suffered by the Operator that results from a failure attributable to plevry in performing the Agreement.

13.2 Maximum. plevry's liability is limited, per event and for all events within twelve months combined, to the higher of (a) 1,000 € or (b) the total of the plevry Pro subscription fees paid over the twelve months preceding the event.

13.3 Liability is excluded for indirect damage, including consequential damage, lost profit, loss of revenue, missed bookings, reputational damage and loss of data to the extent the Operator did not use the export function while it was available to them (Article 10.5).

13.4 The limitations in this article do not apply in the case of intent or deliberate recklessness by plevry or its management, in the case of death or bodily injury, and not to the extent the law prohibits the limitation.

13.5 A claim lapses if the Operator has not reported it to plevry in writing within twelve months after discovering the damage or after they should have discovered it.

13.6 This article does not affect data subjects' rights to compensation under art. 82 GDPR. Those rights cannot be contractually limited. The allocation between plevry and the Operator in the event of a processing incident follows the data processing agreement.

Article 14 — Indemnification

14.1 The Operator indemnifies plevry against claims from End Customers and third parties relating to the Treatment Agreement, to the Operator's cancellation, rescheduling or no-show policy, to their prices or to their customer records, and reimburses the costs plevry reasonably incurs as a result.

14.2 This indemnification does not apply to the extent the claim results from a failure by plevry itself.

Article 15 — Term and termination

15.1 The Agreement applies for an indefinite period.

15.2 The Operator may terminate at any time, without notice period and without cost: by deleting the account in the app, or by an email to [email protected]. The Operator additionally cancels a running plevry Pro subscription themselves under Article 6.6; termination of the Agreement does not automatically end that subscription.

15.3 plevry may terminate with a notice period of 30 days, by email to the address known for the account.

15.4 plevry may suspend use with immediate effect or terminate the Agreement with immediate effect if the Operator uses the Service in violation of the law or of these terms, harms the operation or security of the platform, misuses the payment flow, or is in a state of bankruptcy or suspension of payments. plevry informs the Operator of the reason.

15.5 What happens to the data. Access to the Service ends after termination.

• If the Operator deletes their account, the business, the bookings, the customer data and the linked payment data are permanently deleted and the Mollie connection is revoked. This cannot be undone.
• The Operator makes their own export, before termination, of the data they want to keep, partly because they may be subject to their own statutory retention obligation (tax records).
• After termination, plevry retains only what it is legally required to retain, in particular its own financial records. See the privacy statement.
• §9 of the data processing agreement also applies.

Article 16 — Changing these terms

16.1 plevry may change these terms. A change is announced at least one month before the effective date by email or in the app.

16.2 In the event of a material change, plevry asks the Operator in the app to accept it again. plevry records, per document and per version, what was accepted and when. For a NEW Operator this happens when the business is created (Article 3.2); for an existing Operator, at the moment they accept the changed version in the app. If they do not accept it, acceptance follows from continued use after the effective date (Article 16.3) — the announcement under 16.1 serves as the notice for that.

16.3 If the Operator does not agree with the change, they may terminate until the effective date in accordance with 15.2. If the Operator continues to use the Service after the effective date, the new version applies.

Article 17 — Transfer

17.1 plevry may transfer its rights and obligations under the Agreement to a group company or to a legal entity in which the plevry activities are continued, including an entity yet to be established under the name plevry. The Operator grants their cooperation and consent for this in advance. plevry informs the Operator about the transfer before it takes effect.

17.2 The Operator may not transfer their rights and obligations under the Agreement without plevry's prior written consent. In the event of a takeover or transfer of the Operator's business, plevry grants that consent unless it has a good reason not to do so.

Article 18 — Miscellaneous

18.1 If a provision is void or not applicable, the remaining provisions remain in force and a provision is put in its place that reflects the original intent as closely as possible.

18.2 If plevry does not immediately exercise a right, this does not mean it waives that right.

18.3 These terms, together with the documents referred to in Article 2.3, form the entire agreement between the parties about the use of the Service.

18.4 The Dutch text of these terms is binding. A translation is solely an aid; in the event of a difference, the Dutch text prevails.

Article 19 — Applicable law and disputes

19.1 Dutch law applies to the Agreement.

19.2 Disputes are submitted to the court of The Hague, unless the law mandatorily designates a different court.

Article 20 — Contact

Falley B.V. (trading as "plevry") Oder 20, 2491 DC The Hague, the Netherlands Chamber of Commerce no. 91810760 Email: [email protected]

Part II — Data processing agreement

This data processing agreement ("Agreement") is part of, and forms part of, the terms and conditions in Part I and of the agreement between plevry and the Client for the use of the plevry booking platform (the "Service").

1. Parties and roles

• Controller ("Controller"): the Client — the business (sole trader / salon) that uses the Service to manage the appointments of its own customers (the "End Customers"). In the terms and conditions this party is called the "Operator"; that is the same party as the Client here.
• Processor: plevry — the plevry service, operated by Falley B.V., trading under the name plevry, having its registered office in The Hague, Oder 20, 2491 DC The Hague, the Netherlands, Chamber of Commerce no. 91810760. Where "plevry" is used below, this means Falley B.V.

The Controller determines the purpose and means of the processing of End Customers' personal data. plevry processes that data solely on the instructions of, and for the benefit of, the Controller, in order to provide the Service. For the data of the operator's own account (the owner's name/email), plevry is itself the controller; that falls under plevry's privacy statement, not under this Agreement.

2. Subject matter, nature and purpose of the processing

• Subject matter: managing online bookings and the associated communication/payment.
• Nature of the processing: collecting, recording, storing, consulting, sending (confirmation and reminder emails), and erasing/exporting on instruction.
• Purpose: providing the booking service (calendar, booking page, payment flow, reminders, accounting export) on behalf of the Controller.
• Duration: for as long as the underlying agreement with the Client runs, followed by the return/erasure in §9.

3. Categories of data subjects and personal data

• Data subjects: the Controller's End Customers.
• Personal data: name, email address, telephone number, appointment data (date/time, treatment, amount, status) and any notes entered by the End Customer/Controller.
• Special categories: plevry does not request or require any special categories of personal data. Note: for certain practitioners (e.g. therapeutic/clinical), an identifiable appointment may in fact constitute health data (art. 9 GDPR). The Controller does not record special categories of data in free-text fields unless it has a legal basis for doing so; plevry minimises the exposure (see §5, data minimisation).

4. Instructions

plevry processes the personal data solely on the basis of the Controller's documented instructions (including this Agreement and normal use of the Service), unless a statutory obligation requires otherwise (in which case plevry informs the Controller in advance, to the extent permitted). plevry notifies the Controller if, in its opinion, an instruction infringes the GDPR.

5. Security and data minimisation (art. 32 GDPR)

plevry takes appropriate technical and organisational measures, including:

• Tenant isolation at database level (Row-Level Security): every business sees only its own data; cross-tenant access is tested automatically (a regression test on every change).
• Encryption of payment tokens (Vault) and of transport over TLS.
• Least-privilege internal administration: plevry's internal support tool shows no personal data of End Customers (no names/email/phone; bookings show only date/time/treatment/amount/status), works with an allowlist of administrators, and records every administrator change in an append-only audit log (who/what/when).
• Server-side access only, with a service-role key the browser never reaches.
• No bulk export of personal data from the support tool; a Controller who needs an export obtains it from their own operator app.

6. Confidentiality

Persons who have access to the personal data on plevry's behalf are bound by confidentiality.

7. Sub-processors

• The Controller gives plevry general written authorisation to engage sub-processors (art. 28(2) GDPR). The sub-processors plevry currently engages are listed by name, purpose and processing location in Annex A, which forms part of this Agreement.
• plevry imposes on each sub-processor, by agreement, the same or equivalent obligations as under this Agreement (art. 28(4) GDPR). If a sub-processor fails to comply with those obligations, plevry remains fully liable to the Controller for that compliance.
• If plevry wants to add or replace a sub-processor, it announces this at least one month before the effective date by email to the address known for the account or in the app, stating the name of the sub-processor, what it is engaged for and the processing location.
• The Controller may object to an intended change until the effective date, by email to [email protected] and stating the reason. The parties then consult on whether the objection can be resolved. If that does not succeed, the Controller may terminate the main agreement free of charge until the effective date in accordance with Article 15.2 of the terms and conditions; plevry is not obliged to refrain from making the change.

8. Rights of data subjects, data breaches, DPIA

• plevry assists the Controller, to the extent reasonably possible, with requests from data subjects (access, correction, erasure, data portability) through the functionality of the Service.
• plevry reports a (suspected) data breach to the Controller without undue delay after discovery, with the information available as referred to in art. 33 GDPR.
• plevry supports the Controller, where applicable, with a data protection impact assessment (DPIA) and prior consultation (art. 35–36 GDPR).

9. Return and erasure

On termination, plevry erases the personal data or returns it at the Controller's request, and deletes existing copies, unless a statutory retention obligation requires otherwise. Deleting an account deletes the business and the associated data (see the account deletion function in the app).

Moving from plevry Pro to Free is not a termination within the meaning of this section: no personal data is deleted in doing so (see Article 6.9 of the terms and conditions).

10. Audits

plevry makes available to the Controller the information needed to demonstrate compliance with art. 28 GDPR, and enables audits (e.g. through a report or an independent statement), reasonably and with due regard for the confidentiality of other clients.

11. Transfers outside the EEA

Transfers to a third country take place only with an appropriate safeguard (e.g. EU standard contractual clauses / SCCs) and a transfer risk assessment. See Annex A for the current locations and safeguards (point of attention: email delivery).

12. Liability, term, applicable law

12.1 Liability

plevry's liability arising from or in connection with this Agreement is limited in the manner set out in Article 13 of the terms and conditions. That limitation applies to the main agreement and this Agreement together: there is one maximum, not two. That maximum is, per event and for all events within twelve months combined, the higher of (a) 1,000 € or (b) the total of the plevry Pro subscription fees paid over the twelve months preceding the event.

This limitation does not apply in the case of intent or deliberate recklessness, and not to the extent the law prohibits the limitation. The limitation does not affect:

• data subjects' rights to compensation under art. 82 GDPR — those cannot be written away between the parties;
• the joint and several liability that may follow from art. 82(4) GDPR, and the right of recourse under art. 82(5) GDPR between the parties in proportion to their share of the damage;
• fines a supervisory authority imposes on one party: those remain for the account of the party they are imposed on, unless the other party is the demonstrable cause of them.

The parties provide each other with reasonable cooperation in defending against a claim from a data subject or a supervisory authority.

12.2 Term and termination

This Agreement takes effect at the moment the Controller accepts it when creating their business, and runs for as long as the main agreement with plevry runs. It ends automatically and at the same moment as the main agreement; it cannot be terminated separately from it, because plevry may not provide the Service without this Agreement.

Obligations that by their nature continue — in particular §6 (confidentiality), §9 (return and erasure) and §10 (audits) — remain in force after termination, §10 for the duration of the statutory limitation period.

12.3 Amendment

plevry may amend this Agreement if legislation or regulation, a ruling of a supervisory authority or a change to the Service requires it. A change is announced at least one month before the effective date by email or in the app, and plevry records, per document and per version, what was accepted and when — see Article 16.2 of the terms and conditions for how that works for an existing Operator. If the Controller does not agree with the change, it may terminate the main agreement free of charge until the effective date.

12.4 Applicable law and disputes

Dutch law applies to this Agreement, including the GDPR and the Dutch GDPR Implementation Act (Uitvoeringswet AVG). Disputes are submitted to the court of The Hague, unless the law mandatorily designates a different court. This is consistent with Article 19 of the terms and conditions.

12.5 Order of precedence and language

In case of conflict between this Agreement and the terms and conditions, this Agreement prevails, to the extent it concerns the processing of End Customers' personal data. The Dutch text is binding.

Annex A — Sub-processors

plevry engages the following sub-processors to provide the Service. The Controller gives its authorisation for this by accepting this Agreement (art. 28(2) GDPR). Changes are announced in accordance with §7 of this Agreement, with the possibility to object described there.

Not in this annex, and deliberately not: Google Analytics and the Meta pixel on the marketing website plevry.com. These process only data of visitors to that website, for plevry's own purposes — never End Customer or booking data. They are therefore not a sub-processor under this Agreement. See the privacy and cookie statement.

For the same reason not in this annex: RevenueCat, which we use to keep track of whether a business has a running plevry Pro subscription. RevenueCat receives only the Operator's internal user ID — a random number, no name and no email address — and the status of their subscription. No End Customer or booking data ever goes to it. plevry is itself the controller for this, not a processor on the Operator's behalf; it is therefore set out in the privacy statement and in the internal register, and not here.

For the same reason not in this annex: LocationIQ (Unwired Labs), which we use to look up the business address and determine the time zone from it. Only what the Operator types in themselves about their own business is processed — never End Customer or booking data. plevry is itself the controller for this, not a processor; it is therefore set out in the privacy statement and in the internal register, and not here. If the Operator does not enter an address, LocationIQ is never called for their business.

This annex is the contractually binding list. plevry additionally keeps a more extensive internal register (art. 30 GDPR) with the safeguards in place per party; that register is available to the Controller on request and is not part of this Agreement — so that it can be updated without a contract amendment being required for it.