Wamemba meLegal

How we keep ourselves accountable

Transfer risk assessment

Version 1.0In effect from 15 October 2026See every change

This document assesses each restricted transfer of personal data from Wamemba me to a recipient outside the UK, or to a company that can access UK-stored data from the USA. It follows the ICO transfer risk assessment (TRA) tool:

  • ICO, International transfers: https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/international-transfers/
  • ICO, Transfer risk assessments: https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/international-transfers/international-data-transfer-agreement-and-guidance/transfer-risk-assessments/
  • DSIT, UK-US data bridge supporting documents (analysis of US law): https://www.gov.uk/government/publications/uk-us-data-bridge-supporting-documents

Vendor facts come from register/subprocessors.json (vendor pages read 2026-10-14; DPF participant list dated 2026-10-14). This document is not legal advice. A qualified lawyer has not reviewed it.

1. Method and design choice

For each transfer: (1) circumstances, (2) harm if a third party, including a public authority, accessed the data, (3) enforceability and the likelihood of access in the destination, (4) extra protections and conclusion.

The design keeps the sensitive data at home. The children's data (names, birthdays, sayings, meanings, clips) is stored only in Supabase's London region. What goes abroad is either telemetry without content (Sentry, PostHog: EU, adequate), technical data (Expo, Vercel), or messages that parents choose to send us (Namecheap forwarding). The one exception is remote support access to the London database by Supabase, Inc. (US).

Groups:

  • Group A: UK Extension (UK-US data bridge). The recipient is certified under the EU-US Data Privacy Framework with the UK Extension. The Data Protection (Adequacy) (United States of America) Regulations 2023 make these transfers lawful without a TRA. They are recorded because certification can lapse.
  • Group B: SCCs with the UK Addendum, or the IDTA. Article 46 safeguards; a TRA is required.
  • Group C: EU and EEA. UK adequacy regulations cover them; no TRA needed.
  • Group D: independent controllers. The parent deals with them directly (Apple, Google); not our transfer.
  • Gap: no valid mechanism.

2. US law (common to US recipients)

LawEffectRelevance
FISA s.702Compelled collection from US electronic communication service providers of non-US persons' communications for foreign intelligenceApplies to every US cloud provider. Its reauthorisation (RISAA, April 2024) ran to April 2026; unverified: status after April 2026
EO 12333Signals intelligence outside the USMitigated by TLS
CLOUD ActUS warrants reach data US providers hold abroad, including in LondonApplies to Supabase's US parent access and AWS
EO 14086Necessity and proportionality limits; redress through the Data Protection Review Court; the UK is a qualifying state (2023)Basis of the UK Extension

Likelihood for Wamemba me. The data is the private family notes of ordinary households, with no intelligence value, no government or defence users, and no request ever received. Likelihood of US public-authority access: remote. Harm if it happened: moderate to high, because it concerns children.

Litigation. The EU General Court upheld the EU-US DPF (Latombe, T-553/23, 3 September 2025); an appeal is pending (C-703/25 P). If the EU decision falls, the UK Extension is likely to be reviewed. Fallbacks are listed per recipient.

3. Transfers

T1. Supabase, Inc. support access (Group B)

QuestionAnswer
CircumstancesData stored in London (AWS eu-west-2). Supabase, Inc. (US) can access it to provide support. Contract with Supabase Pte. Ltd. (Singapore). SCCs Modules 2/3 + UK Addendum, incorporated
HarmHigh in principle (children's data)
Enforceability and accessSCC clause 15 (challenge and notify government requests); EO 14086 redress; access is for support only
Extra protectionsData at rest in London; encryption at rest and in transit; access controls; we open no support ticket that grants data access without need
ConclusionProceed. Residual risk low

T2. Vercel Inc. (Group A)

Visitor IP addresses and request data for wamemba.me and insight.wamemba.me (and share pages, coming). Served at the nearest edge (London for UK visitors). DPF with UK Extension active to 2027-04-29; SCCs Modules 1-3 + UK IDTA fallback. Harm low. Lawful. Share pages (S3) will carry a child's first name, age and words: re-assess when S3 ships, and keep pages noindex with short cache rules.

T3. RevenueCat, Inc. (Group B, coming)

QuestionAnswer
CircumstancesApp user id (= Supabase id), store transactions, product and status. US (AWS, Snowflake). SCCs Modules 2/3 + ICO IDTA Addendum. Not on DPF
HarmLow: no children's data, no content, no card data
Enforceability and accessSCC clause 15; EO 14086
Extra protectionsOnly the opaque user id; no name or email sent to RevenueCat
Open pointDPA Annex 3 lists AI sub-processors (OpenAI, Anthropic): confirm before S4 what data reaches them
ConclusionProceed at S4 once the open point is answered

T4. Anthropic (engineering agents) (Group B or gap)

QuestionAnswer
CircumstancesClaude Code sessions that build and operate the service can read production data through the Supabase Management API
MechanismUnder Commercial Terms (Team, Enterprise, API): DPA with SCCs Modules 2/3 + UK IDTA. Under consumer terms (Free, Pro, Max): none
HarmHigh if family content were read; low for schema and aggregate queries
ConclusionGap until the plan is confirmed (ropa.md L10). Meanwhile, operations sessions run only schema and aggregate queries and never read a family's content unless that family asked for help

T5. Namecheap, Inc. email forwarding (gap)

QuestionAnswer
CircumstancesMessages to hello@wamemba.me, including privacy requests, pass through Namecheap's forwarding servers (US) to our mailbox
MechanismNone valid for the UK. Namecheap's DPA (2021) uses the old 2010/87/EU clauses for UK transfers; no IDTA or UK Addendum; not on DPF
HarmLow to moderate: messages from parents, which can mention their children
ConclusionGap. Remedy: move wamemba.me mail to Google Workspace (spec §5) and point MX there (a cost decision: register Namecheap action, owner Garth). Meanwhile, privacy replies ask parents not to send sayings or clips by email

T6. Group A recipients (no TRA required)

RecipientDataDPF + UK ExtValid toFallback
Functional Software (Sentry)Crash reports (stored in the EU; US remote access; org settings in the US)Active2027-05-28SCCs + UK Addendum
PostHogAnalytics events (stored in Frankfurt)Active2027-03-10SCCs + ICO IDTA
650 Industries (Expo)Device IP and versions on update checks; push tokens (coming)Active, re-certification under review2027-10-06None (no UK Addendum in its terms). Watch at each review
Plus Five Five (Resend, coming)Recipient emails, email contentActive, re-certification under review2027-03-03SCCs + UK Addendum
Google (Workspace mailbox)Messages to usActive2027-09-13SCCs
GitHubNo user personal dataActive2027-08-03SCCs + UK Addendum

T7. Group D: Apple and Google stores

Apple (Apple Distribution International for UK customers) and Google act as independent controllers for store accounts, purchases and Sign in with Apple. The parent deals with them directly. Not a transfer by Wamemba me.

4. Actions

IDActionOwner
T-A1Move mail off Namecheap forwarding to Google Workspace on wamemba.meGarth (cost), system (setup)
T-A2Confirm the operations AI plan (Commercial Terms)Garth
T-A3Before S4: RevenueCat Annex 3 AI sub-processorssystem
T-A4At each review: re-check DPF status of every Group A recipient, and FISA s.702's statussystem
T-A5Re-assess Vercel when share pages ship (S3)system

5. Review

Every 6 months, at each trigger above, and if the DPF is struck down. Next review: 2027-04-15.