Ugrás a tartalomhoz

Data Processing Agreement

Last updated: November 17, 2026. Effective from December 17, 2026.

1. Parties, scope and acceptance

1.1 This Data Processing Agreement ("DPA") is between Bookingmood B.V., Keizersgracht 520H, 1017 EK Amsterdam, the Netherlands, registered with the Dutch Chamber of Commerce under number 89056132 ("Bookingmood"), and the customer that holds a Bookingmood account ("Customer").

1.2 This DPA forms part of Bookingmood's Terms & Conditions (the "Terms"). Customer accepts it by accepting the Terms, which happens when Customer creates an account or uses the Service through an account. No signature is needed for it to apply. On request to support@bookingmood.com, Bookingmood provides a copy of this DPA signed by an authorized representative. A signed copy has the same content as the version published on this page on the date of signing.

1.3 For the Customer Personal Data described in Annex 1, Customer is the controller and Bookingmood is the processor. Where Customer itself acts as a processor for another controller (for example a property manager working for owners), Bookingmood acts as Customer's Subprocessor, and Customer confirms that it is authorized by that controller to give the instructions in this DPA.

1.4 This DPA does not cover personal data that Bookingmood processes as a controller for its own purposes, such as Customer's account and billing details, the user accounts of Customer's users and their sign-in data (credentials, two-factor authentication factors and sign-in logs), support conversations with Bookingmood, Bookingmood's website analytics and Bookingmood's own marketing emails. The Privacy Policy describes that processing. Where a support conversation includes Customer Personal Data, such as booking or guest details, Bookingmood processes that data under this DPA.

1.5 If the Terms and this DPA conflict on the processing of Customer Personal Data, this DPA prevails. If this DPA and Standard Contractual Clauses that apply under clause 7 conflict, the Standard Contractual Clauses prevail.

2. Definitions

In this DPA:

  • "GDPR" means Regulation (EU) 2016/679 (General Data Protection Regulation).

  • "Data Protection Law" means the GDPR, the Dutch GDPR Implementation Act (Uitvoeringswet AVG), and any other data protection law that applies to the processing of Customer Personal Data, including the UK GDPR and the Swiss Federal Act on Data Protection where they apply.

  • "Service" means the Bookingmood booking platform as described in the Terms, including the admin app, booking widgets, customer websites, the public API and related features.

  • "Customer Personal Data" means the personal data that Bookingmood processes on behalf of Customer in providing the Service, as described in Annex 1.

  • "Subprocessor" means a third party engaged by Bookingmood that processes Customer Personal Data.

  • "Standard Contractual Clauses" or "SCCs" means the standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914 of June 4, 2021, with the UK Addendum or the Swiss adaptations described in clause 7 where those apply.

  • "Data Privacy Framework" means the EU–US Data Privacy Framework, recognized as adequate by Commission Implementing Decision C(2023) 4745 of July 10, 2023.

  • "Controller", "processor", "data subject", "personal data", "personal data breach", "processing" and "supervisory authority" have the meaning given in the GDPR.

3. Processing on Customer's instructions

3.1 Bookingmood processes Customer Personal Data only on Customer's documented instructions, including with regard to transfers to a third country, unless EU or Member State law to which Bookingmood is subject requires otherwise. In that case Bookingmood informs Customer of that legal requirement before processing, unless that law prohibits this on important grounds of public interest.

3.2 Customer's instructions are the Terms, this DPA, and Customer's configuration and use of the Service: its settings, the integrations it connects, and the messages, emails and SMS it sends through the Service. Customer may give further instructions in writing, as long as they are consistent with the Terms and this DPA.

3.3 Bookingmood immediately informs Customer if, in its opinion, an instruction infringes the GDPR or other EU or Member State data protection provisions. Bookingmood may suspend carrying out that instruction until Customer confirms or changes it.

3.4 Customer is responsible for the lawfulness of its instructions and of the processing it initiates. This includes having a legal basis for the processing, informing guests and other data subjects, and obtaining consent where the law requires it (for example for SMS, as set out in clause 20 of the Terms).

3.5 When Customer connects a third-party service to the Service, Bookingmood sends Customer Personal Data to that service on Customer's instruction. Such services include payment providers (Stripe, Mollie, Square, Clover), channel and pricing tools (such as PriceLabs and Google Vacation Rentals), calendar feeds, webhooks, and API or MCP clients that Customer authorizes. These providers are Customer's own processors or independent controllers under Customer's own agreements with them. They are not Bookingmood's Subprocessors.

