Sub-processors
Who helps us run xNet Cloud, what they receive, and where they operate.
Last updated: June 24, 2026
These third parties process data on our behalf to provide xNet Cloud, our managed, paid service. The local-first app and self-hosted hubs use none of them. Services you choose to connect yourself (such as GitHub, Notion, Slack, or your own webhooks) are your integrations, not our sub-processors, and their own terms govern.
| Provider | Purpose | Data processed | Location |
|---|---|---|---|
| WorkOS | Accounts, authentication, SSO/SCIM | Email, name, account identifier | United States |
| Stripe | Payments and AI usage metering | Email, customer reference, plan, charge amounts | United States |
| Google Cloud (Cloud Run, Firestore) | Hub compute and control-plane state | Tenant metadata, AI usage totals, your running hub | Per plan; region-pinned for Enterprise |
| Cloudflare R2 | Encrypted content blobs and database backups | Encrypted tenant content, database snapshots | Cloudflare network |
| OpenRouter | Managed AI gateway (opt-in feature) | Prompt and message content you send to the AI | United States / selected model provider |
| Sentry | Error monitoring (opt-in, off by default) | Scrubbed crash reports (no documents) | United States |
| Plausible Analytics | Cookieless website analytics | Page views, country, device type (no personal data) | European Union |
Changes to this list
We update this page when we add, remove, or change a sub-processor and bump the date above. Business customers under our Data Processing Addendum receive advance notice of new sub-processors and may object as described there. For questions, contact privacy@xnet.fyi.
See also our Privacy Policy and Terms of Service.