Sengi privacy policy

This policy describes the personal data Clay Cantrell, an individual doing business as Sengi in the United States ("Sengi", "we", "us"), collects when you visit sengi.run, use the Sengi service at app.sengi.run, or write to us, and what we do with it. It applies alongside our service terms at sengi.run/terms; section 5 of those terms covers the same data, and this policy gives the fuller account.

Effective October 27, 2026.

1. What we collect

1.1 Your account. Accounts are created by signing in with GitHub; there is no separate Sengi password. We store your GitHub user ID, the profile GitHub returns, and your verified primary email address.

1.2 Your projects and GitHub connection. The projects you create or are added to, the people in them and their permissions, the Sengi GitHub App installation you connect, and the repositories you approve it for.

1.3 Job records. For each GitHub Actions job Sengi runs: run and attempt IDs, the repository, optional job and workflow titles, status, timestamps, runner size and image, and the metered minutes and amounts.

1.4 Build caches. When a job saves a cache through actions/cache, a setup action's built-in cache or Docker's type=gha layer cache, Sengi stores that cache so later jobs in the same repository can restore it. A cache holds whatever your workflow puts in it.

1.5 Billing. Your billing details, your payment-provider customer record, your payment methods as the payment provider describes them (not the card number), and your invoices.

1.6 Where you first came from. When you arrive at Sengi we record the referring site, the page you landed on, any campaign tags in the link and the time of that first visit, in a first-party cookie. When you create an account those values are copied to your account and the cookie is cleared. No full URL, query string or IP address is kept in this record.

1.7 Server and security logs. Our web servers record each request's path (with any query string removed), its status and the requesting IP address. The application records security events on your account, such as sign-ins.

1.8 What you send us. Email to ops@sengi.run and anything in it.

2. What we do not collect

• Your job logs. Those stay in GitHub, and we link to them there.
• Your repository secrets, environment variables or workflow outputs.
• Your GitHub OAuth token, or GitHub installation access tokens.
• Your card number. Card details go to our payment processor and never to us.
• Anything written to a job's disk outside a cache, which is destroyed with the job's virtual machine and excluded from backups.

3. How we use it

3.1 We use your data to run the service: to sign you in, run your jobs, keep their caches, meter and bill usage, and show you your job history and invoices.

3.2 We also use it to investigate abuse, faults and security incidents, to answer support requests, and to contact you about your account, your billing and changes to our terms or this policy.

3.3 We use first-visit records, in aggregate, to understand how people find Sengi.

3.4 We do not sell your data, we do not use it to train models, and we do not use it to show you advertising.

3.5 We can read your project's records in our operator console to answer a support request or investigate an incident, and those actions are logged.

4. Cookies and analytics

4.1 The signed-in application sets a session cookie to keep you signed in, and the cookies it needs for sign-in security. They are not used for tracking.

4.2 The first-visit cookie in section 1.6 is first-party and expires after 90 days if you do not sign up.

4.3 Public marketing pages use Cloudflare Web Analytics to count visits and measure page performance. It sets no cookies; your browser sends those measurements to Cloudflare. We do not load it on account, sign-in, OAuth callback, operator or legal pages, and the first-visit record in section 1.6 is not sent to it.

4.4 We run no advertising pixels, retargeting tags or session-recording services on our pages.

4.5 The signed-in application loads pinned, integrity-checked JavaScript and stylesheets from the jsDelivr CDN, so your browser's request reaches jsDelivr when you use it.

5. Who we share it with

We share personal data only with the providers below, as needed to run the service, and with authorities where the law requires it.

We will update this list before personal data reaches another provider. If the business passes to a successor, your data goes with it under this policy.

6. Google API data

6.1 Sengi uses the Google Ads API and the Google Search Console API only with Sengi's own Google Ads and Search Console accounts, for internal reporting on and management of Sengi's own advertising campaigns and website.

6.2 We do not ask customers or visitors to sign in with Google, and we do not collect, store or share Google user data from customers or visitors.

6.3 Data we receive from these APIs is used only for that reporting and campaign management. We do not sell it, use it for advertising to individuals, use it to train models, or transfer it to anyone except as the law requires.

6.4 Sengi's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

7. How long we keep it

7.1 Account, project, job, usage and billing records are kept while your account exists and are not deleted automatically, because they are how we explain a charge to you and avoid billing you twice for one job. Disconnecting a repository or uninstalling the App does not erase job history.

7.2 Optional job and workflow titles may expire after 90 days without new activity, and eligible processed delivery details after 30 days. An unresolved incident or an unpaid charge can keep a record longer.

7.3 A cache entry that no job has read for seven days is removed, and when a repository's cache reaches its storage limit the oldest entries are removed first.

7.4 Web server access logs are kept for 30 days.

7.5 Encrypted database backups are kept for disaster recovery and expire on a rolling schedule; a record deleted from the database leaves the backups as they expire.

8. Your choices

8.1 Write to ops@sengi.run for a copy of your data, to correct it, or to ask us to delete what we are not required to keep. We may need to confirm the request comes from the account holder.

8.2 You can revoke Sengi's GitHub authorisation or uninstall the App at any time; we then stop being able to act on your repositories.

8.3 You can block or clear cookies in your browser. Blocking the first-visit cookie does not affect the service; blocking session cookies prevents signing in.

8.4 Depending on where you live, you may have further rights over your data, such as to object to or restrict how we use it, or to complain to a data protection authority. Write to us and we will respond under the law that applies to you.

9. Security

9.1 Each job runs in its own virtual machine with an encrypted disk, destroyed when the job ends. Access to our hosts and operator console is restricted to the operator, and operator actions on customer records are logged.

9.2 We have no security certification or completed third-party audit. If we learn of a breach affecting your personal data, we will tell you as the law requires and as described in section 6.5 of our service terms.

10. Where your data is processed

Our records are stored on machines in Helsinki, Finland. Sengi is operated from the United States, and the providers in section 5 may process data in other countries.

11. Children

Sengi is a service for software developers and organizations and is not directed at children. If you believe a child has given us personal data, write to us and we will delete it.

12. Changes to this policy

We will publish any change at sengi.run/privacy with its effective date. For a material change we will also give notice as described in section 13.5 of our service terms before it takes effect.

13. Contact