BookkMe
For businessFor clients
GuidesContact
For businessFor clientsGuidesContact

English

УкраїнськаPolski

This version takes effect on December 1, 2026.

BookkMe Data Processing Agreement

Version: 2026-12-01 · Effective from: 1 December 2026

This agreement is between the business that uses BookkMe ("the business", the controller) and Nocturne Properties LLC, Kyiv, Ukraine ("BookkMe", the processor). It sets out how BookkMe processes personal data on the business's behalf, as required by Article 28 of the EU General Data Protection Regulation (GDPR) and other applicable data protection law. BookkMe's full details are in Annex 4, Part A.

The agreement forms part of the BookkMe Terms of Service for business owners. The owner accepts it on the business's behalf by creating a business, and it applies for as long as the business exists in BookkMe.

It is available in English, Polish and Ukrainian; each language describes the same agreement, and no language automatically overrides another. Terms not defined here have the meaning given in the GDPR.

Contents

  • 1. Scope and roles
  • 2. The business's instructions
  • 3. The business's responsibilities
  • 4. Confidentiality
  • 5. Security
  • 6. Subprocessors
  • 7. International transfers
  • 8. Assisting the business
  • 9. Personal data breaches
  • 10. Deletion at the end of processing
  • 11. Information and audits
  • 12. Liability
  • 13. Changes
  • 14. Law and disputes
  • 15. Contact
  • Annex 1. Description of the processing
  • Annex 2. Technical and organisational measures
  • Annex 3. Subprocessors
  • Annex 4. Standard contractual clauses

1. Scope and roles

1.1. The business is the controller of the personal data it records in its BookkMe workspace: its clients, its employees and the appointments between them ("workspace data"). Annex 1 describes the processing.

1.2. BookkMe processes workspace data only as the business's processor. This agreement does not cover data for which BookkMe is itself the controller, such as user accounts, sign-in, devices, notification settings, legal-document records, crash reports and support correspondence. The BookkMe Privacy Policy describes that processing.

1.3. Where this agreement conflicts with the Terms of Service on the processing of workspace data, this agreement prevails.


2. The business's instructions

2.1. BookkMe processes workspace data only on the business's documented instructions. The business gives those instructions by this agreement, by the Terms of Service, and by its actions in the app: creating, importing, editing, exporting and deleting records, setting the client data retention period, granting employees permissions and deleting the business. By the same terms the business also instructs BookkMe to link a client record to the BookkMe account of the person whose confirmed email address it holds; to update the business's client and employee records about an account holder when they change their name, phone or email address in their account, and to merge into their client record another client record that holds their new confirmed email address; and to include the records the business keeps about an account holder in that account holder's own data export. Further instructions must be in writing, including by email to [email protected], and must be technically feasible within the service.

2.2. BookkMe may also process workspace data where Union or Member State law to which it is subject requires it. In that case BookkMe informs the business of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest.

2.3. BookkMe immediately informs the business if, in its opinion, an instruction infringes the GDPR or other data protection law. BookkMe may suspend that instruction until the business confirms or changes it.


3. The business's responsibilities

3.1. The business is responsible for the lawfulness of the workspace data and of its instructions. In particular it must:

  • have a lawful basis for every record it creates or imports, including clients imported from an employee's phone contacts;
  • inform its clients and employees about the processing, including people whose data it receives indirectly;
  • set a client data retention period that fits its purposes;
  • not submit health or other special-category data, or data about criminal convictions, unless it has established the additional legal condition and safeguards required for that processing (BookkMe Privacy Policy, section 5);
  • keep cancellation, decline and price-adjustment reasons free of personal details and sensitive information, as the Terms of Service require;
  • give each employee only the permissions they need, and remove or suspend access that is no longer needed.

3.2. The business answers requests from its clients and employees about workspace data. BookkMe passes on to the business, without undue delay, any such request it receives, and does not answer it itself unless the business instructs it to.


4. Confidentiality

BookkMe ensures that everyone it authorises to process workspace data, including its employees, has committed to confidentiality or is under an appropriate statutory obligation of confidentiality, and processes the data only as needed to operate and support the service.


5. Security

5.1. BookkMe implements the technical and organisational measures in Annex 2, taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing and its risks.

5.2. BookkMe may update those measures, provided the overall level of security is not reduced.


6. Subprocessors

6.1. The business gives BookkMe general authorisation to engage subprocessors. The current subprocessors are listed in Annex 3.

