← All legal documents

Subprocessors

Version: 1.0 (DRAFT — v3.7 alignment notes appended 2026-05-11; signed-off form gated on F-13 lawyer review) Last updated: 2026-05-04 (v3.3 era body) + 2026-05-11 (v3.7 alignment notes) Public URL when live: https://meandai.io/legal/subprocessors

This page lists every third party that meandai engages to process personal data on behalf of customers, in fulfilment of Article 28(2) and (4) GDPR and the Data Processing Agreement §7. The list is normative: every subprocessor that touches customer data is named here, with the country, purpose, and DPA URL.


v3.7 alignment notes (2026-05-11 autonomous Track B; pre-lawyer-review for F-13)

This document was authored 2026-05-04 against Stack v3.3 / Master Blueprint v3.4 era. Stack v3.7 (locked 2026-05-07) materially changes the subprocessor list across 6 vendors + 1 region. The body below is preserved as the v3.3-era baseline. The lawyer reviewing under F-13 must incorporate the changes below into the signed-off legal pack BEFORE Phase 1 paid-beta launch.

What v3.7 changes (subprocessor table)

Current entry (v3.3 baseline below)v3.7 statusReplacement (when migration completes)
AWS KMS — eu-central-1 (Frankfurt)REGION_DRIFTAWS KMS — us-east-1 (N. Virginia) per Stack v3.7 §1.2 + §3.10 (US-first lock)
Neon — eu-central-1 (Frankfurt)REGION_DRIFTNeon — us-east-1 per Stack v3.7 §3.3
Neo4j Aura — BelgiumDEMOTEDFalkorDB Cloud preferred per Stack v3.7 §3.5 (us-east-1 if commercial terms clean); Aura demoted to fallback only
Resend — EU regionLEGACY (TRANSITION)Postmark per Stack v3.7 §3.11 (US region); replacement gated on Stefan Postmark signup
Paddle.com Market Limited — Ireland (EU)REMOVEDStripe per Stack v3.7 §3.13 + ADR-006 + ADR-018 (Stripe-only Phase 1 billing); replacement gated on Wyoming LLC formation chain (ADR-005 + ADR-017)
Doppler — United StatesLEGACY (TRANSITION)AWS Secrets Manager — us-east-1 per Stack v3.7 §3.9; replacement gated on F-9
PostHog (EU)LEGACYPostHog Cloud US per Stack v3.7 §3.12 (frontend/lib/posthog-client.ts default fixed in commit 6aa6420a)
Cloudflare R2 — EU/GlobalROLE_CHANGECloudflare R2 — backup-only role per Stack v3.7 §3.7 (NOT primary artefact storage); primary becomes AWS S3 us-east-1 per §3.6
(NEW) Weaviate Cloud USNEWWeaviate Cloud — US per Stack v3.7 §3.4 (semantic memory layer); not in v3.3 baseline; gated on Stefan signup
(NEW) AWS S3 us-east-1NEWAWS S3 — us-east-1 per Stack v3.7 §3.6 (raw artefact storage primary); gated on F-9

What v3.7 confirms (no change)

  • Clerk (US) — auth + tenant orgs.
  • Inngest — workflow / cron / event engine.
  • Logfire — observability (region update to US per Stack v3.7 §2.1).
  • Anthropic / OpenAI / etc. — LLM providers via shared-llm.
  • Notification policy (30-day prior notice + RSS-watchable + in-app changelog) — unchanged.
  • DPA / Article 28(2) GDPR posture — unchanged at the contract layer; subprocessor identity changes within DPA framework.

Commercial-entity change

The contracting party changes from Montenegro company (predecessor implicit) to Wyoming LLC for Phase 1 commercial distribution per Stack v3.7 §1.3 + ADR-005 + ADR-017. Customer-facing invoice identity = Wyoming LLC. Montenegro company remains the platform/IP/development entity. Intercompany distribution/licence agreement gates the legal-pack signed form.

Notification timeline impact

Per the 30-day prior-notice policy (§"Notification policy"):

  • Region migrations (eu-central-1 → us-east-1 for AWS KMS + Neon) → require 30-day notice if any tenant is already onboarded. Today: 3 tenants (MLA + meandai.io + Sandbox), all internal; no external customer notice required for now.
  • Vendor swaps (Paddle → Stripe / Doppler → AWS Secrets / Resend → Postmark / Aura → FalkorDB) → same 30-day rule when external customers exist; for current internal-only state no notice required.
  • Order of operations: all subprocessor changes lock in BEFORE first paid-beta tenant onboards; no live customer ever sees an in-flight subprocessor swap.

Linkbacks to migration tracking

What CTO Tower CANNOT change in this doc

The body subprocessor TABLE (rows 33-47) is preserved as the v3.3-era baseline. CTO Tower does not edit signed-off-target legal-pack content per Master Blueprint v3.7 §10 + CTO Tower v2.3 §1.3 ("legal signatures" + "legal review" are founder/lawyer responsibilities). The lawyer in F-13 review takes these alignment notes and produces the v3.7-aligned signed-off subprocessor table.

