Sub-processors: Paddle Sync
Last updated: 11 November 2026
Kayabyte (Caner Kaya, Stasjonsveien 64, 0771 Oslo, Norway) uses the following sub-processors to provide Paddle Sync. We give 30 days’ notice on this page before adding a new sub-processor; customers on a paid plan can object by email and cancel if we cannot resolve the objection.
| Sub-processor | Purpose | Data | Location |
|---|---|---|---|
| Cloudflare, Inc. | Hosting of the app’s backend (Workers), its database (D1) and background jobs (Queues) | Account ID and name, installing user’s ID and email, app admins’ user IDs, encrypted tokens and Paddle API key, Paddle customers (ID, email, name), subscriptions, transactions, raw Paddle events for up to 14 days, notes waiting for the timeline, owners’ names and emails (cache) | Global network; database primary location in Europe |
| Stripe, Inc. (Stripe Payments Europe, Ltd. for customers in Europe) | Payment processing for the Growth and Scale plans (our own billing) | Billing name, email, address, tax ID and payment details entered at checkout, HubSpot account ID | EU and United States |
HubSpot, Inc. is not a sub-processor of Kayabyte; HubSpot hosts your account data, and the app accesses it through HubSpot’s APIs with your permission. Paddle is not a sub-processor either: it is the billing provider you chose, and the app reads from your Paddle account with the API key you give it.
Transfers outside the EEA rely on the EU Standard Contractual Clauses and the EU-U.S. Data Privacy Framework where the provider is certified.
Contact: support@kayabyte.dev. See also the data processing agreement and privacy and data.