6.2. At least 14 days before adding or replacing a subprocessor, BookkMe informs the business by email to the address of the owner's BookkMe account, naming the subprocessor and its service, and publishes an updated version of this agreement. The business may object on reasonable data protection grounds by writing to [email protected] before the change takes effect. BookkMe then either does not use the new subprocessor for that business's workspace data or, where that is not reasonably possible, tells the business so; the business may then end this agreement free of charge by exporting its data and deleting the business, and BookkMe does not use the new subprocessor for that business's workspace data until the business has had 14 days to do so.

6.3. BookkMe imposes data protection obligations on each subprocessor that provide sufficient guarantees for the processing, as required by Article 28(4) GDPR; a provider's standard terms that incorporate its data processing addendum satisfy this where they meet that standard. BookkMe remains liable to the business for its subprocessors' performance of those obligations.


7. International transfers

7.1. BookkMe's servers, database and backups are in the EU. Some subprocessors process data outside the European Economic Area, as listed in Annex 3. No one accesses workspace data from Ukraine. BookkMe's employees and director may access it remotely from other countries where they are located, which can be outside the EEA.

7.2. BookkMe transfers workspace data outside the EEA only under a mechanism permitted by Chapter V of the GDPR, such as an adequacy decision, including the EU-U.S. Data Privacy Framework where the recipient is certified, or standard contractual clauses, together with any supplementary measures the transfer requires.

7.3. On request, BookkMe provides the business with a copy of the relevant safeguards; confidential information may be redacted.

7.4. Where the GDPR applies to the business's processing of workspace data, BookkMe's processing of that data is a transfer to a third country, because BookkMe is established in Ukraine. For that transfer the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914 apply between the business as data exporter and BookkMe as data importer. Module Two (controller to processor) applies; where the business itself processes the workspace data on behalf of another controller, Module Three (processor to processor) applies instead. The clauses are incorporated by reference and completed as set out in Annex 4, and both parties are deemed to have signed them when this agreement takes effect between them. Where this agreement or the Terms of Service conflict with the clauses, the clauses prevail.


8. Assisting the business

8.1. BookkMe assists the business, through appropriate technical and organisational measures and taking into account the nature of the processing, in answering requests from data subjects to exercise their rights. The app provides the main tools for this: viewing and editing records, deleting a client, exporting the business's data, and the retention period. BookkMe helps by email at [email protected] with any request the app cannot handle.

8.2. Taking into account the nature of the processing and the information available to it, BookkMe assists the business in meeting its obligations on security, personal data breach notification, data protection impact assessments and prior consultation with a supervisory authority (Articles 32 to 36 GDPR).


9. Personal data breaches

9.1. BookkMe notifies the business owner by email without undue delay after becoming aware of a personal data breach affecting workspace data.

9.2. The notification describes, as far as then known, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact for more information. BookkMe provides further information in phases as it becomes available.

9.3. BookkMe takes reasonable steps to contain the breach and mitigate its effects. Notifying the supervisory authority and the data subjects remains the business's decision and responsibility, with BookkMe's assistance.


10. Deletion at the end of processing

10.1. The business chooses whether its workspace data is returned, deleted, or both. The owner can export the business's data in the app at any time, which is how BookkMe returns it, and deleting the business is the instruction to delete it. Before an owner's unused account, and with it the business, is deleted, BookkMe warns the owner 60, 30 and 7 days ahead, and it does not delete that account while another member of the business has been active within the last 3 years.

10.2. When the business is deleted, including when the owner's account is deleted or removed for 3 years without use as the Privacy Policy describes, BookkMe deletes the workspace data from the live service. Names, contact details, notes and client descriptions are encrypted with a key per person, which is destroyed with the data, and copies of the keys in backups are deleted within 7 days, so after that those details can no longer be read from any backup. Other deleted data leaves backups within 30 days, as the backups expire; if a backup taken before the deletion is ever restored, BookkMe deletes the data again before the service resumes.

10.3. BookkMe keeps workspace data after the end of processing only where Union or Member State law requires it to.


11. Information and audits

11.1. BookkMe makes available to the business all information necessary to demonstrate compliance with this agreement and Article 28 GDPR, including written answers to reasonable security questionnaires.

