Privacy policy

What Sailfork collects, why, who else handles it, and how to get it back or delete it.

Last updated

In short

We collect what it takes to run a git host for you, and nothing for advertising. There are no analytics scripts, no tracking cookies and no ad networks on any page, and we do not sell personal data.

What we collect

Account: your handle, name, email addresses and a hash of your password. Anything you add to your profile, such as a picture, bio, location, website, time zone and working hours.

Security: two-factor secrets, passkeys, recovery codes, SSH public keys, hashed API tokens, and a record of security events such as sign-ins and new keys. For each session we keep a short description of the device and when it was last used.

GitHub: when you sign in with GitHub or move repositories from it, your GitHub login and the access tokens GitHub gives us, stored encrypted.

Your content: repositories, pull requests, reviews, issues, comments, attachments, and the logs of CI runs and sandboxes you start.

Messages: what you send through the contact page, with the name and email you give.

Crash reports: when a Sailfork page breaks in your browser, it sends us the error message, the page address without its query string, the app version, your browser's user agent and, if you are signed in, your account. Nothing else from the page, and no cookies beyond the one that says who is signed in.

How we use it

To run the service: sign you in, serve and store your repositories, show your work to the people you share it with, run the jobs you set up, and keep accounts secure.

To reach you: verification and password emails, notifications you have turned on, replies to your messages, and notice of changes to these policies or to billing.

Nothing else. We do not build advertising profiles or train AI models on your private repositories.

Cookies

Sailfork sets only the cookies listed here. None of them track you across sites, and we set no tracking or advertising cookies.

sf_session keeps you signed in for up to 30 days.

sf_github_state, sf_github_pending and sf_github_link are set only while you sign in with GitHub, link a GitHub account, or finish a second-factor check that uses GitHub. They last up to 10 minutes and are cleared when the step finishes.

sf_suspended is set only when a suspended account signs in. It lasts 30 minutes and lets the suspended page show the reason.

sf-panes remembers whether the sidebar and the rail are collapsed. Your browser sets it when you change them, and it lasts one year.

Sailfork does not track you across sites, so there is no tracking to switch off. A Do Not Track signal from your browser changes nothing.

Sailfork sells no personal data and shares none for advertising, so a Global Privacy Control signal has nothing to switch off. When your browser sends it as you sign in, we record that your account opted out of sale and sharing, and nothing about how we handle your data changes.

Who else handles it

Fly.io runs our servers and database in Los Angeles. Tigris stores repository data. Resend sends our email. Cloudflare answers DNS for sailfork.com. Amazon Web Services will run part of our servers alongside Fly.io.

When we verify a custom domain, we send the domain name being checked to the DNS-over-HTTPS resolver that Cloudflare runs, and to Google Public DNS only if Cloudflare does not answer.

GitHub receives requests from us only when you sign in with it or ask us to move or mirror repositories. Depot runs CI jobs only if you connect your own Depot account.

AWS and Hetzner run Drydock overflow jobs only when an organization turns overflow on. Those machines run in an AWS or Hetzner account that the organization owns and connects to Sailfork, and the Sailfork server calls their APIs to start and stop them. Jobs that use sandbox secrets stay on hosts the organization runs itself by default, and the organization can turn that off.

Images embedded in markdown, such as a picture in a README or an issue, load straight from the site that hosts them. That site can see your IP address when your browser fetches the image.

Apart from these providers, we share personal data with anyone else only when the law requires it, and we tell you when we are allowed to.

The full list, with what each provider does and where, is on the Subprocessors page. For content you put on Sailfork for a team or organization, our data processing agreement applies.

What is public

Your handle, name, profile picture and the profile fields you fill in, plus everything in public repositories: code, commit authors and their email addresses as recorded in git, issues, pull requests and comments. Private repositories are visible only to the people you give access.

How long we keep it

Account data and content stay for as long as your account exists. Operational logs are held by our hosting provider for a limited period, under its own retention.

The records that build up as you use Sailfork are deleted on a schedule, whether or not you delete your account. Activity on repositories, which feeds profiles and repository pages, is kept 13 months. Security events on your account, such as sign-ins and new keys, are kept 2 years. An organization's or account's audit log is kept 2 years. Administrator records of actions taken on accounts are kept 7 years.

CI logs are deleted 90 days after the run finishes. A session record is deleted 30 days after the session expires. Messages sent through the contact page are kept 1 year. Browser crash reports are kept 90 days. The commands run in an organization's sandboxes are kept for the period its owners set, or for as long as the organization exists when they set none. Privacy requests, once we have answered them, are kept 2 years with the answer, so we can show when and how we replied.

When a valid legal request tells us to preserve an account, an organization or a repository, we pause these deletions for what it covers until the request ends.

When you delete your account, it is permanently deleted 14 days later, along with your personal repositories and personal data, apart from the records described below. Signing in before then cancels it. Repositories you created in an organization stay with that organization.

Some records outlive the account because other people rely on them. The activity of shared repositories and the CI runs you started stay, but your name is replaced with "Deleted user". Messages you sent through the contact page, from your account or from one of your verified email addresses, are deleted, and so are the name and email on abuse reports you filed once they are resolved.

What still names you: an organization's audit log keeps your handle and what you did there for 2 years, so its owners can see who changed access. Administrator records of actions taken on accounts, yours included, are kept for 7 years as a security record. Abuse reports still open when you delete your account keep the contact details you gave, and copyright notices keep the sender's name and email, so we can follow up and show what was reported.

What stays after deletion

Copies in our database backups and in our email provider’s logs are removed on those providers’ own schedules.

A data export you downloaded before you deleted your account is a copy you hold, and we cannot remove it for you.

Clones and forks that other people made of public repositories are theirs, and we cannot remove them.

Your choices

Correct your details in Settings at any time. Download your account data from Settings: we email you a link to a file of it. Delete your account from Settings, under Account.

Wherever you live, you can ask us what we hold about you, to correct it, or to delete it, through the contact page by choosing Privacy request. We answer within 30 days, and the confirmation you get when you send your request states the date.

Security

Connections use TLS. Passwords are hashed, API tokens are stored only as hashes, and GitHub tokens are encrypted at rest. If a breach affects your data, we tell you without undue delay.

Changes to this policy

We publish every change on this page. For a change that matters to you, we email account holders before it takes effect.

Questions about this page go through the contact page. Fenil, who runs Sailfork, reads every message.

Loading Sailfork