This page lists the vendors Klirry uses. Only vendors marked Engaged are in production use today; a vendor marked Planned is added to the service only after the notice described below. Sub-processors process the Customer's data on Klirry's behalf (DPA Annex 3). Klirry's own tools (billing, newsletter, website analytics) are used by Klirry as controller for its own purposes; they are listed so that nothing is hidden, but they are not sub-processors of the Customer's data. No blanket "all data stays in the EU/EEA" statement can be made about the service: Stripe (a transfer to the United States) and Sentry (a US provider with an EU data location) are on the list. The platforms the Customer connects (Shopify, Meta, Google, TikTok) are not sub-processors; their role is stated under "Platforms" below.
Register
| Vendor | Role | Purpose | Region | Transfer outside the EU/EEA | Data categories | Safeguard | Status | Last verified |
|---|---|---|---|---|---|---|---|---|
| Hetzner Online GmbH | Sub-processor of the Customer's data | Cloud hosting: servers, database, storage volumes and encrypted backups | Germany (Falkenstein) | None: stays in the EU/EEA | All Order Data and Account Data | Hetzner's data processing agreement, accepted with the account | Engaged | 2026-09-16 |
| Scaleway SAS | Sub-processor of the Customer's data | Transactional email only: account, security, trial-reminder and notice mail (never marketing) | France (Paris, fr-par) | None: stays in the EU/EEA | Email addresses of the Customer's users and the content of the messages sent to them | Scaleway's data processing agreement, to be accepted when the account is created | Planned | not yet |
| Functional Software, Inc. (Sentry) | Sub-processor of the Customer's data | Error monitoring and crash reporting | EU data location (de.sentry.io); the provider is a US company | United States: possible access by the US provider; EU standard contractual clauses in Sentry's data processing agreement (the EU–US Data Privacy Framework is also available but an appeal against it is pending at the EU Court of Justice) | Scrubbed stack traces and tenant or user identifiers (UUIDs); no personal data by configuration (a beforeSend filter removes personal data, including Swedish personal identity numbers) | Sentry's data processing agreement including standard contractual clauses, to be accepted when the organisation is created; retention to be set to at most 30 days in the organisation | Planned | 2026-10-01 |
| Stripe | Klirry's own tool (Klirry is controller) | Subscription billing for customers who do not pay through Shopify: hosted checkout and payment collection. Klirry is the controller of billing data; Stripe is not a sub-processor of the Customer's Order Data | Stripe's data processing agreement states that personal data is transferred to Stripe, LLC in the United States under its data transfer addendum | United States: Stripe's data transfer addendum (standard contractual clauses); EU–US Data Privacy Framework where Stripe is certified | Billing contact name and email, company name, VAT number and plan; card details are entered on Stripe's hosted page and never reach Klirry | Stripe's data processing agreement and data transfer addendum, to be accepted before live mode is switched on (until then the account runs in test mode and no customer card data is processed) | Planned until live mode | not yet |
| Sendinblue SAS (Brevo) | Klirry's own tool (Klirry is controller) | Newsletter and other marketing email, sent only to people who opted in (double opt-in). Klirry is the controller; Brevo is not a sub-processor of the Customer's Order Data | France / EU | None: stays in the EU/EEA | Subscriber email address and consent timestamp | Brevo's data processing agreement, to be accepted when the account is created (flag newsletter OFF until then) | Planned | not yet |
| Umami (self-hosted) | Klirry's own tool (Klirry is controller) | Website analytics for klirry.com marketing pages, only after the visitor's consent (see the cookie section of the Privacy Policy). Runs on Klirry's own server; no third party receives the data | Germany (Falkenstein), on Klirry's own Hetzner server | None: stays in the EU/EEA | Page path, referrer domain, country, browser family and screen class of consenting visitors; never from signed-in pages | Own service on Klirry's own server: no recipient. | Planned | not yet |
Connected platforms (data sources you choose)
The platforms below are where the Customer's data comes from. Each is an independent controller of its own data; Klirry reads from it with the Customer's authorisation and is not its processor, nor is the platform Klirry's sub-processor. The roles in full are in section 4b of the Privacy Policy.
| Platform | Role | What Klirry reads or sends | Access | How you revoke access |
|---|---|---|---|---|
| Shopify | Source platform and payment channel. Shopify Inc. (Canada) and Shopify Commerce Singapore Pte. Ltd. are Klirry's counterparties under the Partner Program Agreement; the merchant contracts with Shopify International Limited (Ireland). Klirry reads orders and products with the scopes read_orders and read_products; Shopify is an independent controller of its own data and not a sub-processor of Klirry. | Orders and products (scopes read_orders and read_products). No customer name, email, address or phone is stored | Read-only | Uninstall the app in your Shopify admin, or disconnect it in Klirry under Settings, Connections (Klirry stops reading at once) |
| Meta | Source platform for ad spend and performance (permission ads_read). Meta is an independent controller; Klirry is not Meta's processor and Meta is not Klirry's sub-processor. | Ad spend and performance per ad account (permission ads_read) | Read-only | Remove Klirry from the connected apps in your Meta business settings, or disconnect it in Klirry under Settings, Connections (Klirry stops reading at once) |
| Source platform for Google Ads spend (planned) and Google Analytics 4 as a directional signal (planned, never in the profit figure). Google is an independent controller. | Google Ads spend and Google Analytics 4 sessions (both planned; never part of the profit figure) | Read-only | Remove Klirry from the third-party access of your Google account, or disconnect it in Klirry under Settings, Connections (Klirry stops reading at once) | |
| TikTok | Planned source platform for ad spend. Not connected today. TikTok is an independent controller. | Ad spend (planned; not connected today) | Read-only | Remove Klirry in your TikTok business settings, or disconnect it in Klirry under Settings, Connections (Klirry stops reading at once) |
| WooCommerce | Prepared, not offered to customers yet. Source platform: your own WooCommerce store, which you host. Klirry calls the store's REST API at the address you enter. The store owner is the controller; Klirry is not the store's processor and the store is not Klirry's sub-processor. | Orders and their line items from the store's REST API. No customer name, email, address or phone is stored | Read-only (a read key you create) | Delete the REST API key in WooCommerce (Settings, Advanced, REST API), or disconnect it in Klirry under Settings, Connections (Klirry stops reading at once) |
| PrestaShop | Prepared, not offered to customers yet. Source platform: your own PrestaShop shop, which you host. Klirry calls the shop's Webservice at the address you enter. The shop owner is the controller; Klirry is not the shop's processor. | Orders and their lines from the shop's Webservice. No customer name, email, address or phone is stored | Read-only (a Webservice key you create) | Delete the key under Advanced Parameters, Webservice in PrestaShop, or disconnect it in Klirry under Settings, Connections (Klirry stops reading at once) |
| Shopware 6 | Prepared, not offered to customers yet. Source platform: your own Shopware 6 shop. Klirry calls the shop's Admin API at the address you enter. The shop owner is the controller; Klirry is not the shop's processor. | Orders and their lines through a search request (a read; no change is ever sent). No customer name, email, address or phone is stored | Read-only (an integration you create) | Delete the integration under Settings, System, Integrations in Shopware, or disconnect it in Klirry under Settings, Connections (Klirry stops reading at once) |
| BigCommerce | Prepared, not offered to customers yet. Source platform. BigCommerce is an independent controller of its own data; Klirry is not its processor and BigCommerce is not Klirry's sub-processor. | Orders (v2 REST API). No customer name, email, address or phone is stored | Read-only (a store-level API account with Orders read-only scope) | Delete the API account in your BigCommerce store, or disconnect it in Klirry under Settings, Connections (Klirry stops reading at once) |
| Wix | Prepared, not offered to customers yet. Source platform. Wix is an independent controller of its own data; Klirry is not its processor and Wix is not Klirry's sub-processor. | Orders (eCommerce Orders search, a read). No customer name, email, address or phone is stored | Read-only (an API key with the Read eCommerce Orders permission) | Delete the API key in your Wix account, or disconnect it in Klirry under Settings, Connections (Klirry stops reading at once) |
| Quickbutik | Prepared, not offered to customers yet. Source platform. Quickbutik is an independent controller of its own data; Klirry is not its processor and Quickbutik is not Klirry's sub-processor. | Orders through the store API (JSON GET only). No customer name, email, address or phone is stored | Read-only (the store API key you create) | Delete or regenerate the API key in your Quickbutik account, or disconnect it in Klirry under Settings, Connections (Klirry stops reading at once) |
| PayPal | Prepared, not offered to customers yet. Source of payment fees. PayPal is an independent controller of its own data; Klirry is not its processor and PayPal is not Klirry's sub-processor. | Transactions and their fees from the Transaction Search report. No payer name or email is stored | Read-only (a REST app you create with Transaction Search) | Delete the REST app in the PayPal developer dashboard, or disconnect it in Klirry under Settings, Connections (Klirry stops reading at once) |
| Stripe (your own Stripe account) | Prepared, not offered to customers yet. Source of payment fees from the Stripe account YOU hold with Stripe. This is a different relationship from Klirry's own use of Stripe to bill its customers (see the vendor list): here Stripe is an independent controller of your account data and Klirry only reads it. | Charges and balance transactions, to learn the real fees. No cardholder or customer detail is stored | Read-only (a restricted key with Charges: Read and Balance Transactions: Read) | Delete the restricted key in your Stripe dashboard (Developers, API keys), or disconnect it in Klirry under Settings, Connections (Klirry stops reading at once) |
| Slack (your own workspace) | A destination YOU choose: if you paste an incoming-webhook URL of your own Slack workspace, Klirry posts alerts there in addition to email. Klirry has no Slack workspace of its own that receives customer data. Slack is an independent controller of the messages in your workspace; it is not a sub-processor of Klirry. | Nothing is read. Klirry sends the decision sentence of an alert email and a link to the decisions page, to the webhook you set up | Send only, to your own webhook | Delete the incoming webhook in Slack, or remove the Slack address in Klirry under Settings |
Changes and notice
A change to this list after it is in force (a vendor added or replaced) is announced to customers by email at least 30 days before it takes effect (DPA 3.3), with the right to object (DPA 3.4). Anyone can also subscribe to these notices with their email address on the public page /legal/subprocessors (a double opt-in; the address is used for sub-processor notices only and is kept apart from the marketing list).
Notes
- Hetzner's row is compute and database storage. Encrypted pre-release dumps stay on the production server; a nightly off-site copy is not yet in operation, so no backup data is held by another sub-processor today.
- Connection credentials and two-factor secrets are encrypted at rest at the application level (AES-256-GCM), with the key held outside the database. Full-disk encryption of the production volume is not yet in place.
- No AI/ML sub-processors process customer order or spend data.
- Not yet chosen: external uptime monitoring. It is added to the register, with notice, if it would process personal data.
- Alerts to Klirry's operators go by email through the transactional email provider; no chat service receives any data.
- Source hosting (GitHub), the container build on the Hetzner host and the domain registrar process no customer data and are not sub-processors.
Changelog
A change to this list is a sub-processor change and is announced to customers under the same 30-day mechanism as a material terms change. A row with an effective date carries the date it was announced, at least 30 days earlier.
| Version | Date | Announced | Effective | Change |
|---|---|---|---|---|
| 1.0 | 2026-10-10 | first publication | 2026-10-10 | First published version of the list. |
| 1.1 | 2026-10-11 | not required (minor change) | 2026-10-11 | The list of platforms you connect is extended and now says that Slack is a destination you choose; the status note "until live mode" is added to Stripe. No sub-processor changes. Minor change: no customer is in live mode yet, no sub-processor is added, and periods only get shorter or are new classes, so there is no 30-day notice. |