Skip to content
IX ICRX MS
Component life Flagship Operations Crew & travel New Financials New Workshop & mechanics Engineering Beta All modules
Pricing FAQ Docs
Component life Flagship Operations Crew & travel New Financials New Workshop & mechanics Engineering Beta All modules
Pricing FAQ Docs Log in
Log in Join the waitlist

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.

ProviderPurposeDataLocation
SupabaseDatabase, authentication, file storage, scheduled jobsAll team and account dataEU — Ireland (eu-west-1)
VercelWebsite and app hosting, serverless functionsRequest metadata (IP), transient request payloads[CONFIRM: EU/global edge]
StripeSubscription billing and paymentsBilling contact, subscription status, payment details (held by Stripe)[CONFIRM: EU / US]
ResendTransactional emailRecipient email, message content (invites, resets, notices)[CONFIRM: region]
Google — Firebase Cloud MessagingPush notifications to mobile appsDevice token, notification textUS / global
Google WorkspaceSupport and sales emailCorrespondenceEU / global
AnthropicHelp assistant (when enabled)The question typed by the userUS
SentryError monitoring for the appError 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) reportsEU — 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
IX ICRX MS
Overview Pricing Log in Privacy Sub-processors DPA Brand hello@icrxms.com
© 2026 ICRX · Built in the paddock 🇪🇸