Subprocessors

Last reviewed:

We rely on a small number of third parties to deliver parts of our service — hosting, payment, email, security and delivery. This page lists each of them, what they do for us, the categories of data they receive, where they are, and the legal mechanism covering the relationship. It forms part of our Privacy Policy.

Most of these companies act as our processors: they handle personal data only on our instructions and may not use it for their own purposes. A few act as independent controllers — they decide for themselves how they handle the data in order to meet their own legal and operational obligations — and those are listed separately below, because your rights against them are exercised under their own privacy notices rather than ours.

We require every processor to be bound by a written data protection agreement, to apply appropriate security measures, to restrict access to staff who need it, and not to engage a sub-processor without equivalent protections.

Two different things are recorded against each entry below, and they do different jobs. A data processing agreement governs what a processor may do with personal data on our behalf. A transfer mechanism — Standard Contractual Clauses, or the provider’s certification under the EU-US Data Privacy Framework — is what allows the data to leave the European Economic Area or the United Kingdom in the first place. Most providers include their transfer mechanism inside their data processing agreement rather than as a separate document.

Some of the providers below are certified under the EU-US Data Privacy Framework. Where that applies, it is an additional route that can make a transfer lawful; it does not replace the data processing agreement, which governs what the provider may do with the data. We therefore record both, and we record the mechanism each provider’s own agreement actually relies on rather than the certification alone.

Current subprocessors

Amazon Web Services (AWS)

DPA + SCCs
Purpose
Cloud hosting for the entire site — compute, database, object storage, queues, logs, CDN.
Data categories
  • Account credentials
  • Order data
  • Shipping addresses
  • Marketing-consent metadata
  • Audit-trail metadata
  • All other server-side personal data
Jurisdiction
United States (us-east-1)
Legal mechanism
AWS Data Processing Addendum, which incorporates the EU Standard Contractual Clauses by reference (clause 16). The controller-to-processor clauses apply to our transfers (clause 12.2.1). Data is held in the region we select, currently us-east-1.

Includes Amazon CloudFront (CDN) — covered by the parent AWS DPA; not a separate vendor.

View DPA →

Stripe

DPA + SCCs
Purpose
Card payment processing — tokenizes card details so we never store PAN / CVV.
Data categories
  • Tokenized payment-method reference
  • Billing address
  • Order total
  • Customer email (for receipts)
Jurisdiction
United States (global processing footprint)
Legal mechanism
DPA + SCCs on file. Our Stripe account is held in North America, so we contract with Stripe, LLC in the United States. Stripe acts as our processor when handling a payment on our instruction, and as a controller in its own right for fraud monitoring, anti-money-laundering and know-your-customer checks, regulatory compliance and improving its own services (DPA section 2). The transfer mechanism sits in the separate Data Transfers Addendum, which provides for the Standard Contractual Clauses, the UK International Data Transfer Addendum, or the EU-US Data Privacy Framework as applicable.

Payment methods within Stripe. Where you pay by card, including through a device wallet such as Apple Pay or Google Pay, your card is tokenized on your own device and the token reaches Stripe. We do not exchange your personal data with the device wallet provider and we have no account relationship with them, so they are not listed separately. Where you pay using an account-based wallet — one where you hold an account with the provider and it passes us your details — that provider decides for itself how it handles your data and is listed under independent controllers below. For completeness, the following are enabled and do not appear separately here: Apple Pay and Google Pay tokenize your card on your own device, so no personal data passes between us and them; Cartes Bancaires, Bancontact and EPS are card and bank payment schemes, in the same category as Visa or Mastercard; and Link is Stripe's own saved-payment feature, covered by this entry.

View DPA →

MailerLite

DPA + SCCs
Purpose
Marketing email delivery and double-opt-in confirmation pipeline.
Data categories
  • Email address
  • Marketing-consent metadata (IP, user agent, source, timestamp)
Jurisdiction
United States (contracting entity), with processing in the European Union
Legal mechanism
MailerLite data processing agreement, which contains the Standard Contractual Clauses (controller to processor) and applies the UK International Data Transfer Addendum to UK transfers. The clauses are governed by Lithuanian law.

We contract with MailerLite, Inc. in San Francisco, which is named as the data importer under the Standard Contractual Clauses in the DPA, so those clauses are the operative transfer mechanism. MailerLite's own processing takes place in the European Union, using Google Cloud data centres in Germany and the Netherlands, and its sub-processors are Google Cloud EMEA Ltd (Ireland) and Vercom S.A. (Poland).

View DPA →

Termly

DPA + SCCs
Purpose
Cookie consent management platform — presenting the consent banner, recording your choices, and maintaining the consent log.
Data categories
  • Cookie-consent preferences
  • IP address (for consent log)
Jurisdiction
United States
Legal mechanism
Data processing agreement, which contains the Standard Contractual Clauses.

View DPA →

Google