This DRAFT v1.0 + alignment notes is input to F-13, not a replacement for it. Signed-off normative subprocessor list lands when Stefan + lawyer complete F-13 review and produce v1.1 (or v2.0).


Notification policy

We give all active customers at least 30 days' prior notice of any new or replacement subprocessor by:

  1. Email to the customer's primary contact, and
  2. Update of this page (the public URL is RSS-watchable for customer compliance teams), and
  3. In-app changelog entry under Settings → Compliance.

Within that 30-day window, a customer may object on documented data-protection grounds. If the parties cannot agree on a reasonable alternative within a further 30 days, the customer may terminate the affected services without penalty per DPA §7.2.

Categories

CategoryEngagement modelDefault opt-in / opt-out
Infrastructure — required for the platform to functionAll customersOpt-out impossible without termination
Platform services — auth, jobs, email, paymentsAll customersOpt-out impossible without termination
AI model providers — invoked per inference callAll customers, routed through shared-llmPer-tenant model preference (e.g., disable OpenAI fallback) configurable by Stefan on Enterprise
Observability — logs and product analyticsAll customers (logs) / opt-in (product analytics)Logs cannot be opted out (Art. 32 audit trail); product analytics granular consent via Cookie Banner
Marketing channels — Buffer, Meta, LinkedIn, TikTok, YouTubeTenant-connected (only if customer connects)N/A — customer initiates the connection

A. Infrastructure

SubprocessorCountryPurposeDPA URLLast reviewed
Amazon Web Services, Inc. (AWS)EU — eu-central-1 (Frankfurt)Key Management Service for envelope encryption (per-tenant DEK and system-level CMK). Plaintext customer data never crosses the AWS boundary; only KMS-wrapped DEKs do.https://aws.amazon.com/agreement/ + GDPR DPA at https://aws.amazon.com/compliance/gdpr-center/2026-05-04
Neon, Inc.EU — eu-central-1 (Frankfurt)Postgres database (primary tenant data store). Per-tenant FORCE RLS isolation.https://neon.tech/dpa2026-05-04
Neo4j, Inc. (Aura)EU — BelgiumGraph database (per-tenant knowledge graph). Per-tenant database isolation.https://neo4j.com/legal/dpa/2026-05-04
Cloudflare, Inc.Global edge (EU presence) for CDN/Turnstile; EU region (WEUR) for R2 bucket meandai-backupsCDN, Turnstile (anti-bot), R2 object storage for encrypted Postgres dumps.https://www.cloudflare.com/cloudflare-customer-dpa/2026-05-04
Railway Corp.EU region (configurable; default eu-west)FastAPI service hosting (~34 services), Inngest worker hosting.https://railway.com/legal/dpa2026-05-04
Doppler, Inc.United StatesSecret management — system credentials only. No customer personal data ever sent to Doppler. Listed because of the (encrypted) secret store containing OAuth refresh tokens of meandai's own admin accounts to vendor services.https://www.doppler.com/legal/dpa2026-05-04

B. Platform services

SubprocessorCountryPurposeDPA URLLast reviewed
Clerk, Inc.EU region (cloud-eu)Authentication of Authorised Users — sign-up, sign-in, session, MFA, JWT issuance.https://clerk.com/legal/dpa2026-05-04
Inngest, Inc.United StatesBackground job orchestration — durable cron, queue, retry. Job payloads carry metadata only (job id, run id, tenant id slug, tags); customer personal data is fetched from Neon at job execution time, not stored in Inngest.https://www.inngest.com/legal/dpa2026-05-04
Resend, Inc.EU regionTransactional email — billing receipts, security alerts, account notifications, customer-facing AI-drafted email when sent on customer's behalf via Resend SMTP relay.https://resend.com/legal/dpa2026-05-04
Paddle.com Market LimitedIreland (EU)Subscription billing, tax compliance (Merchant of Record), payment processing. Receives the customer's billing email and company info; never receives customer-tenant content.https://www.paddle.com/legal/data-processing-agreement2026-05-04 (Live target Track 3)

C. AI model providers

These are routed via the shared-llm package, with per-tenant model preference and per-call telemetry. We have a contractual commitment from each that customer data submitted via inference calls is not used to train any model and is retained only as required to provide the API response.