3.6 Address autocomplete and address lookup in the Service use the Google Maps Platform. When a guest or user types an address, Bookingmood's servers send the typed text, a random session identifier and the language to Google. They don't send the visitor's IP address or contact details. Google processes this data as an independent controller under the Google Controller-Controller Data Protection Terms, which the Google Maps Platform terms incorporate, not as Bookingmood's Subprocessor. Customer authorizes this transfer. The Subprocessor List shows it with the transfer mechanism.

4. Confidentiality and personnel

4.1 Bookingmood ensures that every person it authorizes to process Customer Personal Data is bound by a contractual or statutory duty of confidentiality.

4.2 Bookingmood staff access Customer Personal Data only as far as needed to provide the Service, to answer support requests from Customer, to prevent abuse and fraud, or to comply with the law.

5. Security

5.1 Bookingmood implements the technical and organizational measures described in Annex 2 to ensure a level of security appropriate to the risk, as required by Article 32 GDPR. In doing so it takes into account the state of the art, the costs of implementation, the nature, scope, context and purposes of the processing, and the risks to data subjects, in particular from a personal data breach.

5.2 Bookingmood may change these measures as technology and threats develop, as long as the overall level of security does not decrease.

5.3 Customer is responsible for the security of its own use of the Service, including keeping its users' credentials and API keys confidential, enabling two-factor authentication where appropriate, and giving its users only the permissions they need.

6. Subprocessors

6.1 Customer gives Bookingmood general written authorization to engage Subprocessors. The current Subprocessors are listed on the Subprocessors page (the "Subprocessor List"), which forms Annex 3 of this DPA.

6.2 Bookingmood informs Customer at least 30 days before it adds or replaces a Subprocessor. It does so by updating the Subprocessor List and by email to the admins of Customer's organization.

6.3 Customer may object to a new Subprocessor on reasonable grounds relating to data protection, by email to support@bookingmood.com within that notice period. The parties will then discuss the objection in good faith. If Bookingmood cannot address the objection, for example by not using that Subprocessor for Customer's data, Customer may terminate the affected Service before the change takes effect.

6.4 If a Subprocessor must be replaced urgently to protect the security or availability of the Service, Bookingmood may do so with shorter notice. It informs Customer as soon as possible, and Customer's right to object under clause 6.3 applies from that notice.

6.5 Bookingmood engages each Subprocessor, directly or, for Anthropic, through Vercel's AI Gateway under Vercel's data processing terms, under a written contract that imposes the same data protection obligations as this DPA, in particular sufficient guarantees to implement appropriate technical and organizational measures (Article 28(4) GDPR). Bookingmood remains fully liable to Customer for the performance of each Subprocessor's obligations.

7. International transfers

7.1 Bookingmood's database and file storage are hosted in Frankfurt, Germany, and the application runs in Frankfurt, Germany.

7.2 Some Subprocessors are established outside the European Economic Area (EEA), or process Customer Personal Data there, as shown in the Subprocessor List. Bookingmood transfers Customer Personal Data outside the EEA only if one of the following applies:

  • the European Commission has decided that the country or recipient ensures an adequate level of protection (Article 45 GDPR), including recipients in the United States certified under the Data Privacy Framework; or

  • the transfer is subject to appropriate safeguards under Article 46 GDPR, in particular the Standard Contractual Clauses (Module 3, processor to processor), together with supplementary measures where a transfer impact assessment shows they are needed.

7.3 Customer authorizes the transfers described in the Subprocessor List. If an adequacy decision that a transfer relies on is withdrawn or invalidated, Bookingmood will rely on another transfer mechanism or stop the transfer.

7.4 Where the UK GDPR applies to Customer Personal Data, the following applies:

  • Transfers from Customer to Bookingmood need no further safeguard, because UK law recognizes the EEA as adequate.

  • Bookingmood transfers the data to a country outside the UK and the EEA only under UK adequacy regulations, including the UK Extension to the Data Privacy Framework for certified recipients in the United States, or under the Standard Contractual Clauses together with the International Data Transfer Addendum issued by the UK Information Commissioner (the "UK Addendum").

  • References in this DPA to the GDPR include the UK GDPR, and references to a supervisory authority include the UK Information Commissioner.

