This version takes effect on December 1, 2026.
BookkMe Privacy Policy
Version: 2026-12-01 · Effective from: 1 December 2026
This policy explains what personal data BookkMe collects when you use the BookkMe app and service, why, who sees it, how long we keep it, and what rights you have.
This document is available in English, Polish and Ukrainian. Each language describes the same policy; no language automatically overrides another or limits mandatory local rights. Contact us if you find a difference.
Contents
- Who we are
- Our two roles
- What data we collect
- Why we use it and on what basis
- Notes and sensitive information
- Who sees your data
- Transfers to other countries
- How long we keep it
- How we protect it
- Your rights
- Age
- Changes to this policy
- Contact
1. Who we are
BookkMe is operated by Nocturne Properties LLC, Kyiv, Ukraine ("BookkMe", "we", "us"). Our postal address is in section 13.
Questions about this policy or your data: [email protected].
We process personal data under the Law of Ukraine "On Personal Data Protection", including the EU General Data Protection Regulation (GDPR) where it applies. The applicable rules depend on our establishment, the processing and the countries where we offer the service; the language you choose does not determine them.
2. Our two roles
BookkMe connects businesses that take appointments (salons, studios, clinics, tutors and others) with the people who book them.
- For your BookkMe account we are the controller. We decide how your account, sign-in and notification data is used.
- For the workspace records a business keeps about its clients and employees we act as the business's processor. A business that uses BookkMe decides what it records about its clients (contact details, descriptions, notes, appointment history) and how long it keeps it. This also covers employee scheduling and access records processed on its instructions. That business is the controller of those records and is responsible for them. We store and process them only on the business's instructions, under a data processing agreement with that business, published at bookkme.com/dpa. Questions or requests about such a record go first to the business; we will pass on any request we receive and help the business answer it.
3. What data we collect
Account. Your first and last name, your email address (confirmed with a one-time code before the account is created), and, if you add it, your phone number.
Sign-in. BookkMe uses passkeys instead of passwords. We store your passkey's public key and identifier, never your fingerprint, face or device PIN, which stay on your device. For each device you sign in on we store an identifier the app creates when it is installed, the device name the system reports (usually its model), sign-in tokens, and when you last signed in. We record the date you were last active so that we can delete unused accounts (section 8).
Notifications. Your device's push notification token and language, your notification settings, and whether you turned on email notifications.
Legal document records. Which versions of this policy you acknowledged and of the Terms of Service you accepted, and when.
Support. If you contact us by email, we receive your email address, the contents of your message and anything you attach, such as usage logs.
Bookings you make. The business, services, employee, time, price, status, and anything you write in the optional note. A business may add a cancellation or decline reason, completion details and a price adjustment with its reason.
If you work for a business on BookkMe. Your employee profile in that business (name, contact details, services, working hours, days off, permissions, and whether your access is suspended), and the appointments assigned to you.
If you own a business on BookkMe. The business profile (name, description, address, map location, contacts and social links, working hours, currency, client data retention period), its services and prices.
Records businesses keep about their clients (we act as processor, section 2): the client's name, phone, email, a description written by the business, notes, and appointment history.
Data exports you or your business request, kept until they expire (section 8).
Contacts, only if you import clients. A business owner or employee can import clients from their phone's contacts after allowing the app to access them. The app reads the contacts on your device and shows them to you; only the contacts you select (name, phone and email) are sent to us and become client records of your business. We never upload your address book.
Crash reports. When the app crashes, it sends Firebase Crashlytics technical details about the error and your device (model, operating system and app version, an installation identifier, and the time of the crash), so we can fix it. We do not deliberately attach your account identifier, name, email or business/client records. Crash traces can include exception messages, so reports are not guaranteed to be anonymous. Crash reports are off by default and are sent only if you turn them on in Settings → Account → Privacy. You can turn them off there at any time, which also deletes reports not yet sent.
On your device. The app keeps a copy of the data you see (your profile, businesses, appointments, and the clients and employees you manage) on your device so it opens quickly. The copy is deleted when you sign out. If you turn on biometric unlock, the check happens on your device and we receive nothing.
Technical data. Your IP address and request details pass through Cloudflare and our servers for routing and to protect the service against abuse. Our server logs may contain your IP address, account identifiers and error details.
We do not access your location or photos, the app uses no analytics or advertising identifiers, our emails do not track whether you open them or click their links, we do not use your data for advertising, and we do not sell it.
4. Why we use it and on what basis
| Purpose | Data | Basis |
|---|---|---|
| Create and run your account, sign you in, keep your devices signed in | Account, sign-in | Performing our contract with you (the Terms of Service) |
| Let you book, change and cancel appointments and pass your booking to the business | Account, bookings | Performing our contract with you |
| Send booking and account notifications by push, and by email if you turn it on | Notifications, bookings | Performing our contract with you |
| Send account notices (deletion of an unused account, a data export is ready) by email | Account | Performing our contract with you |
| Run a business's workspace: employees, services, schedule, clients, appointments | Business, employee and client records | As processor, the business's instructions (section 2); the business determines and discloses its own legal bases |
| Record terms acceptance and receipt of privacy information | Legal document records | Our legitimate interest in documenting the agreement and the privacy information provided |
| Import the clients you select from your contacts | Selected contacts | Our contract with the business; the business's instructions (section 2) |
| Keep the service secure, prevent abuse, find and fix errors | Technical data, sign-in | Our legitimate interest in a secure, working service |
| Find and fix app crashes | Crash reports | Your consent, given by turning crash reports on; you can withdraw it by turning them off |
| Answer support requests | Support emails and their attachments | Our legitimate interest in resolving requests and maintaining the service |
| Answer requests to exercise your data protection rights | What the request needs | Applicable legal obligations |
| Comply with the law and requests from authorities | What the law requires | Our legal obligations |
Acknowledging this policy records that you received the information; it is not consent to every processing activity. Where consent is required, it must be requested separately for a specific purpose and can be withdrawn through [email protected] or the relevant setting, without deleting your account. Withdrawal does not affect earlier lawful processing.
What you must give us. To create an account you need to give your first and last name, confirm your email address and create a passkey; without them we cannot create the account. Your phone number, a note on a booking, notifications and crash reports are optional.
Automation. We do not profile you or use automated scoring for eligibility, pricing or advertising. Retention and dormancy deletions run automatically as described in section 8, including deletion of an unused account after three warnings. Contact [email protected] if you believe an automatic deletion is incorrect.
5. Notes and sensitive information
Use notes and client descriptions only for information needed to arrange an appointment. Do not enter health information or other specially protected data unless the business has first explained the purpose and established the additional legal condition required for that processing. Where explicit consent is required, the business must obtain it separately; typing a note or acknowledging this policy does not by itself provide it. BookkMe is a booking tool, not a medical record system.
Cancellation, decline and price adjustment reasons are visible to both sides and must not contain personal details or sensitive information. Cancellation and price adjustment reasons remain in the appointment record after client details are removed (Terms of Service, section 7).
6. Who sees your data
- The business you book with sees your name, phone, email, the booking and your note. If the business already has a client record with your confirmed email address, BookkMe links it to your account so your history with that business stays in one place. When you change your name, phone or email, we update your client record in every business you have booked with and your employee profile in every business you work for. If a business has another client record with your new confirmed email, it is merged into yours.
- A business's employees see what their permissions in that business allow. Clients see the business's profile and the name of the employee serving them.
- Our service providers, acting as processors for customer data in the services listed below, and as subprocessors when we act for a business. Some providers also act as controllers for specified service or network data under their own privacy notices:
| Provider | What it does | Where |
|---|---|---|
| Our hosting provider | Servers, database and backups; our email: sending the app's emails (sign-up codes, notifications, account notices) and hosting our mailbox for [email protected] and [email protected] | Servers in Lithuania and Germany, email in France and Germany (EU) |
| Cloudflare, Inc. | DNS, reverse proxy, DDoS protection, and other network security | Global network; United States company |
| Google (Firebase Cloud Messaging, Firebase Crashlytics) | Delivers push notifications; collects crash reports | Global processing, including the United States |
- Authorities, when the law requires it.
Cloudflare describes its separate processing of network and service data in its privacy policy. Google describes Firebase service-data processing in its privacy information.
7. Transfers to other countries
Our servers, database and backups are in Lithuania and Germany (EU), and our email, including the mailbox for [email protected] and [email protected], is in France and Germany (EU). Cloudflare's proxy and security network processes traffic globally. Google/Firebase may process data in the United States; Google may also use facilities in other countries.
Cloudflare's Data Processing Addendum provides for Data Privacy Framework transfers where applicable and standard contractual clauses for other restricted transfers. Our hosting provider's data processing agreement covers our servers and our email, and applies standard contractual clauses to its own subprocessors outside the EEA. Firebase Cloud Messaging and Crashlytics are covered by Google's Firebase Data Processing and Security Terms, whose transfer provisions include the Data Privacy Framework and standard contractual clauses where applicable.
No one accesses production data from Ukraine. Our employees and our director may access it remotely from other countries where they are located, which can be outside the EEA. Such access is limited to operating and supporting the service and uses encrypted connections. Where access from abroad constitutes an international transfer, we apply the safeguards required by applicable law. To request a copy of relevant safeguards, contact [email protected]; confidential information may be redacted.
8. How long we keep it
| Data | How long |
|---|---|
| Your account | Until you delete it. An account not used for 3 years is deleted; we warn you 60, 30 and 7 days before. An owner's account is kept while another member of their business has been active within that time. |
| A device you signed in on | Deleted after 30 days without use. |
| Email confirmation codes | 10 minutes. |
| Copies of the emails we send you (sign-up codes, notifications, account notices), kept in our sending mailbox | 5 years after sending, then deleted automatically. |
| A business's client records | As long as the business keeps them, at most the retention period the business sets (12 to 120 months since the client's last visit or change; 36 by default). After that they are deleted automatically. A business can delete a client sooner. |
| Appointments | Kept while the business exists, with no automatic age-based deletion of appointment history. Client details and notes are removed when the client record is erased, including under the client's separate retention period. |
| Appointment requests | 60 days after the requested appointment ends. |
| Data exports | 72 hours. |
| Legal document records | Until your account is deleted. |
| Support correspondence | 24 months after the last message in the conversation; longer only while needed to establish, exercise or defend a legal claim. |
| Records that an account or client was erased (identifiers only) | 60 days, so that an erasure can be repeated after a backup is restored. |
| Server logs | 14 days. |
| Internal messages between parts of our service that could not be delivered (may contain booking or profile details) | 30 days. |
| Crash reports | Google starts removing crash traces and associated identifiers from live and backup systems after 90 days; this is not a guaranteed completion deadline. |
| Backups | 30 days. Names, contact details, notes and client descriptions in them become unreadable 7 days after the person is erased (section 9). |
When you delete your account, we delete your profile, sign-in data, devices and notification settings, remove you as a client and as an employee from every business, cancel your upcoming appointments, and erase your client details and note from appointments and replace your employee name and remove the employee account link. Cancellation and price adjustment reasons and other appointment details remain; they must not contain personal details. Remaining appointment identifiers, service and time details, or identifying text in other fields can still allow a person to be identified. Your name, contact details and notes are encrypted with a key of your own, which the deletion destroys. Copies of that key in our backups are deleted within 7 days, so after that those details can no longer be read from any backup, although the backups themselves are kept for 30 days; your other data leaves the backups as they expire. If we ever restore a backup taken before the deletion, we erase your data again before the service resumes.
If you own a business, deleting your account also deletes that business with its employees, clients, services and appointments; export the business's data in the app first. The same happens when an owner's unused account is deleted.
A business is deleted only together with its owner's account; its employees, clients, services and appointments are deleted with it.
9. How we protect it
Sign-in uses passkeys, so there is no password to steal. Connections are encrypted (TLS). The database and backups are encrypted at rest, and backups are kept on a separate server from the database. On top of that, each person's name, email address, phone number, notes and client description, and the addresses we send notifications to, are encrypted with a key of that person's own, which is itself encrypted with a master key kept outside the database. Deleting the person destroys their key (section 8). To find an account or client by email address or phone number without decrypting it, we store a keyed hash (HMAC) of it, deleted with the record. Access to production data is limited to the people who operate the service. Each business's employees only see what their permissions allow.
10. Your rights
You have the right to:
- access and export your data. In the app, request a data export (once a day); it is kept for 72 hours once ready.
- correct it. Edit your profile in the app. Changing your email address needs a code sent to the new address.
- delete it. Delete your account in the app, in Settings → Account; this is confirmed with your passkey. If you can no longer use the app, request deletion by writing to [email protected] from your account's email address. What is deleted, what is kept and for how long is described in section 8.
- object to processing based on our legitimate interests, and ask us to restrict processing.
- withdraw your consent at any time, without affecting what we did before. To stop crash reports, turn them off in the app.
- know who processes your data and why, and to receive this information in a clear form.
- complain to the Ukrainian Parliament Commissioner for Human Rights. Where GDPR applies, you may also complain to a supervisory authority in the EEA country of your habitual residence, workplace or the alleged infringement.
These rights apply under the conditions and exceptions in the applicable law; portability is distinct from the app's export feature.
For anything you cannot do in the app, write to [email protected]. The app's daily export limit and 72-hour download window do not limit your statutory rights. We may ask for proportionate information to verify your identity, including an alternative if you cannot access your account email. Where GDPR applies, we respond without undue delay and within one month; a permitted extension of up to two further months is explained within the first month. Under Ukrainian law, we tell you within 10 working days whether a request for access will be fulfilled and fulfil it within 30 calendar days of receipt; any other shorter mandatory local deadline also applies. Requests are normally free; any lawful refusal or fee is explained with the available remedies. For a business's client or employee record, contact the business (section 2).
11. Age
You must be at least 16 to create a BookkMe account. We do not knowingly allow anyone younger to create an account. If you believe a child under 16 has an account, contact us and we will delete it.
12. Changes to this policy
When we change this policy we publish a new version with a new date and keep earlier versions available. The app asks you to read and acknowledge the new version; that acknowledgement is not blanket consent to processing. If a change affects how we use data you already gave us, we tell you before it takes effect.
13. Contact
- Company: Nocturne Properties LLC
- Registration number: EDRPOU code 46113892
- Postal address: 2/37 Leiptsyzka St., apt. 43, Kyiv, 01015, Ukraine
- Email: [email protected]
- Company phone: +380 73 059 70 41
- Company email: [email protected]
Version history
-
Version 2026-12-01
Takes effect on December 1, 2026