Skip to content

Legal

Subprocessors

Last updated 12 October 2026

A subprocessor is a third party VORX AI Software Ltd ("Vorx") engages to process personal information on our behalf in order to deliver the Platform described in our Privacy Policy. This page lists our current subprocessors, drawn directly from the vendors actually wired into our infrastructure rather than a generic list, and what each one is used for.

We review this list against our own configuration when we publish it, but vendors and their roles can change between reviews. Legal entity names below are the vendors' commonly known trading names; contact legal@vorx.com for the precise contracting entity behind any of them, to be notified of changes, or with any other questions.

1. How to read this list

Each entry names the vendor, what we use it for, and roughly what kind of data passes through it. A vendor appears here because Vorx's own infrastructure calls it directly — we did not include tools that only support our internal operations (accounting, recruiting, and the like) and never touch Platform data.

Some vendors act as an intermediary in front of other providers. Where that's true, we say so explicitly rather than listing only the name closest to us.

2. AI model inference — OpenRouter, and the model providers it routes to

Vorx does not hold direct accounts with individual AI model providers. Model calls made while generating, editing or repairing your app — including the text of your prompts and the code and content generated in response — are routed through OpenRouter, which passes each call to a provider that serves the model configured for that step. At the time of writing those models come from:

  • Anthropic (Claude models) and Google (Gemini models), for design, building, editing and classifying requests, and for generating images.

  • DeepSeek (DeepSeek models), for editing an app when you ask for a change, and for the first attempt at repairing code that fails to build. These calls carry your request, your app's code and, for a repair, the error it produced. OpenRouter may serve them from DeepSeek itself, which is based in China, or from Novita, DeepInfra, Fireworks or Morph.

  • OpenAI (GPT models), when an app you build on Vorx uses Vorx-provided AI features: the text your app sends, which can include what its own users type.

These providers are subprocessors of OpenRouter for this purpose rather than of Vorx directly, but we name them here because it is where your prompt and code content actually goes.

We are evaluating a direct integration with Anthropic for some model calls. Anthropic is not in use as a direct subprocessor today; we name it now so that, if that evaluation ships, the same processing described above may also flow to Anthropic directly without changing what this page has already told you.

3. Hosting, CDN and deployment — Cloudflare, Fly.io, Google Cloud

  • Cloudflare — DNS, CDN, and edge delivery for vorx.com and published customer sites/apps; sees request traffic to those domains.
  • Fly.io — hosts live preview instances of in-progress builds while you're working on them, in the United States (Ashburn, Virginia). Each preview holds a copy of your app's code and its configuration, including the address and keys of its backend.
  • Google Cloud Platform — our main systems: the services that run the Platform (Cloud Run), the database that holds your account, workspace and project data (Cloud SQL), messaging between services (Pub/Sub), and file storage for uploaded assets (Google Cloud Storage). They run in the United States (us-central1, Iowa).

4. Customer app backends — Supabase

If you opt an app into a cloud backend, its database and related backend services are provisioned on Supabase infrastructure, under a project Vorx manages on your behalf, in the United States (us-east-1) by default. Data your app's own users create through it — the app's own end-user data, not just your Vorx account data — is stored there.

5. Billing and payments — Stripe

Stripe processes subscription billing and payment card details. Vorx does not store full card numbers; Stripe handles that as an independent PCI-DSS compliant processor.

6. Authentication and SSO — WorkOS

WorkOS brokers enterprise single sign-on (SSO/SAML) and directory sync for organizations that use it, and handles the identity data that flow requires (email, name, and whatever attributes your identity provider sends).

If you choose to sign in with Google or Microsoft, that provider confirms who you are and shares your name and email address with us. It acts as your chosen identity provider under your own account with it, so it is not listed here as a Vorx subprocessor.

7. Transactional email — Postmark

Postmark delivers account, billing, and notification emails on our behalf, which necessarily includes your email address and the content of those messages.

8. Product and website analytics — PostHog, Google Analytics

  • PostHog — product analytics and session replay inside the Vorx app itself, so we can see where builders get stuck. Runs only in production, on PostHog's EU Cloud (data is processed in the EU). We identify you to PostHog by your name and email address so we can follow up on problems you hit. It can capture in-app interactions and screen recordings of your Vorx sessions — of the Vorx interface, not of your published app's end users.
  • Google Analytics — page analytics on the vorx.com marketing site only. Analytics storage is off by default and only enabled if a visitor grants consent; ad storage and ad personalization stay denied either way. It does not run inside the app.

9. Images and design references — Pexels, Figma

  • Pexels — stock photo search. When a build needs an image, Vorx sends Pexels a short search query, such as a product name or a description of the picture wanted. Queries are drawn from your app's content; no account details are sent.
  • Figma — if your prompt links to a Figma design, Vorx fetches that frame from Figma to build from it.

10. Code hosting you connect — GitHub

GitHub — if you connect a GitHub organization to a project, Vorx's GitHub App pushes your app's code to a repository in that organization. Vorx only sends code there at your direction. We do not keep copies of customer code in GitHub repositories of our own.

11. Services your app uses with your own account

Some features let your app connect to a service with your own account, such as sending email through SendGrid or Resend, taking payments with PayPal, or messaging with Twilio. Those services process your app's data for you, under your agreement with them, so they are not Vorx subprocessors and are not listed above.

12. Changes to this list

We'll update the date at the top of this page when we add, remove, or change the role of a subprocessor. For material additions, contact legal@vorx.com to ask about advance-notice arrangements for your account.

Change log

  • 2026-10-12 — Checked again against production configuration. DeepSeek is now also the model for editing apps, not only for repairs. Added OpenAI, used when apps built on Vorx use Vorx-provided AI features. Added where Google Cloud, Fly.io and Supabase run (the United States), and that we identify you to PostHog by name and email.
  • 2026-09-29 — Checked against the services our production systems are configured to call. Added DeepSeek and its hosts to AI inference (code repair), and Pexels and Figma (images and design references). Named GitHub, which receives code only at your direction. Said that Google and Microsoft sign-in are identity providers you choose, and that services your app uses with your own account are not Vorx subprocessors. Described what a Fly.io preview holds.
  • 2026-08-26 — First published.