Juridisch
Sub-processors
Deze pagina is een rendering van het canonical bestand docs/security/sub-processors.md. Elke wijziging gaat via een PR die zowel dit bestand als het DPA-appendix aanpast en je tenminste 30 dagen vooraf op de hoogte stelt.
Sub-processors (Karet)
Last updated: 2026-10-17 · Owner: Founders · Reviewed: PRD-0035, PRD-0039, PRD-0090, PRD-0095, PRD-0118, PRD-0119, PRD-0129
This file is the canonical inventory of every third-party service that
processes Karet data on our behalf. ADR-0011 §5 makes adding a new
sub-processor a PR that touches this file plus the DPA appendix; a
PR that imports a new third-party SDK without a matching entry here
fails CI (scripts/check-sub-processors.ts).
The list is also mirrored on the public /legal/sub-processors page
(PRD-0036) for user-facing transparency. Customer notice before adding
a new sub-processor is 30 days (DPA appendix).
Active sub-processors
| Name | Purpose | Data categories | Region | Retention | SDK / hostnames |
|---|---|---|---|---|---|
| Vercel | Hosting, edge, blob, AI gateway | All app data, request logs, blob (receipts + voice memos) | EU (FRA1 / DUB1) | 90 days logs; blob per PRD-0036 retention | @vercel/blob, @vercel/*, vercel.sh, vercel-storage.com, ai-gateway.vercel.sh |
| Neon | Postgres (primary data store) | All transactional + journal data | EU (Frankfurt) | While workspace exists; 30-day delete window | @neondatabase/serverless, neon.tech |
| Anthropic | LLM (Claude) for chat, detectors, agents | Prompt content + workspace context (anonymised where possible) | EU processing via AI Gateway; zero-retention contract | 0 days (no-prompt-logging) | via ai + @ai-sdk/anthropic → ai-gateway.vercel.sh |
| OpenAI | LLM (GPT) fallback + embeddings | Prompt content + chat snippets | EU processing via AI Gateway; zero-retention contract | 0 days (no-prompt-logging) | via ai + @ai-sdk/openai → ai-gateway.vercel.sh |
| Resend | Transactional email (magic links, digests, security alerts) | Recipient address, subject line, rendered body | US storage. Resend offers no EU data region; the eu-west-1 setting on a sending domain controls only where mail is routed and sent from, not where data is stored. Transfers under SCCs + EU–U.S. Data Privacy Framework (incl. UK/Swiss extensions); Art. 28 DPA in force. | 30 days e-mail + log data (active account); deleted within 90 days after termination; backups persist 7 days | resend, api.resend.com |
| Enable Banking | PSD2 AIS bank sync (sole bank-data provider, PRD-0095) | Bank account metadata (IBAN, holder name, balances) + transactions for connected accounts | Enable Banking Oy, Finland (EU) — registered AISP supervised by the Finnish FIN-FSA; Karet operates under its licence | While connection active; session deleted on disconnect, consent expires per the bank (up to 180 days, re-consent required) | direct REST → api.enablebanking.com (RS256 JWT); bank consent flow on *.enablebanking.com; bank logos from enablebanking.com |
| Saxo Bank | Brokerage data (positions, trades) | Account positions + trade history | EU (HQ Copenhagen) | While connection active | direct REST → *.saxobank.com |
| Interactive Brokers | Brokerage data via Flex Queries | Account positions + activity statement | US (server-side Karet processes; user opts in) | While connection active | direct REST → ibkr.com |
| Bitvavo | Crypto exchange | Balances + trade history | EU (Netherlands) | While connection active | direct REST → bitvavo.com |
| SnapTrade | Aggregator fallback (DEGIRO, long-tail brokers) | Account snapshot data | Canada (DPA in place) | While connection active | direct REST → snaptrade.com |
| openrouteservice (HeiGIT gGmbH) | Driving distance for a new route in the trip log (PRD-0129) | Two coordinate pairs (start and end point) only; no address, name, user or workspace data | EU (HeiGIT gGmbH, Heidelberg, Germany) | n/a (stateless request; Karet keeps the resulting km as part of the trip) | direct REST → api.openrouteservice.org (API key) |
| PDOK (Kadaster) | Address suggestions and address → coordinates lookup in the trip log (PRD-0129) and postcode lookup in onboarding | The partial or full address being typed (no user or workspace identifiers) | EU (Dutch government, Netherlands) | n/a (stateless, public keyless API) | direct REST → api.pdok.nl (Locatieserver) |
| Have I Been Pwned | k-anonymity breach-password lookup | First 5 chars of SHA-1 hash of candidate password only | Cloudflare global | n/a (stateless) | direct REST → api.pwnedpasswords.com |
| Stripe | Billing (subscriptions, invoicing, tax) | Customer (email, BTW, KvK, billing address), payment-method reference (no PAN), invoice line items | EU (Stripe Payments Europe Ltd, Ireland) | 7 years invoices (NL art. 52 AWR); 30 days webhook bodies | stripe, *.stripe.com |
| PostHog (EU) | Product analytics, funnels, user feedback | distinct_id (userId UUID), event names, non-PII properties; feedback text and scores the user submits (IBANs redacted) | EU Cloud (eu.i.posthog.com, AWS eu-central-1) | 13 months (also mirrored in telemetry_events) | posthog-node, eu.i.posthog.com |
Notes on recent additions (2026-05)
- Stripe — DPA archived at
docs/security/dpas/stripe.pdf. PCI-DSS scope kept to SAQ A via hosted Checkout — Karet never touches PAN. Sub-sub-processors per Stripe's published list. - PostHog (EU) — DPA archived at
docs/security/dpas/posthog.pdf(signed 2026-10-15 by Karet B.V., KvK 04052618, and PostHog Inc.; PandaDoc ref XDLZF-XAHC4-YF2LP-WWZBT). EU Cloud project 307411. Server-side only (noposthog-js): session replay, autocapture, heatmaps and web vitals off. No PII in event properties (lint enforced atsrc/lib/billing/telemetry.ts); feedback text is the user's own words with IBANs masked.
Correction — Resend region and retention (2026-09)
The Resend row previously read "EU region (eu-west-1)" and "90 days delivery logs". Both were wrong, and both overstated our privacy posture:
- Region.
eu-west-1is the sending region chosen per domain. Resend's own GDPR page states plainly that it offers no EU data residency and that all customer data is stored in the US, and that the domain region "controls where email is routed and sent from" — explicitly not where data lives. We had conflated the two. - Retention. 30 days is the active-account retention for e-mail and log data. 90 days is the post-termination deletion window, which is a different thing.
Source: https://resend.com/security/gdpr (checked 2026-09-01).
Open item for the founders, not resolvable in code. The marketing trust
strip, trust section and /trust page all state "Geen data buiten de EU" with
the supporting detail "Vercel fra1 en Neon Frankfurt". That claim is not
accurate while Resend is in the stack: every magic link, security alert and
digest carries a recipient address and a rendered body to US storage. The
options are to qualify the claim, to move transactional e-mail to an
EU-resident sender, or to accept and disclose the transfer. Nobody should edit
that copy without deciding which.
Notes on the PSD2 provider change (2026-10)
- Enable Banking replaced Salt Edge as the bank-data provider (PRD-0095). Salt Edge's live PSD2 access required Karet's own AISP licence + eIDAS certificates, or a €1000/month partner programme; it never left sandbox. Enable Banking Oy (Finland) is a registered AISP supervised by the FIN-FSA and lets Karet operate under its licence.
- Salt Edge is retired, not yet deleted: a code switch
(
SALT_EDGE_RETIRED) stops every connect, callback, webhook and sync, so no data is sent to it. Its code is removed in PRD-0095 M3; the row above stays as history.
Notes on the PSD2 provider change (2026-08)
- Salt Edge replaced Tink (Visa) as the bank-data provider. PRD-0039 migrated all PSD2 AIS to Salt Edge and removed the Tink and GoCardless integrations; no Tink code, credentials or endpoints remain. Tink is therefore removed from the table above rather than kept as historical.
- The PSD2 AISP licence is held by Salt Edge's UK entity — Karet operates under it rather than holding its own AISP authorisation.
Retired (no longer receiving data)
Kept for the record: these processed Karet data in the past. No new data flows to them; their code is still in the repository until it is deleted.
| Name | Purpose (historical) | Data categories (historical) | Region | Retention | SDK / hostnames |
|---|---|---|---|---|---|
| Salt Edge | PSD2 AIS bank sync — retired 2026-10 (PRD-0095), replaced by Enable Banking; never reached live (sandbox only) | Bank account metadata (IBAN, holder name, balances) + transactions for connected accounts | UK entity holds the PSD2 AISP licence; EU data processing | While connection active; credentials + tokens deleted on disconnect, consent expires per PSD2 (90 days, re-consent required) | direct REST → www.saltedge.com/api/v6, hosted Connect flow on saltedge.com |
Pending (not yet active, listed because referenced in code)
- Sentry (EU) — error reporting. EU region required if/when adopted.
- Google Ireland Ltd (Google Analytics + Google Ads) — marketing-site
measurement and advertising (PRD-0119 slices 3–4, ADR-0048 Decision 4).
Browser: one Google tag (gtag.js) on the production marketing host
(karet.money) only, never in the app; Consent Mode v2 with everything
denied by default. Data: pseudonymous identifiers in cookies (
_ga,_gcl_*) set only with consent on the cookie banner, page URLs (including the ad click id Google itself issued), referrer, browser/device signals, thesign_up/generate_leadCTA events, and help-center search terms (e-mail addresses, IBANs and long numbers masked) with their result count; without consent only cookieless pings. Server (slice 4): the ad click id (gclid/gbraid/wbraid, stored only with marketing consent), the conversion (trial started / first paid invoice), its time, the ex-VAT value + currency, and an opaque order id (our outbox row id), sent over REST togoogleads.googleapis.com(OAuth viaoauth2.googleapis.com). No name, e-mail, hashed identifiers (no enhanced conversions), user id or workspace data. Region: Google Ireland Ltd (EU entity); transfers to Google LLC under SCCs / the EU–U.S. Data Privacy Framework. DPA: Google Ads Data Processing Terms + Google Analytics data processing terms (accepted in each product's admin). Hostnames:www.googletagmanager.com,*.google-analytics.com,*.analytics.google.com,*.g.doubleclick.net,www.googleadservices.com,googleads.googleapis.com; no npm package, so the CI import check does not see it. Activates whenNEXT_PUBLIC_GA_MEASUREMENT_ID/NEXT_PUBLIC_GOOGLE_ADS_ID/GOOGLE_ADS_*are set in production; move to Active (with retention: GA4 data retention 14 months) then.
Known gap in the CI check
scripts/check-sub-processors.ts matches npm package imports against
the allowlist below. Every vendor Karet talks to over plain fetch —
Enable Banking, Salt Edge (retired), Saxo, Interactive Brokers, Bitvavo,
SnapTrade, Have I Been Pwned, openrouteservice, PDOK — is invisible to it. That is exactly why the Tink→Salt Edge swap
passed unnoticed: no SDK was added or removed, so there was nothing for
the check to catch.
Until the check also scans outbound hostnames, a direct-REST vendor
change is a manual review item on any PR touching src/lib/connectors/.
Allowlist (scripts/check-sub-processors.ts)
These package-name prefixes are recognised as "third-party SDK" imports by the CI check. A PR adding an import that matches one of the prefixes but has no row above will fail CI.
@anthropic-ai/ → Anthropic
openai → OpenAI
@ai-sdk/anthropic → Anthropic (via Vercel AI SDK)
@ai-sdk/openai → OpenAI (via Vercel AI SDK)
@ai-sdk/gateway → Vercel AI Gateway
@ai-sdk/react → Vercel AI SDK (client hooks; no PII leaves)
ai → Vercel AI SDK
@vercel/ → Vercel (blob, kv, postgres, etc.)
@neondatabase/ → Neon
posthog- → PostHog
@sentry/ → Sentry
@aws-sdk/ → AWS (KMS / SES)
stripe → Stripe
@upstash/ → Upstash (Redis-as-a-service)
resend → Resend
@react-email/ → React Email (rendering; not a sub-processor itself)
better-auth → Better Auth (open source; runs in our process)
drizzle-orm → Drizzle ORM (open source; runs in our process)
@react-email/, better-auth, and drizzle-orm are libraries that
run inside our process and don't ship data to a third party — listed
here so the lint doesn't flag them. Anything new matching the prefix
patterns above must be either added to the active table or explicitly
exempted in EXEMPT_PACKAGES in the script.