Last updated: August 5, 2026
A sub-processor is any third party we use that processes personal data, or that personal data passes through, in the course of running the Service. We keep this list short on purpose. Everything below is derived from the codebase and infrastructure configuration that actually runs the Service, not written from memory — see the Privacy Policy §6 for the summary version of this same list.
| Sub-processor | Purpose | Data | Location |
|---|---|---|---|
| Scaleway | Compute hosting the hardware-isolated VM for each session; the control-plane database and audit log; S3-compatible object storage for checkpoints and templates; and, as of August 2026, transactional email (sign-in codes, team invitations, account notices) via Scaleway Transactional Email. | Session, checkpoint, and template disk/memory state (may include whatever data you send into your own sessions); account, billing, and audit-log metadata; recipient address and content of transactional email. | EU — fr-par (Paris, France). |
| Stripe | Payment processing — checkout, billing portal, and prepaid top-up webhooks. | Billing email address, prepaid top-up transaction records, Stripe customer ID. Card and payment details are entered directly into Stripe’s own hosted pages and never reach our servers. | Not yet confirmed — we have not verified the exact data-processing location for our Stripe account, so we do not claim it is EU-only. See the Privacy Policy, sections 4 and 8, for how this affects the international-transfer commitment. |
| GitHub | Optional OAuth sign-in — only if you choose "Continue with GitHub" instead of email. | Your GitHub account ID and the verified email address on your GitHub account. We store only those two fields, not your broader GitHub profile. | Processed by GitHub as part of its own OAuth flow; not under our control. |
| Optional OAuth sign-in — only if you choose "Continue with Google" instead of email. | Your Google account ID and verified email address. We store only those two fields, not the rest of your Google profile. | Processed by Google as part of its own OAuth flow; not under our control. | |
| Cloudflare | DNS resolution for our domains, and inbound email routing for @inis.run addresses. DNS-only (not proxied, no traffic visibility) for every hostname except our public status page. | DNS query metadata for our domains; for status.inis.run only, standard web request metadata (Cloudflare terminates TLS for that one static, public page). Inbound mail addressed to @inis.run passes through Cloudflare Email Routing to reach the inbox it forwards to. | Global anycast network; Cloudflare is a US company. No session or application traffic passes through it. Inbound email to our @inis.run addresses does, as described above. |
No analytics, advertising, support-desk, or CRM integration is wired into the codebase — no PostHog, Segment, Mixpanel, Amplitude, Sentry, Intercom, Zendesk, HubSpot, or Google Analytics. Operational metrics and logs are self-hosted on our own infrastructure and never shared with an analytics broker.
We will give at least 30 days’ notice, by email or in-product notice, before adding or replacing a sub-processor that processes personal data, so you can object — and, if we cannot resolve the objection, stop using the Service and close your account before the change takes effect. See Privacy Policy §6.
Questions about this list? Contact privacy@inis.run.
See also the Data Processing Agreement and the security overview.