Providers, Processors and Other Recipients
Last updated: August 3, 2026
This page identifies third parties relevant to the processing described in the Privacy Policy. A party’s role may vary by feature: the same provider may be Verxion’s processor in one flow and a separate controller in another.
1. Verxion processors
| Provider | Service and main data | Location / transfer | Processing terms |
|---|---|---|---|
| Railway | API and service hosting; PostgreSQL database; operational logs | Production region in the EU; support access may occur under the contract | Railway DPA |
| Amazon Web Services (KMS) | Encryption-key custody; receives cryptographic operations, not plaintext content | eu-north-1 (Stockholm, EEA) | AWS GDPR Center |
| Upstash | Redis for rate limits, idempotency and security; identifiers and hashes | eu-west-2 (UK); EU–UK adequacy decision | Upstash DPA |
| Resend | Transactional email and requested lists; email address, message content and delivery | Sending domain configured in Ireland; the US entity may be covered by SCCs | Resend DPA |
| Sentry | Browser and server error/performance diagnostics; technical traces, pseudonymous IDs and HTTP metadata | Project configured in the German region | Sentry DPA |
| Vercel | Hosting/CDN for the public site and web app; HTTP requests and deployments; Blob storage only if enabled | Global CDN and possible US access; SCCs in applicable terms | Vercel DPA |
| Cloudflare | R2 and CDN/Image Transformations for exercise-instruction images; objects and delivery logs | Bucket configured in Western Europe; US entity and global CDN, with SCCs | Cloudflare DPA |
| PostHog | Optional product analytics and interface errors; pseudonymous ID, events and usage properties. Session recording disabled | European host configured; subject to prior consent | PostHog Trust Center |
PostHog must only initialize after the required consent. Vercel may process data on Verxion’s behalf only under a plan and terms that effectively incorporate its DPA; Verxion verifies that point during periodic contract review.
2. Separate controllers and user-selected third parties
- Apple and Google, when selected for authentication.
- MCP clients and connected applications you authorize through OAuth. The client receives only granted scopes, but its later use is governed by its own terms.
- BYOK AI providers selected for the built-in agent—OpenAI, Anthropic, Google, or OpenRouter and any downstream provider. Verxion relays the conversation from its server using your key and applies available no-training/zero-retention controls, but the provider operates under your relationship with it.
- The AI provider’s search partners, only when you enable web search and the model uses it.
- OpenFoodFacts for food lookups, and YouTube, Vimeo, TikTok, or Instagram/Meta if you add a video link from which minimal public metadata is retrieved.
- Coaches and other authorized users, within the relationship, visibility, and permissions configured in Verxion.
- App stores and payment providers, if a purchase or subscription is activated through their systems.
3. Telegram: operational channel under review
When enabled, Verxion uses Telegram for internal new-signup and feedback alerts. A message may include an email address, username, referral source, category, and free-text feedback. Telegram must not be used for clinical information, credentials, or unnecessary content. This channel is under a data-minimization, location, security, and contractual-role review; until that is complete, Verxion must restrict or disable the personal content sent.
4. International transfers
Where a provider or its subprocessors allow access outside the EEA, Verxion uses the mechanism stated in the applicable terms—normally Standard Contractual Clauses—and supplementary controls such as encryption, pseudonymization, minimization, European regions, and restricted access. Third parties chosen directly by the user may process data in other countries under their own policies.
5. Changes
We will publish material changes before they take effect where possible and update the Privacy Policy or request a new acceptance/choice where law or a purpose change requires it. Contact or reasoned objection: [email protected].
| Date | Change |
|---|---|
| 2026-08-03 | Inventory reconciled with production: Cloudflare R2, browser PostHog, browser/server Sentry, BYOK harness, and Telegram channel. Removed absolute statements about regions or contracts that cannot be verified from code alone. |
| 2026-06-20 | Added optional AI-provider web search. |
| 2026-05-08 | Initial publication. |