In brief
- Undernapse Sp. z o.o. is the controller of account, organisation, billing, security and telemetry data.
- For Booking and Invitee data the Host is the controller and we are the processor, acting on the Host’s instructions.
- We process data to run, bill and secure the service — not to build advertising profiles.
- Data is held in the EEA by default; transfers outside it rely on the SCCs, an adequacy decision or the EU–US Data Privacy Framework.
- You can reach us at support@kallenda.app, and complain to UODO at ul. Stawki 2, 00-193 Warsaw.
Controller and contact
The controller of the personal data described in this policy is Undernapse Sp. z o.o., ul. Hoża 86 lok. 410, 00-682 Warsaw, Poland, KRS 0001037160, NIP 7011145585, REGON 525353982, share capital PLN 5,400.00. In this policy, “Kallenda”, “we”, “us” and “our” mean that company. Kallenda is the platform brand; the company is the contracting party and the controller.
Privacy questions and requests go to support@kallenda.app. We answer within one month of receiving a request, as Article 12(3) GDPR requires, and may extend that by two further months for a complex or repeated request — if we do, we tell you within the first month and explain why. We have not appointed a data protection officer, because our processing does not meet the criteria that make one mandatory; the address above is the contact point for data-protection matters.
Our roles: controller and processor
We act in two roles at the same time, and which one applies to you matters. For some data we decide the purposes and means; for Booking data the Host decides, and we act only on the Host’s documented instructions.
| Data | Controller | Our role |
|---|---|---|
| Account, organisation, membership and host-profile data | Undernapse Sp. z o.o. | Controller |
| Subscription, billing, invoice and fiscal-receipt data | Undernapse Sp. z o.o. | Controller |
| Staff, audit, security and telemetry data | Undernapse Sp. z o.o. | Controller |
| Booking and Invitee data on a Host’s Scheduling Page | The Host | Processor |
| Event Type, availability and Booking content published by the Host | The Host | Processor |
As processor we handle Booking data only to provide the service, under a data processing agreement that incorporates Article 28 GDPR. Booking data belongs to the Host, we do not use it for our own purposes, we do not sell it and we do not use it to train advertising models. The agreement is available from support@kallenda.app. We are not a joint controller with a Host for any data.
Subscription payments are processed by Stripe Payments Europe as our processor. Payments for Paid Bookings are different: they run on the Host’s own connected Stripe account, the Host is the merchant of record, and Stripe’s relationship with the Host is governed by Stripe’s terms. We never hold the Invitee’s card details and we never invoice the Invitee.
What data we process
We collect what the service needs to work, what the law requires and what keeps it secure. The categories below describe that data in plain terms rather than listing database fields.
- Account and organisation data. Name, email address, hashed password or identity-provider identifier, language, time zone, organisation name, role and the handle used in the Scheduling Page address.
- Host-profile and schedule data. Display name, public profile description, availability, date overrides, buffers, minimum notice and booking-window settings.
- Event Type and Booking data. Event Type title, description, duration, location, questions and price; Booking times, status and answers, and the Booking Snapshot taken when the Booking was made.
- Invitee data. The name, email address, answers and notes an Invitee supplies at booking, and correspondence about that Booking.
- Calendar metadata. Calendar identifiers, connection status and the busy times imported from a connected calendar; we do not read the content of external events beyond what the provider exposes to compute availability.
- Billing and tax data. Billing profile, tax identifiers, country, Plan, invoices, corrections, fiscal receipts, payment status and the last four digits of a payment method as returned by the provider.
- Notification delivery records. Recipient, template identifier, locale, provider identifier, delivery status and timestamps, kept without the message content.
- Technical, security and audit data. IP address, user agent, request times, session metadata, rate-limit counters, error events with redacted identifiers, and an immutable record of privileged actions.
- Support and complaint records. The correspondence you send us, the case record and the outcome.
We do not ask for special-category data and we do not want it in Booking questions. If a Host’s question invites health, religious or other special-category information, the Host is responsible for a lawful basis; our own processing of it is limited to storing it for the Host as processor.
Calendar data is obtained from the calendar provider after the Host authorises the connection. Invitee data is obtained from the Invitee, or from the Host where the Host collected it or asked us to collect it through a Booking question. Where we receive data from someone other than the person it relates to, we provide the information in this policy to that person at the latest when we first contact them or disclose the data.
Purposes and legal bases
Every purpose below is tied to a legal basis under Article 6 GDPR. Where we rely on legitimate interests, we have balanced them against your rights and you may object as described in section 8. Where we rely on consent, you may withdraw it at any time without affecting processing that happened before the withdrawal.
| Purpose | Data | Legal basis |
|---|---|---|
| Creating and running your account and Organisation | Account and organisation data | Article 6(1)(b) — contract |
| Publishing Scheduling Pages and taking Bookings | Event Type, schedule and Booking data | Article 6(1)(b); as processor for Invitee data |
| Calendar sync and Busy Time calculation | Calendar metadata | Article 6(1)(b) — contract |
| Transactional notifications about Bookings | Recipient address and delivery metadata | Article 6(1)(b); Article 6(1)(c) for notices the law requires |
| Subscription billing, invoices and fiscal receipts | Billing, payment and invoice data | Article 6(1)(b); Article 6(1)(c) — tax and accounting law |
| Security, abuse prevention and audit | Technical, security and audit data | Article 6(1)(f) — legitimate interests |
| Support, complaints and legal claims | Correspondence and case records | Article 6(1)(b); Article 6(1)(f) |
| Aggregated service analytics, live queries only | Event and usage data | Article 6(1)(f) — legitimate interests |
| Electronic delivery of a fiscal receipt | Email address | Article 6(1)(a) — consent |
| Processing Booking data for the Host | Booking and Invitee data | Article 28 GDPR — on the Host’s instructions |
The last row is not our own purpose: the Host chooses the legal basis for that processing and we act on the Host’s documented instructions.
- Our legitimate interests are running a secure and reliable service, preventing fraud and abuse, keeping records that let us answer claims, understanding at an aggregate level how the product is used, and meeting our accountability obligations. We keep them narrow and we do not override your rights with them.
- Analytics means live aggregate queries with a maximum twelve-month window; there is no separate analytics warehouse and no individual behavioural profile.
- Marketing We do not market to Invitees. We contact Hosts about the service and their account, under Article 398 of the Polish Electronic Communications Act — with prior consent, or within the soft opt-in for existing customers, and always with an unsubscribe route.
Recipients and subprocessors
We share personal data only where the service needs it, where the law requires it or where you ask us to. The providers that process data for us are listed, with their role and location, on the Subprocessors page, which forms part of this policy.
- Infrastructure, identity, email, push, monitoring and error-tracking providers, each under a data processing agreement and limited to the data its function needs.
- Payment, invoicing and fiscalisation providers, for subscription billing and, on the Host’s connected account, for Paid Booking payments.
- Google and Microsoft, where a Host connects a calendar, so that busy times can be read and Booking events written.
- The Host, who sees the Booking in their dashboard because the Host is its controller.
- Our accountant and, where needed, our lawyers and auditors under confidentiality, and authorities or courts where the law requires disclosure — we check the legal basis of a request first.
We do not sell or rent personal data, and we do not disclose it to advertising networks or data brokers. There are no third-party advertising or tracking scripts on the service.
Transfers outside the EEA
Our primary store and application infrastructure are in the European Union, in the Frankfurt region. Some providers are established outside the EEA or receive support from outside it, so a limited transfer can happen — for calendar sync, push delivery, error monitoring or support.
- An adequacy decision of the European Commission for the destination country.
- The Standard Contractual Clauses (SCCs), with the supplementary measures the transfer impact assessment requires.
- The EU–US Data Privacy Framework, where the recipient is certified for the part of the transfer it covers.
We keep a transfer impact assessment for each provider that receives data outside the EEA and review it when the provider, the destination or the law changes. A copy of the safeguard is available from support@kallenda.app. We do not claim that all data stays in the EU; we say where the primary store is and what safeguard covers each transfer.
Retention periods
We keep data for as long as we need it for the purpose it was collected for, then delete or anonymise it. A Host’s own retention setting for Booking data can shorten the default within the limits the service offers.
| Data | Retention period |
|---|---|
| Account and organisation data | While the account exists, plus a 30-day soft-delete window; then deletion, except tax and billing records |
| Booking and Invitee data | 24 months per organisation by default, configurable between 3 and 60 months; an erasure request may shorten it |
| Notification delivery records (metadata only) | 5 full calendar years after the transaction year |
| Audit entries | 12 months hot; 24 months when flagged to an incident |
| Data-subject request evidence | 24 months after the case is closed, unless a claim is open |
| Backups | 35-day rolling lifecycle, encrypted |
| Billing and tax records | 5 years from the end of the tax year, as Polish tax and accounting law requires |
| Aggregated analytics | Live queries only, maximum 12-month window, no warehouse copy |
When the retention period for Booking data ends, we delete the fields that identify the Invitee and keep a Booking skeleton — the fact that a booking existed, its time and its status — so that the Host’s schedule, statistics and accounting remain consistent. An erasure request handled by the Host is applied on the Host’s instruction.
Your rights and the UODO complaint route
Subject to the conditions in the GDPR, you have the right to:
- access your data and receive a copy, with information about how we process it;
- have inaccurate or incomplete data corrected or completed;
- have your data erased where we no longer have a lawful reason to keep it;
- restrict processing while a question about accuracy, lawfulness or our legitimate interests is resolved;
- receive the data you gave us in a structured, commonly used, machine-readable format, and ask us to transmit it where that is technically feasible;
- object to processing based on our legitimate interests, and to any direct marketing at any time;
- withdraw a consent you gave, without affecting processing that relied on it before the withdrawal;
- not be subject to a decision based solely on automated processing that produces legal or similarly significant effects.
Write to support@kallenda.app to exercise a right. We answer within one month, extendable by two months for complex or repeated requests, and the request is free. We may ask for information that lets us verify that the request comes from the person concerned, but not more than we need for that purpose.
Some of the data is necessary to enter into the contract with us: without account and billing data we cannot open the account or bill the Subscription. Optional fields are marked as optional, and where we process data because the law requires it, refusing to provide it means we cannot lawfully provide the service.
You have the right to complain to a supervisory authority, in particular in the country where you live, where you work or where the alleged infringement happened. For us that authority is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO), ul. Stawki 2, 00-193 Warsaw, Poland, helpline 606 950 000, uodo.gov.pl. You may complain at any time; contacting us first is not a condition, though it is usually the fastest way to solve a problem.
Data of Invitees
An Invitee books time with a Host and never needs a Kallenda account. The Invitee’s data therefore reaches us from the Invitee through the booking form and from the Host when the Host adds, reschedules or answers a Booking. We store and process it for the Host, who is its controller.
- The Scheduling Page shows the Host’s identity and the privacy information the Host provides, so an Invitee can see who is collecting their data before booking.
- The Booking Confirmation contains the Booking details, the Host’s cancellation terms and, for a Paid Booking, the pre-contract information and the withdrawal form where it applies.
- We send the Invitee only transactional messages about that Booking — confirmation, reminders, reschedule and cancellation notices — unless the Invitee separately agrees to something else.
- An Invitee may ask the Host to erase their data; the Host decides, and when the Host instructs erasure we apply it and keep only the Booking skeleton described in section 7.
- Invitees’ data is not used to build profiles across Hosts and is not shared between Hosts.
If you are an Invitee and want to know what a Host holds about you, the Host is the right addressee. We will help the Host answer, and if the Host cannot be reached we will do what we can within the limits of our processor role.
Security
We apply technical and organisational measures appropriate to the risk. These are the measures we operate; they are not a certification and they do not make the service risk-free.
- TLS for data in transit, on the public site, the dashboard, the API and the booking flow.
- Encryption at rest for the primary database, backups and object storage.
- Least-privilege staff access, with administrative actions recorded in the audit log.
- Application logs with personal identifiers redacted, so debugging does not create a second copy of personal data.
- EU data residency for the primary store, and the transfer safeguards in section 6 for everything else.
- Access reviews, dependency updates and a vulnerability-disclosure route at support@kallenda.app.
If a personal-data breach occurs, we notify the Host without undue delay and in any event within 24 hours of becoming aware of a breach affecting the Host’s data, with the information the Host needs to meet its own 72-hour duty. Where we are the controller, we notify UODO within 72 hours where the breach is likely to result in a risk to rights and freedoms, and tell the affected people without undue delay where the risk is high.
Automated decisions and profiling
We do not make decisions about you based solely on automated processing that produce legal or similarly significant effects. We do not use personal data to build advertising profiles, to score people or to set a price for an individual. The price of a Plan is the same for every customer in the same country and on the same Plan, as Article 12(1)(5a) of the Polish Consumer Rights Act requires.
Some features compute a result automatically — available slots, Busy Time subtraction, minimum-notice checks, duplicate-booking prevention and payment-hold expiry. Those are deterministic rules applied to the data the Host configured, not profiling, and a Host or an Invitee can always reach a person through support@kallenda.app to query an outcome. Fraud and abuse signals may lead us to restrict an account, but a person reviews that decision before it takes lasting effect.
Children
Kallenda is a business scheduling service and is not directed to children. A Host account may be held only by a person who is at least 18 years old and has capacity to contract.
We do not knowingly collect data from children. If you believe a child’s data has reached us — for example because an Invitee entered it in a Booking question — write to support@kallenda.app and we will investigate, delete the data where we are the controller, and inform the Host where the Host is. A Host who invites minors to book should consider whether their own notice and lawful basis cover that.
Changes to this policy and contact
This policy is version 1.0 and applies from 10 November 2026. We review it when the service, the providers or the law change, and we publish the new version on this page with its own version number and date.
Where a change materially affects how we process personal data, we announce it to Hosts by email and in the dashboard at least 30 days before it takes effect, unless a shorter period is required by law or by an urgent security need. Older versions are available from support@kallenda.app.
For security reports and other questions about the service, email support@kallenda.app.
Service operator
Undernapse Sp. z o.o.
UNDERNAPSE SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ
ul. Hoża 86 lok. 410, 00-682 Warsaw, Poland
- KRS
- 0001037160
- Register court
- Regional Court for the Capital City of Warsaw in Warsaw, 12th Commercial Division of the National Court Register
- NIP
- 7011145585
- REGON
- 525353982
- Share capital
- PLN 5,400.00
Contact