Data Protection & GDPR

Privacy Policy

Last updated: August 9, 2026

See also the sub-processor list and Data Processing Agreement for more detail than fits here.

1. Who We Are

The Service is provided by inis.run, an independently owned business established and operating in Ireland; our full legal and registration details are available on request from legal@inis.run. We are the data controller for the personal data this policy describes — your account, billing, and security data. For data you process inside your own sessions (your end users’ data, for example), you are the controller and we act as your processor under the Data Processing Agreement. For anything in this policy, contact privacy@inis.run.

2. Session Content

We do not inspect, read, or log the content of the code you run or the data flowing through a session, by default and by design.

That claim has one honest exception: it describes what we don’t look at, not what we don’t store. If you explicitly save a checkpoint or a template, that saved state — memory and disk — is retained because you asked us to keep it, until you delete it or your account is closed. A session you destroy has its memory and disk deleted. A session that idles out, or reaches its maximum lifetime, is paused instead: its state is preserved, encrypted and in the EU, until you resume it, delete it, or its paused-retention window expires, at which point it is destroyed. We separately record minimal operational metadata about the session itself (duration, resource allocation, and billing metrics) — not its contents.

3. Information We Collect

We collect only the information necessary to provide, bill, and protect the Service:

  • Account information: your email address, used to send sign-in codes, team invitations, and account communications. If you sign in with GitHub or Google instead, we receive and store your account ID and verified email from that provider — see Section 6 for what each one sends us.
  • Billing & transaction details: card and payment details are entered directly into our payment processor’s (Stripe) own hosted pages and never reach our servers. We track your prepaid balance and billing transaction history.
  • Usage metadata: session duration, resource allocation size, storage sizes, and API request rates — collected to meter usage and manage capacity.
  • Network & security logs: IP address, browser type, and request headers, used to detect abuse, protect against fraud, and debug API issues. Retained for up to 90 days.
  • Session, checkpoint & template content: whatever you send into a session and choose to checkpoint or publish as a template — see Section 2.

Legal basis for processing (relevant if you are in the EEA/UK): account and billing data is processed to perform our contract with you (GDPR Article 6(1)(b)); security and abuse-detection logs are processed under our legitimate interest in keeping the Service safe and available (Article 6(1)(f)); anything else requiring consent is only processed with it. We do not use personal data for automated decision-making that produces legal or similarly significant effects.

4. Data Residency

The infrastructure that runs your sessions — compute, control-plane database, and object storage for checkpoints and templates — runs on EU infrastructure we operate at Scaleway, in the European Union (currently Paris, France). That infrastructure is EU-owned, operated by an EU company with no US parent, and outside the reach of the US CLOUD Act.

Transactional email (sign-in codes, team invitations, account notices) is sent through Scaleway’s EU transactional-email service, region fr-par. The software has no non-EU email provider to fall back to.

Payment processing (Stripe) is different: we have not yet confirmed the exact data-processing location for our account, so we do not claim it is EU-only until we have. See the sub-processor list for the specifics on both, and for GitHub/Google — if you choose to sign in with one of those instead of email, your account ID and verified email necessarily pass through that provider’s own infrastructure (not ours, and not EU-pinned) as part of using their sign-in button. That is inherent to offering third-party sign-in and is a separate thing from our own hosting choices.

5. GDPR & Your Rights

Under the General Data Protection Regulation, you have the right to:

  • Access the personal data we hold about you.
  • Request rectification of inaccurate data.
  • Request erasure of your personal data (“right to be forgotten”), subject to what we must retain for legal, tax, or dispute-resolution purposes.
  • Restrict or object to processing of your data.
  • Receive your data in a portable format, where the GDPR gives you that right.
  • Withdraw consent at any time, for any processing that relies on it.
  • Lodge a complaint with your local supervisory authority — for us, that is the Irish Data Protection Commission (dataprotection.ie).

To exercise any of these rights, contact us at privacy@inis.run. We will respond within one month, as required by the GDPR.

