In brief
- This page lists every provider that processes personal data for us, whether as our processor or as a subprocessor of the Host.
- For Booking data the Host is the controller and we are the processor, so our providers are the Host’s subprocessors.
- We give at least 30 days’ notice before adding or replacing a subprocessor, and the Host may object.
- Most data stays in the EEA; transfers outside it rely on the SCCs, an adequacy decision or the EU–US Data Privacy Framework.
What this list covers
Undernapse Sp. z o.o., the operator of Kallenda, uses the providers below to run the service. They process personal data in two capacities, and this page says which is which: as our processors for account, organisation, billing, support, security and telemetry data, where we are the controller; and as our subprocessors for Booking and Invitee data, where the Host is the controller and we are the processor.
Booking data belongs to the Host. The data processing agreement (DPA) between us and the Host incorporates this list by reference, sets out the instructions and the security measures, and is available from support@kallenda.app. It is referenced from the Terms of service.
Subprocessor list
The table is complete as at 10 November 2026. It names each provider, the service, the categories of personal data, the region where data is stored or primarily processed, and the basis on which data may leave the European Economic Area (EEA).
| Provider | Service | Personal data | Location | Transfer basis |
|---|---|---|---|---|
| Fly.io | Application hosting and Managed Postgres | Account, organisation and Booking data | EU (Frankfurt) | SCCs |
| Cloudflare | DNS, CDN and R2 backup storage | Backups and request metadata | EU (R2 EU jurisdiction) | SCCs; DPF where certified |
| Upstash | Redis cache and rate limiting | Session and cache metadata | EU | SCCs |
| Auth0 | Identity and authentication | Account identifiers and login metadata | EU tenant | SCCs |
| Stripe | Payments, Billing, Tax and Connect | Subscription and payment data | EEA (Ireland) | Within the EEA; SCCs for group processing |
| Amazon SES | Transactional email delivery | Recipient addresses and delivery metadata | EU region | Within the EEA; DPF where certified |
| Expo | Push notifications for the host apps | Device push tokens | US | SCCs |
| Calendar API sync | Calendar identifiers and busy times | EEA and US | SCCs; DPF where certified | |
| Microsoft | Outlook and Microsoft Graph calendar sync | Calendar identifiers and busy times | EEA and US | SCCs; DPF where certified |
| Grafana Cloud | Metrics and operational dashboards | Telemetry with redacted identifiers | EU | SCCs |
| Sentry | Error monitoring | Error events with redacted identifiers | EU | SCCs |
| Better Stack | Uptime monitoring and status page | Uptime checks and alert metadata | EU | Within the EEA |
| Fakturownia | Invoices and KSeF submission | Billing profile and invoice data | Poland | Within the EEA |
| Fiscal-receipt provider (to be appointed) | Electronic fiscal receipts for consumer subscriptions | Receipt data | Poland | Within the EEA |
The fiscal-receipt provider is named as a category because it is not yet contracted; it will be engaged and named before consumer paid plans open. Providers that never receive personal data, and tools used only by staff, are not listed.
Where a provider is certified under the EU–US Data Privacy Framework, we rely on it for the transfer to the United States and on the Standard Contractual Clauses for any transfer the certification does not cover. Section 6 of the Privacy policy explains what that means for a data subject.
Changes and objections
We may add or replace a subprocessor when the service needs it. Except where a change is required by law or by an urgent security fix, we give the Host at least 30 days’ notice before a new or replacement subprocessor starts processing Booking data, by email to the Host’s administrator and by updating this page.
- The Host may object on reasonable data-protection grounds by writing to support@kallenda.app before the change takes effect.
- We discuss the objection in good faith and, where it is justified, propose a way to avoid the change or a safeguard that addresses it.
- If a sustained objection cannot be resolved, the Host may terminate the affected part of the service and we refund the unused prepaid period. Where the processing cannot be separated from the service, either party may terminate the DPA.
Contracts, security and audits
Every provider is bound by a written agreement that meets Article 28(3) GDPR: processing only on documented instructions, confidentiality, appropriate technical and organisational measures, assistance with data-subject requests and breach notification, deletion or return at the end, and the flow-down obligations in section 5.
- Security: encryption in transit and at rest, least-privilege access, audit logging of privileged actions and limited staff access.
- Transfers: the SCCs, an adequacy decision or the EU–US Data Privacy Framework where the provider is certified, with a transfer impact assessment on file.
- Audits: we review providers before engagement and at least annually, make their audit reports available to a Host on request under confidentiality, and answer reasonable security questionnaires.
- Breach notification: a provider must notify us without undue delay, and we notify the Host within 24 hours of becoming aware of a breach affecting the Host’s data.
We remain responsible to the Host for our subprocessors’ performance of their data-protection obligations, as Article 28(4) GDPR requires. Engaging a subprocessor does not transfer that responsibility.
Further subprocessors
A provider may engage its own subcontractors only if the same data-protection obligations flow down to them: confidentiality, security, transfer safeguards and a prohibition on processing for their own purposes. We do not list every downstream subcontractor, because the list would be stale on publication; instead, each provider must disclose its subprocessors on request, and we obtain that disclosure when we assess the provider and when a Host asks about one. Write to support@kallenda.app for the chain behind a particular provider.
Contact
Email support@kallenda.app with questions about this list, requests for the DPA or an audit report, objections to a change, security reports, support requests, or complaints. We answer data-subject requests within the period set by Article 12(3) GDPR.
The operator 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. The full imprint is in section 14 of the Terms of service.
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