7.5 Where the Swiss Federal Act on Data Protection (FADP) applies to Customer Personal Data, the following applies:

  • Transfers from Customer to Bookingmood need no further safeguard, because Switzerland recognizes the EEA countries as adequate.

  • Bookingmood transfers the data to a country outside Switzerland and the EEA only to a country or recipient that Switzerland recognizes as adequate, including recipients certified under the Swiss–US Data Privacy Framework, or under the Standard Contractual Clauses adapted for Switzerland: the Swiss Federal Data Protection and Information Commissioner (FDPIC) is the competent supervisory authority as far as the FADP applies, references to the GDPR include the FADP, and data subjects in Switzerland can bring claims in their place of habitual residence.

8. Assistance to Customer

8.1 Data subject requests. The Service lets Customer find, export, correct and delete the personal data of its guests and users. Taking into account the nature of the processing, Bookingmood also assists Customer by appropriate technical and organizational measures, insofar as possible, in responding to requests from data subjects exercising their rights under Chapter III GDPR. If Bookingmood receives such a request directly, it forwards it to Customer without undue delay and does not respond to it itself, except on Customer's instructions or where the law requires.

8.2 Articles 32 to 36. Taking into account the nature of the processing and the information available to it, Bookingmood assists Customer in ensuring compliance with its obligations under Articles 32 to 36 GDPR: security of processing, notification of personal data breaches to the supervisory authority and to data subjects, data protection impact assessments, and prior consultation with the supervisory authority.

8.3 Supervisory authorities. Bookingmood cooperates with supervisory authorities in the performance of their tasks, as far as this concerns Customer Personal Data, and informs Customer of any such request unless the law prohibits this.

8.4 Costs. Bookingmood provides the assistance in this clause free of charge where it is reasonable in scope. For assistance that requires substantial effort beyond the Service's features and the documentation in this DPA, Bookingmood may charge reasonable costs, agreed with Customer in advance.

9. Personal data breaches

9.1 Bookingmood notifies Customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data.

9.2 Bookingmood sends the notification by email to the admins of Customer's organization. As far as the information is available, it describes: the nature of the breach, including the categories and approximate number of data subjects and records concerned; the likely consequences; the measures taken or proposed to address the breach and limit its effects; and a contact point for more information. Where not all information is available at once, Bookingmood provides it in phases without undue delay.

9.3 Bookingmood promptly takes reasonable measures to contain the breach and limit its consequences, documents the breach, and cooperates with Customer's investigation. Customer decides whether to notify the supervisory authority and data subjects. Bookingmood does not notify them on Customer's behalf unless Customer instructs it to or the law requires it.

9.4 A notification under this clause is not an acknowledgment of fault or liability.

10. Return and deletion of Customer Personal Data

10.1 Return. While Customer has an account, Customer can export Customer Personal Data at any time through the exports in the admin app and through the public API. When Customer's use of the Service ends, Customer chooses whether to export its data before it is deleted. On request within the retention period in clause 10.2, Bookingmood helps Customer export its data in a common, machine-readable format.

10.2 Deletion. Customer Personal Data is kept while Customer's organization is active. An organization is inactive when it has no active trial or subscription and no pre-paid credit left.

  • If Customer deletes its organization in the Service, the organization is closed immediately, but its data is kept so it can be restored. Bookingmood permanently deletes the data 365 days after the organization became inactive, without further notice.

  • If Customer's organization becomes inactive without being deleted, Bookingmood emails its admins 30 days before deletion and permanently deletes the data 365 days after the organization became inactive.

Customer may ask Bookingmood to delete the data sooner by email to support@bookingmood.com. Bookingmood handles such a request within 30 days.

10.3 Logs and backups. The activity log of an organization is deleted 30 days after Customer deletes the organization, even though its other data can still be restored until it is permanently deleted under clause 10.2. A restored organization therefore has no activity log from before. If the organization is permanently deleted without Customer deleting it first, its activity log is deleted 30 days after that. Price calculation records are deleted together with the organization's data. Operational logs are deleted on the shorter schedules in Annex 2. Deleted data can remain in Bookingmood's encrypted database backups for up to 7 days, until they expire. Bookingmood uses backups only to restore the Service after an incident.