If personal data is processed inside your own sessions (your end users’ data, for example), we generally cannot act on a rights request about it ourselves — we don’t inspect session content, so you, as the controller of that data, are best placed to locate and respond to it. Where a request needs action on infrastructure we control (deleting a specific session, checkpoint, or template), we will assist. See the Data Processing Agreement for how this works when we act as a processor on your behalf.

6. Sub-Processors

We keep the number of third parties who touch your data small on purpose:

  • Scaleway — compute, control-plane database, object storage, and (as of August 2026) transactional email. EU (Paris, France).
  • Stripe — payment processing. Card details never reach our servers. Exact data-processing location for our account not yet confirmed — see Section 4.
  • GitHub — optional OAuth sign-in, if you choose “Continue with GitHub” instead of email. Receives your GitHub account ID and the verified email address on your GitHub account; we store only those two fields, not your broader GitHub profile.
  • Google — optional OAuth sign-in, if you choose “Continue with Google” instead of email. Receives your Google account ID and verified email address; we store only those two fields, not the rest of your Google profile.
  • Cloudflare — DNS for our domains, DNS-only (not proxied, no traffic visibility) for everything except our public status page (status.inis.run), which is proxied through Cloudflare purely for TLS termination. That page is static and public; no personal data or session/application traffic passes through it.

The full sub-processor list, with the specifics of what each one does and does not see, is at inis.run/security/subprocessors. We do not sell personal data, and we do not use an analytics, advertising, or CRM broker — all operational metrics and logs are self-hosted on our own infrastructure.

Our current Data Processing Agreement draft is at inis.run/security/dpa — the facts on that page are accurate today; a few business terms are still marked as pending legal review. Want a signed DPA now? Email legal@inis.run and we will work through it with you directly. 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.

7. Data Retention & Deletion

  • Session data: destroyed on session end, timeout, or expiry, unless you explicitly checkpointed it.
  • Checkpoints & templates: retained until you delete them, or your account is closed. There is no automatic expiry — deletion is always something you or the account-closure sweep does explicitly.
  • Account data: retained while your account is active. You can close your account yourself from Console settings, once you’re its only remaining member — no need to email us. Closing starts a grace period of at least 7 days during which you can cancel; once it passes, an automated sweep permanently erases your personal data and account identity, along with any remaining checkpoints, templates, and artifacts, within 30 days of your request — except what we must retain to meet legal, tax, or accounting obligations, to resolve an open dispute, or the usage-metering and security/audit records described below.
  • Usage metering & security/audit logs: these are our own records of operating the Service, not customer content, so they sit outside the 30-day account-closure commitment above. Security & network logs are retained for up to 90 days; usage metering data (session duration, resource size, request rates) is retained for as long as we need it to meter usage and keep the Service secure.
  • Billing records: retained for as long as applicable tax and accounting law requires.

8. International Transfers

The infrastructure that runs your sessions does not, by design, transfer session data outside the EU. Where a sub-processor’s own processing involves a transfer outside the EEA/UK — see Section 4’s note on Stripe and transactional email — we rely on an appropriate GDPR Article 46 transfer mechanism, such as Standard Contractual Clauses, once that transfer is confirmed. We will not assert SCCs are in place for a transfer we have not confirmed exists.

9. Breach Notification

If we become aware of a personal data breach affecting your account information, we will notify the Irish Data Protection Commission within the timeframe the GDPR requires, and notify affected customers without undue delay. If the breach involves data you hold as controller inside your own sessions, we will notify you as the controller so you can meet your own obligations — see the Data Processing Agreement.

10. Cookies & Tracking

inis.run does not use advertising, marketing, or behavioral tracking cookies.

We only use essential, first-party technical cookies necessary to keep you securely signed in to your account. Because we do not perform tracking or run third-party analytics scripts, we do not require, and do not show, a cookie consent banner.

11. Changes to This Policy

We may update this policy as the Service evolves, and will post each revision here with an updated “Last updated” date. For a material change — a new category of data collected, a new purpose for processing, or a change to retention or residency commitments — we will notify you by email or in-product notice before the change takes effect.

Questions? Reach out to privacy@inis.run.