Sub-processors
Who touches your data.
DRAFT — last updated 10 November 2026 · pending legal review
DRAFT. Not yet reviewed by counsel. Confirm each row against the live configuration before publication.
When ICRX processes team data on behalf of a team, these are the sub-processors we use. We will give teams prior notice of additions or replacements as described in the data processing terms.
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Supabase | Database, authentication, file storage, scheduled jobs | All team and account data | EU — Ireland (eu-west-1) |
| Vercel | Website and app hosting, serverless functions | Request metadata (IP), transient request payloads | [CONFIRM: EU/global edge] |
| Stripe | Subscription billing and payments | Billing contact, subscription status, payment details (held by Stripe) | [CONFIRM: EU / US] |
| Resend | Transactional email | Recipient email, message content (invites, resets, notices) | [CONFIRM: region] |
| Google — Firebase Cloud Messaging | Push notifications to mobile apps | Device token, notification text | US / global |
| Google Workspace | Support and sales email | Correspondence | EU / global |
| Anthropic | Help assistant (when enabled) | The question typed by the user | US |
| Sentry | Error monitoring for the app | Error traces with an opaque user and org id (no email or name), a 10% sample of performance traces, text-masked replays of sessions that hit an error, browser security (CSP) reports | EU — Germany (Frankfurt) |
Transfers outside the EEA rely on the EU–US Data Privacy Framework and/or Standard Contractual Clauses. Questions: privacy@icrxms.com.
Back to Privacy