Sub-processors
Last updated: 2026-06-22
retru·vai uses the following sub-processors to run the Stuart event app and the prep tool. A sub-processor is a third party that processes personal information on our behalf, under a data processing agreement.
We will tell you here, and by email to active users, at least 30 days before adding a new sub-processor.
| Vendor | Service provided | Data processed | Location | DPA / SCC in place |
|---|---|---|---|---|
| Supabase Inc. | Database, authentication, server-side functions | Account, profile, matches, reflections, prep cards, telemetry | Both databases in Stockholm (eu-north-1): the Stuart event project (scosvarlooxicbabtzps) and the prep-tool project; Supabase's corporate HQ and management functions in the USA |
DPA + EU SCCs + UK Addendum |
| Anthropic, PBC | Large language model API | Prompt content (paste, onboarding answers, event context) at the moment of generation. Retained by Anthropic for up to 30 days under their commercial terms for abuse monitoring; longer retention is possible where content is flagged for safety review. Not used to train Anthropic's models under commercial terms. | USA | DPA + EU SCCs + UK Addendum |
| Vercel Inc. | Hosting and edge delivery for the web front-ends | IP address, request metadata. Does not process reflection content (reflections are handled by our Supabase Edge Functions, not Vercel). | USA | DPA + EU SCCs + UK Addendum + DPF / UK Data Bridge |
| Resend (Plus Five Five, Inc.) | Transactional email: sign-in codes and service emails for the Stuart event app | Email address, the contents of the transactional email | USA | DPA + EU SCCs + UK Addendum |
| Functional Software, Inc. (Sentry) | Application error and crash reporting (runtime monitoring is enabled) | Diagnostic and crash data, which can include a user identifier, device and app metadata, and technical context. We do not deliberately send reflection content or pasted material to Sentry. | USA | DPA + EU SCCs + UK Addendum |
| Expo (650 Industries, Inc.) | Push-notification delivery for the Stuart mobile app, via Apple Push Notification service and Google Firebase Cloud Messaging | Device push token and the notification payload (first names and a short framing line only; no location, surname, or reflection content) | USA | DPA + EU SCCs + UK Addendum |
Note on the Anthropic transfer position: Anthropic currently processes prompt content in the USA under the safeguards above.
These are services we use to run the business, that may incidentally process personal data:
| Vendor | Service | Data processed |
|---|---|---|
| Google Workspace | Email (hello@bemorestuart.com) | Inbound and outbound email content |
PostHog (product analytics) is not deployed. If it is enabled in production, this list will be updated at least 30 days before it goes live.
- We do not use any third-party advertising or tracking service.
- We do not use a separate scraping or search vendor. The prep tool does not fetch third-party content at v1.
- We do not pass your identifiable personal data to a third-party AI provider to train their models. Where we train our own models, we use pseudonymised or aggregated data where we can.
If you believe a sub-processor is handling your data incorrectly, email hello@bemorestuart.com. We monitor sub-processor compliance and will follow up directly with the vendor.