Privacy Policy

1. How We Handle Your Data

CarbonRunner does not collect personal information directly. We rely on trusted third-party services — specifically Clerk for authentication and GitHub for source control integration. Any personal data we receive (e.g. name, email, username) is accessed through these services and governed by their respective privacy policies.

2. Authentication

Users log in to CarbonRunner using their GitHub account via Clerk. Clerk manages the authentication process and provides us with basic user information to create and manage your session.

3. What We See

Based on what Clerk and GitHub provide, we may have access to your GitHub username, email address, and public profile details. We do not access your repositories or perform any actions on your behalf beyond what is necessary to deliver our services.

4. How We Use Your Data

We use data strictly to provide, maintain, and improve our services. This may include displaying relevant info in your dashboard, associating activity with your account, or offering support.

5. Cookies

We may use cookies and session storage for essential functionality and anonymous usage metrics. You can manage cookie preferences via your browser settings.

6. Your Rights

You may request to access, update, or delete the data we receive via Clerk or GitHub. However, we recommend managing your data directly through those platforms.

6. Security

What is the patching schedule like for the runners?

An automated nightly build of all base images is created, including all of the latest security updates for the Operating System.

GitHub Runners are updated within 24 hours of a release to allow time for testing the new version before deployment.

What is being logged or captured on the runners?

We only send logs from runinit, a lightweight program started at boot to connect CarbonRunner to GitHub/GitLab and other services. This log is sent via secure Syslog over TLS.

The data logged includes your GitHub organization or username, repository name, CPU frequency settings, and network byte counters (Rx + Tx). We do not log any other data.

Are there any prepackaged tools on the runners and how often are they updated?

Yes. If you choose the standard CarbonRunner ubuntu-latest image, it includes the same packages and tooling as GitHub’s default runners. These are updated in sync with nightly image builds.

What controls are available for specifying regions?

CarbonRunner allows you to restrict runner deployment by region. GitHub Runners are typically installed at the Organization level, meaning your workflows can run in any region CarbonRunner supports.

You can restrict regions and cloud providers in your CarbonRunner Dashboard. This gives you control over where workflows are executed without requiring changes to the runs-on tag after initial setup.

8. Contact

Questions? Email us at hello@carbonrunner.io.