Skip to content
Hands and notebooks on a wooden table during a meeting

Subprocessors

Controller or processor
Antitropy, LLC, depending on context
Count
Five
Notice of change
Before a new subprocessor begins processing customer data
Updated
9 September 2026
Status
Draft for counsel review

These are the third parties that may process data on our behalf in the course of operating this website and building the Riopex platform. The list is short on purpose, and it is complete.

No customer data is processed by any of these today, and the list is published in advance because a group evaluating us will ask for it. A list produced only on demand is a list nobody has checked.

Regions

Region below is where processing is configured to take place for us, not where the provider is incorporated. For a pilot, the platform's database and file storage region is chosen with the customer, and residency requirements are a scoping question we answer specifically rather than generically.

Changes

We will give notice before a new subprocessor begins processing customer data, and a customer under a data processing agreement may object under the terms of that agreement. Adding a provider that touches only our own internal operations, and no customer data, is not a change to this list.

If you would like to be told when this page changes, say so at privacy@riopex.com.

Subprocessors, purpose and processing region
ProviderPurposeRegionData it may process
VercelHosting and content delivery for riopex.com and the applicationUnited States and European Union edge regionsRequest records, including IP address and user agent; anything submitted through the pilot form in transit
SupabaseManaged Postgres database, authentication and private file storage for the platformChosen per deployment; selected with the customer for a pilotPlatform account details and customer telecom records, including invoice artifacts
ResendTransactional email: replies to pilot enquiries and platform notificationsUnited StatesName and email address, and the content of the message being sent
SentryError tracking and performance monitoringEuropean UnionDiagnostic events with personal data scrubbed before sending; entity identifiers rather than names, and no invoice content
AnthropicAI extraction of invoice documents into structured lines, behind a review queueUnited StatesInvoice document content submitted for extraction; it is not used to train models, and prompts and invoice bodies are never sent to error tracking