Nexus StudioSubprocessors
Last updated 2026-10-19 · the providers that process account data for us
Nexus Studio runs on your machines, and your tests and evidence stay on your machines and reach us only if you send them. The account portal, the license check and this website do run on our side, with the providers below. Each one receives only what its job needs. What we keep ourselves, and for how long, is in the Privacy Policy.
Cloudflare, Resend, Customer.io and Intercom process this data only on our instructions. Stripe processes it for us and also, as a controller in its own right, for fraud prevention and to meet its legal duties, under its own privacy policy. Google, GitHub and Microsoft are not our processors: if you choose to sign in with them, they handle your account with them under their own terms and privacy policies, and send us only what this page lists.
The list
| Provider | What it does for us | What it receives | Where |
|---|---|---|---|
| Cloudflare | Delivery of this website from our own server through Cloudflare's network; hosting of the account portal and the license servers; the database; request logs. | The IP address and headers of every request to us; everything in the database the Privacy Policy lists, such as your email, your license records and the hashes of your keys and machines. | Database: Eastern North America (United States). Portal and license servers: Cloudflare's global network. Website: our own server, delivered through Cloudflare's network. |
| Stripe | Payments: checkout, subscriptions, invoices, receipts, the billing portal, tax. | Your email and account ID from us; your card, billing address and any tax ID straight from you. We never see or store your card. Stripe tells us your customer and subscription IDs, the payment status and the date you have paid until. | United States |
| Resend | Transactional email: sign-in links, trial and renewal reminders, notices about your plan, license and account. | The recipient address and the message. When you apply to the Founding Customer Program, the message we send ourselves contains the fields of your application. Product and follow-up emails go through Customer.io, below. | United States |
| Customer.io | Product tips and follow-up emails after sign-up or a trial; and, only if you accept analytics on this website, page-view and button-click measurement. | Your email address, your plan and renewal date, and account events (account created, trial started, trial ending or ended, subscription started, canceled or ended, payment failed, Studio activated on a computer). With analytics accepted, also an anonymous browser ID, your page views and key button clicks. Never your tests, runs, results or license key. | United States |
| Intercom | The support chat on this website and in the account portal: an AI agent answers first and opens a ticket when it cannot help. It loads only when you press "Chat with the AI agent". | What you type in the chat, your IP address, your device and browser type and the page you are on. In the portal, also your account ID, customer ID and email address. Never your license key or sign-in token. | United States |
| Sign in with Google, only if you choose it. | The sign-in request. It returns your email address and your Google account ID, and nothing else. | United States | |
| Google (Gmail) | Our business mailboxes: support, privacy, security, sales and hello at sentinel-nexusstudio.com, which Cloudflare Email Routing forwards to a Gmail account. | What you write to us and your email address; the copy of each Founding Customer Program application that we email ourselves. | United States |
| GitHub | Sign in with GitHub, only if you choose it. | The sign-in request. We ask GitHub for read access to your profile and email addresses, and keep only your GitHub account ID and your verified primary email address. | United States |
| Microsoft | Sign in with Microsoft, only if you choose it. | The sign-in request. We ask Microsoft for your email address only, and keep your Microsoft account ID and that email address, which we use only when Microsoft confirms that it belongs to you. | United States |
Providers you connect are yours, not ours
The Studio can use services you configure on your own machine: an AI provider (Ollama on your own hardware, the Anthropic or OpenAI APIs or an endpoint compatible with them, or a command-line tool such as Claude Code, Codex, Gemini CLI or opencode), and Jira, Xray, Azure DevOps, Slack or Telegram. They are not our subprocessors. The Studio talks to them straight from your machine, with your own account and keys, under your agreement with them, and nothing of it passes through us.
Changes
We update this page before a new provider starts processing account data, and email account holders when a change affects them.
Questions: [email protected].