11.2. Where that information is not sufficient, the business, or an auditor it mandates who is bound by confidentiality and is not a competitor of BookkMe, may carry out an audit, including an inspection. The business gives at least 30 days' written notice, audits at most once a year unless a supervisory authority requires it or a personal data breach justifies it, and bears its own costs. Audits are conducted during business hours, without access to other customers' data and without disrupting the service.


12. Liability

Each party's liability under this agreement is governed by the Terms of Service and Article 82 GDPR. Nothing in this agreement limits liability that cannot lawfully be limited, or a data subject's rights against either party.


13. Changes

BookkMe may amend this agreement to reflect changes in law, guidance from supervisory authorities, the service or its subprocessors. BookkMe publishes each version with a date and keeps earlier versions available; changes take effect as described for changes to the Terms of Service. A change does not reduce the protection of workspace data below what Article 28 GDPR requires.


14. Law and disputes

This agreement is governed by the law of Ukraine. Disputes are resolved by the courts of Kyiv, Ukraine. The standard contractual clauses in section 7.4 are instead governed by the law, and subject to the courts, chosen in Annex 4. This does not affect the competence of supervisory authorities or the rights of data subjects.


15. Contact

Data protection questions about workspace data: [email protected].


Annex 1. Description of the processing

Subject matter and purpose. Providing the BookkMe workspace to the business: publishing its services and hours, taking, scheduling and managing appointments and appointment requests, keeping client and employee records, sending booking notifications to its clients and employees, importing selected contacts, exporting its data, and applying its retention settings.

Nature of the processing. Collection, recording, organisation, storage, retrieval, consultation, alteration, transmission to the business's employees and clients through the app, by push notification and by email, export, erasure and destruction.

Duration. For as long as the business exists in BookkMe, followed by deletion as in section 10.

Data subjects.

  • the business's clients, whether or not they have a BookkMe account;
  • the business's employees, including the owner in their role as an employee;
  • people whose contacts an employee imports as clients.

Personal data.

  • client records: name, phone, email, a description written by the business, notes, the link to the client's BookkMe account if any, and when the client last visited or changed;
  • appointments and appointment requests: client and employee names and contact details, service, time, price, status, the client's note, cancellation and decline reasons, completion details and price adjustments with their reasons;
  • employee records: name, contact details, services, working hours, days off, permissions, whether access is suspended, and assigned appointments;
  • data exports of the business's records.

Special categories. None are intended. The business must not submit them unless section 3.1 is met.

Retention.

Data How long
Client records Until the business deletes them, or automatically after the retention period the business sets: 12 to 120 months after the client's last visit or change, 36 by default
Appointments While the business exists; client details and notes are removed when the client record is erased
Appointment requests 60 days after the requested appointment ends
Data exports 72 hours
Records that a client was erased (identifiers only) 60 days, so an erasure can be repeated after a backup is restored
Internal messages between parts of the service that could not be delivered 30 days
Server logs 14 days
Backups 30 days; names, contact details, notes and client descriptions in them unreadable 7 days after the person's erasure (Annex 2)

Annex 2. Technical and organisational measures

  • Sign-in. Users sign in with passkeys; there are no passwords to steal. Deleting an account and other sensitive actions are confirmed with a passkey.
  • Encryption. Connections to the service use TLS. The database and backups are encrypted at rest. In addition, the names, email addresses, phone numbers, notes and client descriptions of account holders, clients and employees, and notification addresses, are encrypted with a separate key for each person, itself encrypted with a master key kept outside the database. Lookups by email address or phone number use a keyed hash (HMAC) instead of the plain value.
  • Backups. Backups are kept on a separate server from the database for 30 days. Erasing a person destroys their key, and backups of the keys are kept for 7 days, so the person's encrypted details cannot be read from any backup after that. A restore is followed by repeating any erasures made after the backup was taken.
  • Access within the business. Each employee sees and changes only what the permissions granted by the business allow; a suspended employee loses access at once. Every query for a business's records is limited to that business.
  • Access by BookkMe. Access to production data is limited to the people who operate the service, who are bound by confidentiality, and is used only to operate and support it. No one accesses production data from Ukraine, and the servers refuse SSH and VPN connections from Ukrainian addresses.
  • Network protection. Traffic passes through Cloudflare's reverse proxy and DDoS protection, with rate limits on sign-in and code-sending routes.
  • Data minimisation. The app uses no analytics or advertising identifiers, emails carry no open or click tracking, and only the contacts a user selects are uploaded on import.
  • Retention. Automatic deletion of client records, appointment requests, exports, logs, inactive devices and unused accounts, as listed in Annex 1 and the Privacy Policy.
  • Monitoring. Server logs and metrics are monitored to detect failures and abuse; logs are kept for 14 days.

