Sub-processors
Every third party that processes personal data on our behalf, with what they do and where.
What is a sub-processor?
A sub-processor is a third party that processes personal data on our behalf and under our instructions. Under GDPR Article 28 we have to keep a current list of them, make it available to you, and tell you before we add or change any.
Current sub-processors
The table below lists every third party we use as of the "Last updated" date at the bottom of this page. We will give you at least 30 days' notice by email before we add a new sub-processor that handles personal data.
| Sub-processor | Purpose | Data shared | Region | DPA |
|---|---|---|---|---|
Supabase Infrastructure High-volume PII | Database, authentication, object storage. | All platform data: user accounts, course progress, ICI responses, AI reports, file storage. | United States (project region to be confirmed at signup). | Standard DPA available. Cover order on file. |
OpenAI AI / ML Medium | Optional fallback LLM provider. Used only if the operator switches AI_PROVIDER=openai. | Same prompt payload as the default LLM provider, sent to api.openai.com. | United States by default. EU residency available on enterprise tier. | DPA available. Default API data handling policy is no-training-on-customer-data for paid tiers. |
Whop Payments High-volume PII | Primary payment processor for paid Mind Architecture courses (Emotional Intelligence at Work, Future-Ready Leadership, Human Renaissance). Handles hosted checkout, payment intents, webhooks, and tax/sales compliance. | Buyer name, email, billing address, payment method token, transaction metadata, course-level metadata (course_id, learner_email, external_order_id). Card data is collected and stored entirely by Whop — we never see it. | United States by default (Whop Inc., Delaware). International card processing via Whop's acquiring partners. | Whop standard terms apply; DPA available on request via privacy@whop.com. |
Stripe Payments High-volume PII | Historical payment processor for paid courses. Currently deactivated — no live checkout traffic — but kept in this register in case of dormant data and historical transaction records. | Billing name, email, address, card details (tokenised, not stored by us), transaction metadata for past transactions only. | United States by default. EU and other regional entities available. | Stripe DPA countersigned on standard terms. |
Paddle Payments High-volume PII | Historical merchant-of-record alternative for paid courses. Currently deactivated — no live checkout traffic — but kept in this register for dormant data and historical transaction records. | Billing name, email, address, transaction metadata for past transactions only. Card data was handled entirely by Paddle. | United Kingdom (Paddle.com Markets Limited) was the controller for EU/UK transactions. | DPA available under standard MoR terms. |
Google LLC (Google Analytics 4) Analytics Low | Web analytics for the public marketing and course catalogue pages — how visitors arrive, what they read, and whether they reach a checkout or start an enquiry. The tag is not loaded at all until the visitor accepts analytics cookies, and pages behind sign-in are never measured. | Page URL and title, approximate location derived from IP address, browser and device type, referrer and campaign parameters, and a _ga cookie used to recognise a returning visitor. No advertising identifiers, no profile data, no content of forms, and nothing from the learner app. | Google Ireland Limited for UK / EEA visitors; Google LLC (United States) elsewhere. | Google Ads Data Processing Terms and the Google Analytics terms of service apply. |
Cloudflare (Turnstile) Security Low | Bot and abuse protection on public-facing forms (ICI submissions, contact, login). | Browser fingerprint, IP, user agent, interaction telemetry with the widget. | Global edge network; closest region to the user is selected automatically. | Cloudflare DPA countersigned on standard terms. |
The list above is the working register. It will be reviewed and updated as part of our Phase 2 compliance work. Items still to be closed are flagged as open risks in our internal compliance baseline.
Safeguards we require
- A signed data processing agreement (or equivalent standard terms) on file before any data is shared.
- Confirmation of the sub-processor's security certifications relevant to the data we share.
- A documented region of processing, captured in the table above.
- An exit clause that lets us retrieve or delete personal data on termination.
- Notification of any sub-processor-of-a-sub-processor change.
AI providers (special notes)
AI providers receive prompt payloads that may include organisation names, assessment answers, and conversation history. They are configured to not use those payloads for model training where the vendor offers that option. We minimise what we send (see the data minimisation work in Phase 2) and we review AI reports before they reach a client.
Before any new AI provider is added, we run a vendor security review that covers data handling, retention, training opt-out, region, and breach notification. The review is filed in docs/vendor-assessments/.
Right to object
Under GDPR Article 21 you have the right to object to processing based on legitimate interest and to object to processing for direct marketing. If you have a specific concern about one of the sub-processors above, contact legal@mindarchitecturegroup.com and we will respond within 30 days.
Changes to this register
We will post material changes on this page and bump the version number and last-updated date. Active users will receive at least 30 days' email notice before any new sub-processor is added.
