Klendr

Data Processing Agreement

Last updated: 2026-11-16

This DPA forms part of the Klendr Terms of Service between the Customer (controller) and HOTPIE DIGITAL OÜ, registry code 16786310, Liivamäe tn 3-16, 10132 Tallinn, Estonia (Klendr, processor). It meets Article 28 of Regulation (EU) 2016/679 (GDPR). It is accepted together with the Terms; a signed copy is available on request at support@klendr.me.

2.1 Subject and duration

  1. Klendr processes Client Data on the Customer's behalf to provide the Service. The details are in Appendix A.
  2. This DPA applies for as long as Klendr processes Client Data for the Customer, including the deletion period after the account is closed.

2.2 Instructions

  1. Klendr processes Client Data only on the Customer's documented instructions. The Terms, this DPA and the Customer's use and settings of the Service are the Customer's complete instructions. Further instructions must be in writing and within the Service's functions.
  2. Klendr will tell the Customer if it believes an instruction breaks data protection law, and may refuse to follow it.
  3. Klendr may process Client Data otherwise only where EU or Estonian law requires it; it will tell the Customer first unless that law forbids it.
  4. Klendr does not sell Client Data and does not use it for its own purposes, including to train AI models. Klendr may use aggregated, anonymised statistics that identify no person or Customer.

2.3 Confidentiality

Klendr ensures that everyone it allows to process Client Data (staff, contractors, Partners) is bound by confidentiality and only accesses Client Data as needed for their task.

2.4 Security

Klendr applies the technical and organisational measures in Appendix B, as required by Article 32 GDPR. Klendr may update them if the level of protection does not decrease.

2.5 Sub-processors

  1. General authorisation. The Customer gives Klendr general written authorisation to engage sub-processors. The current list is in Appendix C and published at klendr.me/subprocessors.
  2. Notice of changes. Klendr will announce any new or replaced sub-processor at least 30 days in advance by updating that page and by email to the account address.
  3. Objection. The Customer may object in writing within those 30 days on reasonable data protection grounds. The parties will try to find a solution. If none is found, the Customer may terminate the affected Service and receive a pro-rata refund of prepaid fees for that Service from the date of termination.
  4. Klendr imposes on each sub-processor data protection obligations no less protective than this DPA and remains liable to the Customer for their performance.
  5. Partners. Authorised Klendr Partners are sub-processors. They access a Customer's account only through the Klendr admin interface, only with the Customer's consent given in the product, for a limited time, for onboarding and support. Each access is logged. Partners may not copy, export or photograph Client Data.

2.6 International transfers

  1. Klendr stores Client Data in the European Economic Area (EEA).
  2. Where a sub-processor processes Client Data outside the EEA, Klendr ensures a lawful transfer under Chapter V GDPR: an adequacy decision (including the EU–US Data Privacy Framework for certified US companies) or the Standard Contractual Clauses (Commission Decision (EU) 2021/914), with additional measures where needed. Appendix C states the mechanism for each sub-processor.

2.7 Help with data subject rights

  1. The Service lets the Customer find, correct, export and delete Client Data.
  2. If a Client contacts Klendr directly, Klendr will forward the request to the Customer without undue delay and will not answer it itself unless the Customer instructs it.
  3. Klendr will give reasonable further help where the Customer cannot handle a request with the Service's functions.

2.8 Help with other obligations

Klendr will give the Customer reasonable help with security, breach notification, data protection impact assessments and prior consultation (Articles 32–36 GDPR), taking into account the information available to Klendr. Help beyond the Service's normal functions may be charged at reasonable cost.

2.9 Personal data breaches

  1. Klendr will notify the Customer of a personal data breach affecting Client Data without undue delay and no later than 48 hours after becoming aware of it.
  2. The notice will describe, as far as known: what happened, the categories and approximate number of persons and records affected, likely consequences, measures taken or proposed, and a contact person. Klendr will add information as it becomes available.
  3. Klendr will take reasonable steps to contain the breach and reduce its effects. Notifying the supervisory authority and Clients remains the Customer's responsibility as controller.

2.10 Deletion or return at the end

  1. The Customer can export Client Data at any time and for 30 days after the account is closed.
  2. Klendr then deletes Client Data. Copies that remain in backups, if any, are deleted within a further 30 days.
  3. Klendr may keep Client Data only where EU or Estonian law requires it, and only for as long as required, protected under this DPA.

2.11 Audits

  1. Klendr will make available the information needed to show compliance with this DPA.
  2. By default an audit is done by documents and a written questionnaire, which Klendr answers within 30 days, up to once a year.
  3. An on-site audit is allowed only if a supervisory authority requires it or after a personal data breach affecting the Customer; not more than once a year; with at least 30 days' written notice; during business hours; by the Customer or an independent auditor bound by confidentiality; at the Customer's cost. It must not give access to other customers' data or to Klendr's confidential information beyond what is needed.