Annex 3. Subprocessors

Subprocessor Service Location of processing Transfer mechanism
Hostinger International Ltd., Cyprus Servers, database and backups; emails to the business's employees and clients, and BookkMe's mailbox Servers in Lithuania and Germany, email in France and Germany (EU) Not applicable; Hostinger's Data Processing Addendum applies standard contractual clauses to its own subprocessors outside the EEA
Cloudflare, Inc. DNS, reverse proxy, DDoS protection and network security Global network; United States company Cloudflare Customer DPA: Data Privacy Framework where applicable, standard contractual clauses otherwise
Google (Firebase Cloud Messaging) Push notifications to the business's employees and clients Global processing, including the United States Firebase Data Processing and Security Terms: Data Privacy Framework and standard contractual clauses where applicable

Annex 4. Standard contractual clauses

This annex completes the standard contractual clauses incorporated by section 7.4.

Options.

Clause Choice
Clause 7, docking clause Does not apply
Clause 9(a), use of sub-processors Option 2, general written authorisation. BookkMe informs the business specifically, by email to the owner, of any intended addition or replacement of a sub-processor at least 14 days in advance, and handles an objection, as in section 6.2
Clause 11(a), redress The optional wording on an independent dispute resolution body does not apply
Clause 13(a), supervision The supervisory authority in Part C
Clause 17, governing law Option 2: the law of the EU Member State in which the business is established; where that law does not allow third-party beneficiary rights, or the business is not established in an EU Member State, the law of Poland
Clause 18(b), choice of forum The courts of the EU Member State in which the business is established; where the business is not established in an EU Member State, the courts of Poland

Part A. List of parties.

  • Data exporter: the business, as identified by its business profile in BookkMe. Contact: the business owner, at the email address of the owner's BookkMe account. Activities relevant to the transfer: using the BookkMe workspace as described in Annex 1. Role: controller under Module Two, or processor under Module Three. Signature and date: deemed signed when this agreement takes effect between the business and BookkMe.
  • Data importer: Nocturne Properties LLC (ТОВ «НОКТЮРН ПРОПЕРТІС»), EDRPOU code 46113892, 2/37 Leiptsyzka St., apt. 43, Kyiv, 01015, Ukraine. Contact: [email protected]. Activities relevant to the transfer: providing and supporting the BookkMe service. Role: processor. Signature and date: deemed signed when this agreement takes effect between the business and BookkMe.

Part B. Description of the transfer.

  • Categories of data subjects and of personal data: as in Annex 1.
  • Sensitive data: none is intended (section 3.1). If the business submits any, it is protected by the measures in Annex 2, including access limited by the permissions the business grants.
  • Frequency: continuous, for as long as the business exists in BookkMe.
  • Nature of the processing: as in Annex 1. The data is stored on servers in the EU and accessed by the people who operate the service from the countries where they are located, never from Ukraine (section 7.1).
  • Purpose of the transfer and further processing: providing the BookkMe workspace to the business, as in Annex 1.
  • Retention: as in the retention table in Annex 1, followed by deletion as in section 10.
  • Transfers to sub-processors: to the subprocessors in Annex 3, for the services listed there; subject matter, nature and duration as in Annex 1.

Part C. Competent supervisory authority. The supervisory authority responsible for the business's compliance with the GDPR as regards the transfer: that of the EU Member State in which the business is established, or its lead supervisory authority where it has establishments in several. Where the business is not established in the EU but has appointed a representative under Article 27(1) GDPR, that of the Member State in which the representative is established. Where it is not required to appoint one (Article 27(2) GDPR), that of a Member State in which the data subjects whose personal data is transferred are located.

Annex II of the clauses, technical and organisational measures: Annex 2 of this agreement.

Annex III of the clauses, list of sub-processors: Annex 3 of this agreement.

Version history

  • Version 2026-12-01

    Takes effect on December 1, 2026

BookkMe — a source-available booking app for Android and iOS.

App source
Server source
FSL-1.1-ALv2 license
Self-hosting permission

Copyright © 2026 Nocturne Properties LLC. All rights reserved.

Privacy Policy
Terms of Service
Contact