SubprocessorCountryPurposeDPA URLLast reviewed
Anthropic, PBCUnited StatesClaude family LLM inference (default for chat, judge, planning, brand synthesis).https://www.anthropic.com/legal/dpa + EU SCCs 2021/914 + DPF2026-05-04
OpenAI, L.L.C.United StatesGPT family inference (fallback for routing failures), Whisper (audio transcription), TTS (voice output).https://openai.com/policies/eu-data-processing-addendum + EU SCCs 2021/914 + DPF2026-05-04
fal.ai, Inc.United StatesImage generation (when tenant requests; no default invocation).EU SCCs 2021/914 (per https://fal.ai/legal/dpa)2026-05-04 — opt-in, not default
Google LLC (Gemini, optional)United States / EU regionsLLM fallback (not default; configured per-tenant on request only). Engaged only when customer's brand-pack model_preferences includes Gemini.https://cloud.google.com/terms/data-processing-addendum + DPF2026-05-04 — opt-in, not default

D. Observability

SubprocessorCountryPurposeDPA URLLast reviewed
Pydantic Services Ltd. (Logfire)EU regionStructured-log observability (every agent run, every tool call, every judge verdict). PII redaction policy applied at emit time; full payload retained 30 days; aggregates retained 1 year.https://pydantic.dev/legal/dpa2026-05-04
PostHog, Inc.EU region (cloud-eu)Product analytics (Authorised User events) — opt-in via Cookie Banner only; not loaded for visitors who reject analytics. Feature flags used by judge-gate auto-flip and kill switch.https://posthog.com/dpa2026-05-04
Better Stack (Pingdom-equivalent)EUPublic uptime page (status.meandai.io) — does not access customer data.https://betterstack.com/dpa2026-05-04

E. Marketing channels (tenant-connected only)

These subprocessors only receive personal data if the customer connects them. They are listed here for transparency but are not engaged by default.

SubprocessorCountryPurposeDPA URLLast reviewed
Buffer, Inc.United StatesScheduled posting to social channels (Buffer fans-out to Instagram / LinkedIn / TikTok / YouTube on tenant's connected accounts).https://buffer.com/legal/dpa2026-05-04
Meta Platforms, Inc.Ireland (Meta Ireland) for EU usersPosting + reading Instagram, Facebook on the tenant's connected accounts.https://www.facebook.com/legal/terms/dataprocessing2026-05-04
LinkedIn CorporationIreland (LinkedIn Ireland)Posting on the tenant's connected LinkedIn pages / personal profile.https://www.linkedin.com/legal/l/dpa2026-05-04
TikTok / Bytedance Ltd.Ireland for EU usersPosting on the tenant's connected TikTok account.https://www.tiktok.com/legal/page/eea/dpa-addendum/en2026-05-04
Google LLC (YouTube)United States / EU regionsPosting on the tenant's connected YouTube channel.https://cloud.google.com/terms/data-processing-addendum + DPF2026-05-04
Telegram FZ-LLCUAEOut-of-band kill switch + admin notifications via meandai's bot. No customer personal data sent, only platform alerts.https://telegram.org/privacy2026-05-04
WhatsApp Ireland Ltd. (Meta)IrelandWhatsApp Business messaging when the tenant connects its WABA.https://www.whatsapp.com/legal/dataprocessing-business2026-05-04 — opt-in, not default
Zoom Video Communications, Inc.United States / EU regions for EU customersMeeting recordings + transcripts when the tenant connects Zoom; otherwise not engaged.https://explore.zoom.us/en/data-processing-addendum/2026-05-04 — opt-in, not default

F. Insurance and professional services

These are not "subprocessors" in the strict GDPR sense (they do not process personal data on our instructions to provide the platform), but they are listed for transparency because they may receive incident-related personal data.

RecipientCountryEngagementPersonal data category
Coalition, Inc. (cyber + tech E&O insurance)United States, EU operationsOn insurance claim onlyIncident report metadata, breach notification material
External lawyer (TBD via Track 0.C)Montenegro / EUOn legal matter onlyAs required by the matter
External accountantMontenegroAnnual filingsBilling data, employee data (when staff hired)
Securitum / DeepStrike (planned annual pentest)EUScheduled engagement under NDASynthetic test data only — no production tenant data

G. Region map

A summary of where each subprocessor's primary processing occurs:

EU primary (default)        : Neon, Neo4j Aura, Cloudflare R2, Railway, AWS KMS,
                              Resend, Clerk, Logfire, PostHog, Paddle, Better Stack
US primary                  : Anthropic, OpenAI, fal.ai, Inngest (metadata only),
                              Doppler (system secrets only)
EU primary, US data-sharing : Cloudflare edge (global), Buffer/Meta/LinkedIn (tenant-connected)

H. Cross-border transfer mechanisms

Where a subprocessor primarily operates outside the EEA, the legal mechanism for transfer is documented per-subprocessor:

  • Anthropic, OpenAI, fal.ai — EU Standard Contractual Clauses 2021/914 Module Two + transfer impact assessment (TIA). Anthropic and OpenAI also rely on the EU-US Data Privacy Framework (DPF) where adequacy is in force.
  • Inngest, Doppler — EU SCCs 2021/914 Module Two; data sent is metadata/system credentials, not customer personal data.
  • Telegram, Buffer, Meta, LinkedIn, TikTok — relevant SCCs and the subprocessor's own DPA, executed at the moment the customer connects the integration.

A copy of the executed SCCs and TIAs is available on customer request via privacy@meandai.io.

I. Subprocessor change history

DateChangeNotes
2026-05-04Initial publicationTrack 9 / Wave 19

Internal note — Track 9 / Wave 19:

Paddle is listed as Live-target because Paddle KYC + integration is Track 3 work. Until Paddle is connected, Stripe Connect (US) may be the interim payments processor; if so, this list must be updated and 30 days customer notice given before LIVE flip. Drata Foundation (compliance evidence) is not a subprocessor — it ingests platform metadata (Doppler audit log, Clerk audit log) but does not see customer personal data; it is listed as a recipient in the AUP §4 enforcement evidence trail, not here.