2.12 Liability and priority

  1. Each party's liability under this DPA is subject to the limits in the Terms, except where GDPR does not allow a limit.
  2. If this DPA conflicts with the Terms on personal data, this DPA prevails.

Appendix A — Processing details

ItemDetails
Subject matterProviding the Klendr booking and client-management Service to the Customer
DurationTerm of the Customer's account plus the deletion periods in section 2.10
Nature of processingHosting and storage, display in the dashboard, online booking, sending email and SMS reminders and messages, facilitating prepayments through Stripe, push notifications, AI assistant replies (if enabled), support and onboarding access with consent, backup and deletion
PurposeRunning the Customer's bookings, client records, reminders, payments and communication with Clients
Data subjectsThe Customer's Clients and prospective Clients; the Customer's staff and Users; people who write to the Customer through channels connected to the AI assistant
Categories of dataIdentity and contact (name, phone, email, language); booking data (services, dates, times, prices, visit history, comments, notes entered by the Customer); payment data (amounts, status, Stripe references; card numbers are held only by Stripe); message content (reminders, marketing messages, AI-assistant conversations); technical data (IP address and time of booking, accepted booking rules, consent records)
Special categoriesNot required by the Service. The Customer may enter health information (for example allergies or contraindications) only where it has a legal basis (section 1.13 of the Terms)
FrequencyContinuous
RetentionAs set by the Customer during the account. Client contacts with no bookings in the last 12 months are deleted automatically, and the Customer is notified. After closure: section 2.10

Appendix B — Technical and organisational measures

  1. Location. Application servers in Germany (Hetzner) and the database in Ireland (Supabase on AWS eu-west-1).
  2. Encryption. All connections use TLS (HTTPS). The database provider encrypts stored data at rest.
  3. Access control in the product. Each Customer's data is separated by database row-level security. Users have roles (administrator, master, accountant); team members see only what their role allows.
  4. Access by Klendr staff and Partners. Access to a Customer's account only with the Customer's consent in the product, limited in time, through the admin interface. Every support session is logged (who, whose account, start and end). Partners work under a written agreement that forbids copying or exporting data.
  5. Admin and infrastructure access. Restricted to named people, with individual credentials; secrets kept out of the code repository; two-factor authentication where the provider offers it.
  6. Payments. Card data is collected and stored only by Stripe (PCI DSS Level 1); Klendr never stores card numbers.
  7. Abuse protection. Bot protection (Cloudflare Turnstile) and rate limits on the public booking page and sign-in.
  8. Backups and recovery. Redundant infrastructure of the hosting and database providers, and database backups where the provider's plan includes them.
  9. Data minimisation and deletion. Automatic deletion of inactive Client contacts after 12 months; deletion of closed accounts under section 2.10.
  10. People. Everyone with access is bound by confidentiality and instructed on data protection.
  11. Incidents. Breaches are assessed and notified under section 2.9; each incident is recorded with its facts, effects and remedial action.
  12. Vendors. Sub-processors are chosen for their security and bound by data protection terms (Appendix C).

Appendix C — Sub-processors and transfers

Published at klendr.me/subprocessors. Last updated 16 November 2026.

Sub-processorPurposeDataLocation of processingTransfer outside EEA and safeguard
Supabase, Inc. (USA)Database, authentication, file storageAll Client DataIreland (AWS eu-west-1)Support access from the USA possible: EU–US Data Privacy Framework where certified, otherwise SCCs
Hetzner Online GmbH (Germany)Application hostingClient Data passing through the applicationGermany (Falkenstein)None
Stripe Payments Europe, Limited (Ireland), with Stripe, Inc. (USA)Client prepayments, card storageClient name, email, payment dataEEA and USAData Privacy Framework where certified, otherwise SCCs
Think Intermedia SIA, trading as Sendberry (Latvia, reg. no. 40103671346)SMS deliveryClient phone number, message contentEU (Latvia); delivered through mobile networks of the recipient's countryNone for processing in the EU
Resend, Inc. (USA)Email delivery (confirmations, reminders, Customer marketing emails)Client email, name, message contentUSAData Privacy Framework where certified, otherwise SCCs
Cloudflare, Inc. (USA)Bot protection on the booking page (Turnstile)IP address and browser data of booking-page visitorsGlobal networkData Privacy Framework where certified, otherwise SCCs
Google Ireland Limited (Firebase Cloud Messaging), with Google LLC (USA)Push notifications to the Customer's appDevice token, notification text (may include a Client name and time)EEA and USAData Privacy Framework where certified, otherwise SCCs
Anthropic, PBC (USA)AI assistant replies (beta, only if the Customer enables it)Conversation content, Client name, booking detailsUSAData Privacy Framework where certified, otherwise SCCs
Authorised Klendr Partners (individuals or companies under contract with Klendr)Onboarding and supportData visible in the Customer's account during a consented session; no exportEU (currently Latvia)None

Not sub-processors: WhatsApp, Instagram (Meta), Telegram and other channels are the Customer's own accounts that it connects to the AI assistant under those providers' terms (section 1.12 of the Terms).