To run SmartKDP we rely on a small number of service providers. Under the GDPR these are our "subprocessors", and we think you are entitled to know who they are whether or not the law requires it of us.
We keep this list deliberately short. Every addition is a company you have to trust because you trust us.
Current subprocessors
| Provider | What it does | Location | Status |
|---|---|---|---|
| Google Cloud Platform | Application hosting, databases, file storage, and caching. The primary place your account and project data lives. | United States | In use |
| Firebase Authentication (Google) | Verifies your identity when you sign in with email or Google. Handles the password check itself, so we never see or store your password. Google's One Tap sign-in card is part of the same relationship: for signed-out visitors it loads a script from accounts.google.com — disclosing the IP address of that request — and sets a g_state cookie so it does not re-offer itself on every page. Since 13 September 2026 neither happens until the cookie banner has been answered. | United States | In use |
| Lemon Squeezy | Merchant of record for every purchase. Lemon Squeezy sells the product to you as an authorised reseller, takes the payment (card or PayPal), runs subscription billing and fraud prevention, and calculates, charges and remits the sales tax or VAT added to our prices at checkout. Card details are entered directly into Lemon Squeezy's payment fields and never reach our servers; receipts are issued by Lemon Squeezy and linked from your billing page. | United States | In use |
| Cloudflare | Hosts and serves the website itself, and delivers the product demo videos. As the network in front of everything, it processes the IP address and request details of every visit for routing, caching, and protection against attack. The video player is loaded only if you press play. | Global edge network, with the operating entity in the United States | In use |
| Google Analytics (Google Ireland Limited) | Website and product analytics: which pages are visited, which features are reached, and where visitors drop out. Engaged only after you accept analytics cookies — Google Consent Mode denies analytics storage until then. No Google Signals, no ad personalisation, and no name, email address, or account identifier is ever sent to Analytics. Advertising measurement is a separate purpose with its own consent; see the Google Ads entry below. | European Union, with processing in the United States under the EU–US Data Privacy Framework | In use |
| Google Ads (Google Ireland Limited) | Advertising measurement only: telling Google that a click on one of our ads ended in a purchase, so we can judge whether an ad is worth paying for. Engaged only after you accept advertising cookies — Google Consent Mode denies advertising storage until then, and declining means nothing is sent at all, not even an anonymised signal. It receives the fact of a purchase, its value and currency, the click identifier from the ad link, and a one-way hash of the order's email address computed in your browser. Ad personalisation and Google Signals are denied in code permanently, so this builds no audience and drives no remarketing. | European Union, with processing in the United States under the EU–US Data Privacy Framework | In use |
| Amazon Web Services (Amazon SES) | Delivers our outgoing email. SES is the relay: it transmits each message and processes the recipient address and delivery result (delivered, bounced, marked as spam) so we stop mailing addresses that reject us. It does not hold our subscriber list. | United States | In use |
| Sentry (Functional Software, Inc.) | Collects reports when something goes wrong — the error, where in our code it happened, and the address of the page or API route that failed. It is how we find out a purchase or an export broke for you without waiting for you to tell us. It receives no request bodies, no cookies, no headers, and no query strings, and we do not send it your name or email address. | United States | Not yet in use |
| Anthropic | Powers AI-assisted writing features. Not currently in use — listed in advance so its addition is never a surprise. | United States | Not yet in use |
Payments moved to Lemon Squeezy, 18 September 2026
Stripe has been removed from this list and Lemon Squeezy added in its place. Stripe closed our account on 15 September 2026, and since 18 September every purchase has been made through Lemon Squeezy, LLC as our merchant of record.
This is a bigger change than swapping one vendor for another, and the honest description of it is not "we changed payment processor":
- Lemon Squeezy is the seller, not our agent. It buys from us and resells to you. For your purchase it is a controller in its own right, so its privacy policy applies to the payment data directly, and you can take a data-subject request to it as well as to us.
- Your statement line changed. Charges now read
LEMSQZY* SMARTKDP. - Tax is now added at checkout rather than included in the price, and Lemon Squeezy — not us — determines, charges and remits it.
- Stripe still holds records of orders placed before 18 September 2026 under its own retention policy. It no longer receives anything new from us.
Error reporting, added 13 September 2026
Sentry is new to this list and is marked not yet in use, because it is: the integration is built and switched off, and nothing has been sent to it. We are listing it now rather than on the day it is switched on, which is what the promise further down this page asks for.
What it is for: when a purchase, an export or a page fails, we would rather find out from the failure itself than from you. Sentry receives the error, the place in our code it happened, and the address of the page or API route involved.
What it does not receive, and this is enforced in code rather than by care:
- No query strings. The address is trimmed at the
?before an error report leaves our servers, so nothing carried after it — which can include personal details — reaches the error store. The trimming has a test that fails if anyone removes it. - No request bodies, cookies or headers. Not trimmed afterwards — never collected.
- No name, email address or account id, and no session recording or screen capture of any kind.
The limit worth stating plainly: an error report contains whatever our own code put into the error message. We do not put customer data there, and Sentry removes common sensitive patterns on its side, but that is a practice backed by a second net rather than a guarantee the way the three bullets above are.
Where processing happens
Most processing takes place in the United States.
Where personal data of individuals in the EEA or the UK is transferred to the United States, we rely on the transfer safeguards offered by the provider — typically the European Commission's Standard Contractual Clauses, together with the provider's own certifications.
What is not on this list
- We do not use data brokers, and we do not sell personal data. One advertising network is now on the list above — Google Ads, added 13 September 2026 — and it is there for a single purpose: telling Google that a click on one of our ads ended in a purchase, so we can tell which ads are worth paying for. It receives nothing unless you accept advertising cookies. Until that date this bullet said we used no advertising network at all, which was true when it was written; it is narrower now, and saying so is the point of a versioned page.
- No third party builds an advertising profile of you. Ad personalisation and Google Signals are denied in code on every page, for everyone, whatever they answered — so nothing here feeds remarketing or audience building.
- Our analytics provider receives nothing that identifies you personally — no name, no email address, no account id. It receives a cookie identifier only if you accept analytics cookies, and nothing at all if you decline. Google Ads is the exception and is described separately: if you accept advertising, it receives a one-way hash of your order's email address.
- Our newsletter list is not hosted by a marketing company. The subscriber list is held on our own infrastructure, with the hosting provider listed above, so no third-party marketing platform holds it. Amazon SES appears in the list above only because it is the relay that carries the messages — it transmits them, it does not hold the list.
- Lemon Squeezy is more than a subprocessor — it is the seller. As our merchant of record it resells the product to you, which makes it a data controller in its own right for your purchase, not only a processor acting on our instructions. Card numbers are transmitted directly from your browser to Lemon Squeezy and never reach our servers. Lemon Squeezy also determines the sales tax or VAT added to your total at checkout, and charges and remits it — that is its responsibility, not ours.
Changes to this list
If we add a subprocessor that will process customer personal data, we will update this page before it goes live. Customers on business or team plans who want advance notice of changes can request it at support@smartkdp.com, and we will email you when this page changes.
If you object to a new subprocessor, tell us — we will discuss it, and if we cannot resolve it you may cancel and receive a pro-rata refund of any prepaid period.
Questions
Email support@smartkdp.com. If you need a Data Processing Agreement for your own compliance obligations, ask and we will arrange one.