10.4 Legal retention. Bookingmood may keep Customer Personal Data longer only where EU or Member State law requires it to store the data. It then keeps the data confidential and processes it only for that purpose. Customer remains responsible for its own legal retention duties, such as keeping invoices it issued to guests, and must export that data before deletion.

10.5 On request, Bookingmood confirms the deletion to Customer in writing.

10.6 Aggregated statistics. Bookingmood may keep aggregated statistics derived from the Service, such as the number of bookings and subscriptions, without time limit to analyze its business. These statistics do not identify Customer's users, guests or other individuals and are not Customer Personal Data.

11. Information and audits

11.1 Bookingmood makes available to Customer all information necessary to demonstrate compliance with Article 28 GDPR and this DPA. This includes this DPA and its annexes, answers to reasonable security questionnaires, and, where available, the security certifications or audit reports of its main Subprocessors.

11.2 If that information is not sufficient to demonstrate compliance, or a supervisory authority requires it, Bookingmood allows for and contributes to audits, including inspections, by Customer or an independent auditor mandated by Customer. The auditor must be bound by confidentiality. Customer gives at least 30 days' notice, audits no more than once in any 12 months unless a personal data breach or a supervisory authority's request gives reason to, and bears its own costs.

11.3 An audit must not interfere unreasonably with Bookingmood's operations and must not give access to the data of Bookingmood's other customers or to information that would compromise the security of the Service.

12. General terms

12.1 Duration. This DPA applies for as long as Bookingmood processes Customer Personal Data. Clauses 10 and 11 continue to apply after the Terms end, until all Customer Personal Data has been deleted.

12.2 Liability. The limitations of liability in the Terms apply to this DPA, except where Data Protection Law does not allow liability toward data subjects to be limited.

12.3 Changes. Bookingmood may change this DPA to reflect changes in the law, guidance from supervisory authorities, or changes to the Service, provided the protection of Customer Personal Data does not decrease. Bookingmood announces material changes at least 30 days before they take effect, by email to the admins of Customer's organization. Changes to the Subprocessor List follow clause 6.

12.4 Notices. Notices to Bookingmood go to support@bookingmood.com or to the address in clause 1.1. Notices to Customer go to the email addresses of the admins of Customer's organization.

12.5 Severability. If a provision of this DPA is invalid, the rest remains in force, and the parties replace the invalid provision with a valid one that comes as close as possible to its purpose.

12.6 Governing law and jurisdiction. This DPA is governed by the laws of the Netherlands. Disputes are submitted exclusively to the competent court in Amsterdam.

Annex 1 – Details of the processing

Subject matter. Processing of personal data needed to provide the Service: managing bookings, availability, pricing, payments and invoices for vacation rentals; guest communication by email and SMS; and Customer's booking widgets, websites and API.

Duration. For as long as Customer uses the Service, and afterwards until the data is deleted under clause 10.

Nature of the processing. Collection (through widgets, websites, forms, the admin app, the API and calendar imports), recording, storage, organization, retrieval, consultation, use, translation at Customer's request, processing with AI models for support and features of the Service, transmission (emails, SMS, webhooks, calendar feeds, integrations Customer connects, and redirects to pages Customer sets after a booking), restriction, and deletion.

Purposes. Providing the Service to Customer under the Terms; support at Customer's request; securing the Service and preventing abuse and fraud; complying with legal obligations.

Categories of data subjects and types of personal data

Data subjectsTypes of personal data
Customer's users (admins, members, owners with access to selected rentals)Name, email address, phone number, language, role and permissions in Customer's organization; the activity log of changes they make
Guests and prospective guestsName, email address, phone number, postal address, country, language; booking details (dates, rental, number and type of guests, prices, discounts, answers to booking form fields Customer defines); payment and refund records (amount, status, method type, payment provider reference; no full card numbers); invoices; messages, emails and SMS exchanged with Customer, and their delivery and open events; reviews; notes Customer adds
Other contacts Customer records (for example co-guests, owners, cleaners and other service providers)Name, contact details, and the tasks, notes and bookings they are linked to
Visitors to Customer's websites and widgetsPages viewed, referrer, country and a random session identifier for site statistics; IP address, used briefly for rate limiting and abuse prevention; address text entered in address autocomplete

