RunsOn Privacy Notice

Effective date: June 5, 2026

1. Who We Are

RunsOn is sold by Cyril Rohr EIRL in France.

VAT: FR15751044132
SIRET: 75104413200031
Registered address: 4 rue Michel Gérard, 35235 Thorigné-Fouillard, France
Privacy contact: ops@runs-on.com

2. Product Model

RunsOn is self-hosted software. Customers install and operate RunsOn in their own infrastructure, typically in their own AWS account.

Customer controls its own repositories, workflow configuration, runners, cloud accounts, logs, caches, artifacts, secrets, and network environment. RunsOn is not a shared hosted CI/CD service for customer workflow execution.

3. Data RunsOn May Process

RunsOn-side systems may process:

account, billing, checkout, invoice, subscription, license, and customer contact data;
free-license registration data;
license validation data, including a license identifier, organization, product version, deployment region, and validation result;
minimal operational diagnostics describing the RunsOn deployment, such as a deployment identifier, product version, platform, region, and high-level configuration of the install;
approximate request geolocation associated with diagnostics traffic, derived from network-edge metadata;
support, procurement, onboarding, and ordinary business communications;
website analytics and marketing data, where enabled;
optional advertising measurement data when a website visitor consents, including click identifiers used to attribute trials and purchases to a referring ad, landing page metadata, conversion event metadata, and consent status;
payment data handled by our billing providers.

Minimal operational diagnostics and license validation do not include repository contents, customer secrets, workflow logs, runner filesystem contents, or build artifacts.

RunsOn does not collect automatic crash reports, perform automatic update checks from customer deployments, or upload support bundles automatically. Customers may choose to send logs, screenshots, configuration snippets, or other support materials to RunsOn. An upload mechanism for support materials may be offered in the future.

4. License Checks and Minimal Diagnostics

Standard RunsOn deployments perform two outbound calls to runs-on.com:

license validation, which confirms the deployment is entitled to run the installed product version;
minimal operational diagnostics, which describe the deployment at a high level.

Diagnostics are used to understand product usage, administer licensing and usage limits, and improve compatibility, performance, and reliability.

License validation and minimal diagnostics are part of the standard product and cannot be disabled through configuration. Customers that need offline, no-diagnostics, or restricted-diagnostics builds should contact ops@runs-on.com before purchase. Different license-validation arrangements (for example, AWS Marketplace deployments or other written agreements) require custom terms.

5. Customer-Controlled Data

Customer is responsible for the data processed inside its own infrastructure, including repository contents, CI/CD workflows, logs, caches, artifacts, secrets, runner instances, cloud resources, and access controls.

RunsOn sees customer-controlled data only when Customer shares it — for example, in a support email, shared log, screenshot, call, procurement process, or authorized troubleshooting session.

6. Support Access

RunsOn does not have remote access to Customer infrastructure. Any support access must be explicitly initiated or authorized by Customer.

Materials Customer sends for support purposes — logs, screenshots, configuration files, support bundles, and similar — may contain personal data or confidential information. Customer should remove secrets and unnecessary personal data before sending them.

RunsOn keeps customer-provided support materials for ninety (90) days after the support case closes, and no longer than twelve (12) months, unless a longer period is needed for legal, security, abuse-prevention, or dispute-resolution reasons.

7. Legal Roles Under GDPR

Cyril Rohr EIRL acts as an independent data controller for RunsOn-side license validation, minimal diagnostics, billing, account, website, marketing, and ordinary support data.

RunsOn has no role by default for Customer CI data that remains in Customer infrastructure, including repository contents, workflow logs, artifacts, secrets, runner instances, and cloud resources.

For ordinary support where Customer emails logs, screenshots, or configuration to debug RunsOn, RunsOn treats itself as an independent controller for that support case data.

RunsOn may act as a processor only for customer-provided support materials containing personal data controlled by Customer. Processor terms or a data processing agreement apply only where expressly agreed or legally required for that support material.

8. Why We Process Data

RunsOn may process data for the following purposes and legal bases:

license validation: contract and legitimate interests;
minimal operational diagnostics, including usage data needed to administer License Plans and Usage Limits: contract and legitimate interests;
billing and accounting: legal obligation and contract;
account administration, renewals, and product support: contract and legitimate interests;
support, security, procurement, and legal requests: contract and legitimate interests;
optional marketing or newsletter communications: consent or a separate B2B marketing basis, depending on the context;
optional website analytics and advertising measurement: consent;
fraud prevention, abuse prevention, and legal compliance: legitimate interests and legal obligation.

9. Sharing

RunsOn uses service providers for website hosting, API hosting, diagnostics forwarding, billing, payments, email, support, analytics, and related business operations.

Current vendors include Cloudflare, Hetzner, Stripe, Lemon Squeezy, Ahrefs, Google Ads / Google, Fastmail, Slack, and GitHub. RunsOn maintains a service-provider and subprocessor list.

Website analytics and advertising measurement run only after the visitor consents. When a visitor consents and arrives through an ad, RunsOn may store an ad click identifier in a first-party cookie and carry it through checkout so that trial or paid conversions can later be attributed to the referring ad.

10. Cookies and Local Storage

RunsOn stores the visitor's consent choice on the website. If the visitor consents to analytics and ads measurement, RunsOn may additionally set a first-party attribution cookie that records how the visitor arrived (ad click identifier, landing page, timestamp, and consent marker). Declining optional tracking prevents this attribution cookie from being stored and removes any existing one.

You can review or change your choice at any time:

11. Retention

RunsOn keeps data as long as needed for product operation, billing, tax, accounting, support, security, legal compliance, dispute resolution, and legitimate business purposes.

Current retention targets:

minimal operational diagnostics: twelve (12) months;
license validation logs: twelve (12) months;
customer-provided support materials: ninety (90) days after support case closure, and no longer than twelve (12) months unless needed for legal, security, abuse-prevention, or dispute-resolution reasons;
first-party advertising attribution cookies: up to ninety (90) days;
billing and accounting records: up to ten (10) years;
other account and support records: only as long as needed for the relevant business, legal, security, or support purpose.

12. International Transfers

RunsOn is based in France, but service providers and customers may be located outside France or the European Economic Area.

RunsOn uses EU/EEA providers where practical. For non-EEA providers, RunsOn relies on adequacy decisions, standard contractual clauses, the EU-U.S. Data Privacy Framework where applicable, or another valid transfer mechanism.

13. Your Rights

Depending on applicable law, individuals may have rights to access, correct, delete, restrict, object to, or port personal data.

To make a privacy request, contact ops@runs-on.com. Where GDPR applies, RunsOn will respond within one (1) month unless an extension is legally available.

For data that remains in Customer infrastructure, RunsOn will route the request back to Customer unless RunsOn is processing that data as a processor for support.

14. Security

The primary security boundary is architectural: RunsOn runs in Customer infrastructure, and Customer controls the workflow execution environment, secrets, and access controls.

For RunsOn-side systems, we apply technical and organizational measures appropriate to a self-hosted software business. Further detail is available in our security notice.

15. Changes

RunsOn may update this notice over time. The effective date should be updated when material changes are made.