DPA + SCCs
Purpose
Google Sign-In (federated login), Google Analytics 4 (site analytics), and address autocomplete on the checkout shipping form (Google Maps Platform). These run under separate sets of terms, and Google's role differs between them.
Data categories
  • Email, name, and Google account identifier (Sign-In only)
  • Online identifiers and cookie IDs, IP address, pages viewed, events and approximate location derived from IP (Google Analytics only)
  • Partial address text typed into the checkout shipping form (address autocomplete only)
Jurisdiction
United States (global processing footprint)
Legal mechanism
Each service runs under its own agreement, so there is no single entry — see the breakdown below. Terms: Google Analytics Measurement Controller-Processor Data Protection Terms; Google Terms of Service (Sign-In); Google Maps Platform Terms of Service.

Google Analytics 4 — processor

Measuring how the site is used so that we can improve it. Loaded only after you consent to analytics cookies. Advertising features and Google signals are switched off, so the data is not used for advertising. Terms: Google Analytics Measurement Controller-Processor Data Protection Terms, which contain the Standard Contractual Clauses. These are accepted in the Analytics admin console and are separate from the Cloud addendum.

Google Sign-In — independent controller

Google operates its own account infrastructure and decides for itself how it handles your Google account; we receive only your email address, name and an account identifier when you choose that sign-in method.

Google Maps Platform (address autocomplete) — independent controller

Google supplies Maps Platform under separate terms and acts as a controller for the data it receives, so its own privacy notice governs that handling. This feature is not essential and is loaded only after you consent.

View DPA →

Cloudflare

DPA + Data Privacy Framework
Purpose
Bot protection (Cloudflare Turnstile) on public forms — email signup, marketing opt-in, the privacy-choices opt-out, and the order tracking and checkout endpoints. Cloudflare describes Turnstile as behaviorally non-profiling: it sets one strictly necessary security cookie (cf.turnstile.u), and the IP transferred to Cloudflare on each challenge is used only for that challenge and is not folded into any advertising or cross-site identity graph.
Data categories
  • IP address (every protected form submission, transmitted to challenges.cloudflare.com for the verification round-trip)
Jurisdiction
United States (global edge network)
Legal mechanism
Cloudflare Data Processing Addendum (version 6.4). Transfers rely on Cloudflare's certification under the EU-US Data Privacy Framework, with the EU Standard Contractual Clauses and the UK International Data Transfer Addendum applying automatically if that certification lapses (clauses 6.2 and 6.4). Cloudflare is also certified under the Global Cross-Border Privacy Rules and Global Privacy Recognition for Processors systems.

No tracking cookies, no behavioral profiling, no cross-site fingerprinting. Cloudflare's use of Turnstile data is contractually limited to operating the bot-detection service.

View DPA →

Other recipients who act as independent controllers

These organizations receive personal data from us but decide for themselves how they handle it, under their own privacy notices and their own legal obligations. They are not our processors, and we cannot direct what they do with the data once it reaches them.

Stripe is listed above as a processor, which is how it acts when handling a payment on our instruction. It also acts as a controller in its own right for fraud monitoring, anti-money-laundering and know-your-customer checks, regulatory reporting and improving its own services. Stripe’s privacy policy governs that activity.

PayPal

Independent controller
Purpose
Alternative checkout payment method (PayPal Smart Buttons) — payer authentication and authorization.
Data categories
  • Payer email
  • Payer name
  • Billing address
  • Order total
Jurisdiction
United States (global processing footprint)
Legal mechanism
PayPal holds its own account relationship with you as the wallet account holder, so it acts as an independent controller rather than as our processor. Its own user agreement and privacy statement govern that relationship. No data processing agreement applies, because we do not instruct PayPal on how to handle your data.

PayPal decides for itself how it uses payment data to meet its own legal and regulatory obligations, including fraud prevention, anti-money-laundering checks and financial reporting.

View terms →View privacy notice →

Venmo

Independent controller
Purpose
Alternative checkout payment method offered within PayPal's wallet services.
Data categories
  • Payer name
  • Payer email or Venmo handle
  • Order total
Jurisdiction
United States
Legal mechanism
As with PayPal, Venmo holds its own account relationship with you and acts as an independent controller. Its own user agreement and privacy policy govern that relationship.

View terms →View privacy notice →

Apple

Independent controller
Purpose
Sign in with Apple — an optional federated login method.
Data categories
  • Name and email address, or a private relay address where you choose to hide your email
  • An Apple user identifier
Jurisdiction
United States (global processing footprint)
Legal mechanism
Apple operates its own account infrastructure and decides for itself how it handles your Apple Account, so it acts as an independent controller rather than as our processor. Its own privacy policy governs that handling.

If you use Apple's Hide My Email option, we receive a relay address rather than your real email address, and Apple forwards our messages to you. We treat the relay address the same way we treat any other email address you give us.

Amazon Pay