Special categories of data. The Service is not intended for special categories of personal data (Article 9 GDPR) or data relating to criminal convictions. Customer must not request such data, or national identification numbers, through custom booking form fields unless it has a legal basis to do so and has assessed the risks.

Frequency. Continuous, for as long as the Service is used.

Retention. As set out in clause 10 and in the log retention periods in Annex 2.

Annex 2 – Technical and organizational measures

These are the measures in place on the date of this DPA.

Hosting and location

  • The database and file storage run on Supabase in AWS region eu-central-1 (Frankfurt, Germany). The application runs on Vercel functions in region fra1 (Frankfurt, Germany).

  • Physical security of data centers is provided by these hosting providers.

Encryption

  • All traffic to the Service and to its APIs uses TLS (HTTPS).

  • Data in the database, file storage and backups is encrypted at rest by the hosting provider.

Access control for Customer's users

  • Authentication through Supabase Auth; passwords are stored only as hashes. Sign-in with Google is also available.

  • Optional two-factor authentication with an authenticator app (TOTP) or phone. Once a user enables it, every request to the database API and file storage requires a session that completed the second factor; this is enforced in the database itself.

  • Roles and per-rental permissions within an organization. Postgres row-level security enforces in the database which rows each user, API key, widget and website visitor can read or change.

  • API keys are limited to the scopes Customer gives them, enforced in the database. OAuth access tokens for connected apps expire and can be revoked.

  • A captcha (Cloudflare Turnstile) protects sign-up and sign-in, and rate limits protect public endpoints.

Access by Bookingmood staff

  • Staff use a separate back office with a dedicated database role. Staff accounts can enable the same two-factor authentication as Customer's users.

  • Staff access only what they need for support, abuse prevention and operating the Service (clause 4).

  • To help with a support request, staff can sign in to the account of one of Customer's users. Each such session is recorded, and changes made in it are logged as made by the staff member.

  • Server-side secrets are kept in the hosting providers' encrypted environment configuration and Supabase Vault, never in source code or in the browser.

Logging and accountability

  • Database triggers record every change to bookings, payments, invoices, contacts, messages, reviews and the organization's settings in an audit log, with who made it: a user, an API key, a staff member or a system job. Only columns without personal data, such as statuses, dates and amounts, are logged with their values. Other columns are logged by name only.

  • Customers can view their organization's activity log, without staff identities.

Integrity of inputs and integrations

  • Incoming webhooks from payment and messaging providers are verified by signature. Scheduled jobs require a secret.

  • Input is validated on the server. URLs that users provide (such as calendar feeds) are fetched through a guarded fetcher that blocks requests to internal networks.

  • Prices are calculated on the server, and the calculation behind each booking's price is recorded, so it can be checked later.

Availability and resilience

  • Managed Postgres with automatic daily backups, kept on a rolling 7-day basis.

  • Emails are queued and retried; scheduled jobs are written to be safe when they run twice or late.

  • A public status page informs customers about incidents.

Change management

  • All code and database schema changes are kept in version control and checked automatically (type checks, linting and tests) before deployment.

  • Schema changes are made only through migrations; a daily check flags any change to the production schema that is not in a migration.

Data minimization and retention

DataKept for
API request logs7 days
Webhook delivery logs7 days
Email queue7 days
Calendar synchronization logs7 days
Support assistant runs90 days
Website statistics (no IP addresses)12 months
Authentication logs12 months
Email open events12 months
Activity log of settings changes12 months
Activity log of bookings and related records, such as payments, refunds, invoices, contacts, messages and reviews7 years
Price calculation records (no guest contact details)7 years
Activity log of a deleted organization30 days after Customer deletes the organization, or after it is permanently deleted (clause 10.3)

Abuse prevention

  • Daily limits on emails to guests, and automated hourly detection of organizations that appear to send spam.

Organization

  • Everyone with access to Customer Personal Data is bound by confidentiality.

  • A written incident response procedure names an incident lead and a backup, and sets out how incidents are recorded, contained, assessed and reported to customers within the deadline in clause 9.1. Every incident is recorded in a breach register. The procedure is reviewed every year and after each incident.

Annex 3 – Subprocessors

The Subprocessors are listed on the Subprocessors page, which forms part of this DPA. Changes to it follow clause 6.

Utoljára módosítva 2026. november 17.