Skip to content
Menu
What Sengi keeps

Security

What Sengi keeps and doesn't keep about your code

Sengi does not store your job logs: they stay in GitHub. Every job runs in a fresh virtual machine that is destroyed when the job ends, and nothing written to its disk is kept except the build caches your workflow saves, which are deleted after seven days without use. What Sengi does keep includes your GitHub sign-in identity and email, your billing details, a record of each job (repository, commit, branch, labels, timing and result), GitHub's event deliveries and our own logs for 30 days, and masked recordings of our public and sign-up pages for 30 days.

Last checked November 19, 2026, against our privacy policy and the code that runs Sengi.

What stays in GitHub

  • Your job logs. Sengi links to them in GitHub and does not copy them.
  • Your secrets. Repository secrets, environment variables and workflow outputs stay in GitHub. GitHub passes the secrets a job uses to that job's machine while it runs; Sengi does not store them.
  • Your GitHub tokens. Sengi does not store your GitHub sign-in token or the App's installation access tokens.
  • Your card number. Card details go to our payment processor, Stripe, and never reach Sengi.

What happens on the job's machine

  • Each job gets its own fresh virtual machine with its own CPU and memory limits. It runs one job and is destroyed when the job ends. No machine runs a second job, yours or anyone else's.
  • Each machine registers with GitHub as a one-time runner that runs a single job.
  • The machine's disk is encrypted and is never backed up. Whatever the job writes there, including your checked-out code and build output, is gone when the machine is destroyed.

You can check this yourself: the runner name in the "Set up job" step of each job's log in GitHub is different for every job.

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 it so later jobs in the same repository can restore it. Caches are kept per repository in Cloudflare R2, and runner hosts keep a local copy for faster restores.

  • An entry no job has read for seven days is deleted.
  • When a repository reaches its cache storage limit, the least recently used entries are deleted first.
  • A cache holds whatever your workflow puts in it, so keep secrets out of cache paths.

What Sengi keeps, and for how long

WhatHow long
Your GitHub user ID, the profile GitHub returns and your verified primary emailWhile your account exists
Your projects, their members and permissions, the Sengi GitHub App installation and the repositories you approveWhile your account exists
Job records: repository, run and attempt IDs, commit, branch, pull request numbers, labels, start and end times, result, runner size and image, metered minutes and amountsWhile your account exists
Job and workflow names and each step's name, times and result90 days after the job finishes, for a job that ran on a Sengi machine; while your account exists, for a job that never got one
Each job's workflow file path and commit. Sengi reads the file and does not keep itWhile your account exists
Billing details, the payment processor's customer record, your payment methods as the processor describes them, and invoicesWhile your account exists
Sign-in and other security events on your accountWith your account records
GitHub's event deliveries (the webhook payloads GitHub sends us about your jobs and installation)30 days after processing; while your account exists, for deliveries about a job that never got a Sengi machine
GitHub's notices that you revoked Sengi's GitHub authorizationWith your account records
Our application and system logs30 days
Web server access logs: each request's path without its query string, its status and the requesting IP address30 days
Where you first came from: referring site, landing page, campaign tags and, if you came from one of our ads, the ad click identifierCopied to your account at signup; the cookie expires after 90 days if you do not sign up
Recordings of sengi.run and our sign-up, sign-in and first GitHub connection pages (pointer movement, clicks and scrolling), with every form field and all page text hidden30 days
Encrypted backups of our database90 days, on a rolling schedule

Account, job and billing records stay while your account exists, because they are how we explain a charge and avoid billing one job twice. The page recordings never include your email, name, repository names, logs or tokens, and they are not made on account, billing, repository, token or runner pages. Full details are in our privacy policy.

Who at Sengi can see what

  • Access to production systems is limited to Sengi's owners.
  • The operator console answers only on our control server and refuses requests from the internet.
  • We read a project's records in the console to answer a support request or investigate an incident.
  • We do not sell your data, use it to train models, or use it to show you advertising.

Where your data is

Our primary records are stored on machines in Helsinki, Finland, and our encrypted database backups in Cloudflare R2. Jobs run on machines in Finland, Germany and Canada, and on overflow machines in Sweden when ours are full.

Security practices in place

  • A fresh, encrypted, single-use virtual machine for every job.
  • Nightly database backups, encrypted with AES-256 before they leave our server and kept off-site.
  • The credentials Sengi uses to run the service are kept out of its source code, in files only the server's administrator can read.
  • Adopted security policies for information security, change management, vendor management and acceptable use, with a risk assessment and checklists for access reviews and offboarding.
  • Written procedures for rotating our credentials.

Report a vulnerability to ops@sengi.run rather than in a public issue. More on isolation is in Security.

Frequently asked questions

Does Sengi store my GitHub Actions logs?

No. Job logs stay in GitHub, and Sengi links to them there. Sengi keeps a record of each job, such as the repository, commit, branch, labels, timing and result, for billing and your job history, but not the log output.

Can Sengi see my source code?

Yes. The Sengi GitHub App can read the contents of the repositories you connect, and Sengi uses that to read the workflow file of each job it runs. It keeps the file's path and commit, not the file. Your code is checked out only inside the job's own virtual machine, which is destroyed when the job ends.

Does Sengi store my repository secrets?

No. Secrets stay in GitHub. GitHub passes the ones a job uses to that job's machine while it runs, and the machine is destroyed afterwards.

Is a runner machine ever reused for another job?

No. Each job gets a fresh virtual machine that runs one job and is then destroyed. The runner name in the Set up job step of each job's log in GitHub is different for every job.

How long does Sengi keep build caches?

A cache entry no job has read for seven days is deleted. When a repository reaches its cache storage limit, the least recently used entries are deleted first.

Who at Sengi can see my data?

Access to production systems is limited to Sengi's owners. We read a project's records to answer a support request or investigate an incident, and we do not sell your data or use it to train models.

How do I get a copy of my data or have it deleted?

Email 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.