Independent controller
Purpose
Alternative checkout payment method offered through Stripe, where you pay using your Amazon account.
Data categories
  • Payer name
  • Payer email
  • Billing and shipping address
  • Order total
Jurisdiction
United States (global processing footprint)
Legal mechanism
Amazon holds its own account relationship with you and decides for itself how it handles your data, so it acts as an independent controller rather than as our processor. Its own privacy notice governs that relationship.

Klarna

Independent controller
Purpose
Pay-over-time credit offered at checkout through Stripe. Klarna, not us, decides whether to offer you credit.
Data categories
  • Name
  • Contact details
  • Billing and shipping address
  • Order total and contents
  • Any further information Klarna collects from you directly to assess your application
Jurisdiction
Sweden, with a United States entity for US customers
Legal mechanism
Klarna is an independent controller. You enter a separate credit agreement with it, it runs its own checks, and its own privacy notice governs the information it holds about you.

Affirm

Independent controller
Purpose
Pay-over-time credit offered at checkout through Stripe, for customers in the United States and Canada. Affirm, not us, decides whether to offer you credit.
Data categories
  • Name
  • Contact details
  • Billing and shipping address
  • Order total and contents
  • Any further information Affirm collects from you directly to assess your application
Jurisdiction
United States and Canada
Legal mechanism
Affirm is an independent controller, on the same basis as Klarna.

UPS

Independent controller
Purpose
Shipment carriage, tracking-number issuance, and delivery polling.
Data categories
  • Shipping address
  • Recipient name
  • Tracking number
Jurisdiction
United States (global delivery network)
Legal mechanism
Carrier customer agreement. UPS receives your name, delivery address and contact details in order to perform carriage, and determines its own retention, tracking and proof-of-delivery practices in order to meet its own obligations as a carrier. It therefore acts as an independent controller rather than as our processor, and its own privacy notice governs its handling of your data.

Other recipients

Sipact EU

Authorized representative
Purpose
Our authorized representative in the European Union for product safety purposes under the General Product Safety Regulation (EU) 2023/988. Sipact EU holds our product safety documentation, receives consumer safety complaints and enquiries from EU market surveillance authorities, and coordinates with us on any recall or corrective action.
Data categories
  • Only what a safety complaint or a recall requires — typically your name, contact details, and the details of the product and the concern you raised. We do not routinely send Sipact EU customer or order data, and we keep what we do send to the minimum the matter requires.
Jurisdiction
France
Legal mechanism
Authorized Representative Agreement under Regulation (EU) 2019/1020 and the General Product Safety Regulation. Sipact EU is established in the European Union, so no transfer mechanism is needed for personal data of EU customers.

Contact: compliance@sipacteu.com, 16B Avenue de la Marne, 59290 Wasquehal, France.

Changes to this list

When we add or remove a third party, we update this page in the same change that connects or disconnects the integration, and we record it in the log below. Material changes — for example adding an analytics or advertising vendor — are also reflected in our Privacy Policy and, where consent is required, are not switched on until you have given it.

Because this page is updated more often than the Privacy Policy itself, changes recorded here do not by themselves trigger the notice we give for material changes to the Privacy Policy. Where a change to this list is material to you, we will give that notice as well.

Change log

  • 2026-09-29 — Cloudflare entry corrected: Turnstile sets one strictly necessary security cookie (cf.turnstile.u); it was previously described as cookieless.
  • 2026-08-19 — Legal review. Amazon Pay added as an independent controller, alongside PayPal and Venmo, because you hold an account with it and it passes us your identity and address. Klarna and Affirm added as independent controllers: they are lenders rather than wallets, you enter a separate credit agreement with them, and they collect information from you directly that we never see. The Stripe entry now explains why the other payment methods available through Stripe need no entry of their own.
  • 2026-08-11 — Legal review. Entries reconciled against the signed agreements. UPS and PayPal reclassified as independent controllers and moved to a separate section, together with Apple for Sign in with Apple. Google Analytics 4 added as a processor, and Google Sign-In and Google Maps Platform identified as operating under their own separate terms. Transfer mechanisms restated to match what each agreement relies on. MailerLite jurisdiction corrected to reflect the US contracting entity. Termly purpose updated following consolidation of the cookie policy into Section 11 of the Privacy Policy. Venmo added as an independent controller alongside PayPal, and PayPal’s entry corrected to reflect its wallet terms. Sipact EU added as our authorized representative in the European Union for product safety.
  • 2026-05-31 — Google reCAPTCHA removed; Cloudflare Turnstile added for bot protection on public forms.
  • 2026-05-28 — Page created as part of the multi-jurisdiction privacy rewrite.

For the full description of how we collect and use personal data, and for your jurisdiction-specific rights, see our Privacy Policy. Section 11 of that policy explains the cookies and similar technologies we use. To opt out of marketing-related disclosure, visit Your Privacy Choices.