Data processing agreement

How Sailfork handles personal data on behalf of the teams and organizations that use it, written to meet GDPR Article 28, the UK GDPR and the CCPA.

Last updated

Your role
Controller
Our role
Processor
Breach notice
Within 72 hours
New subprocessors
30 days notice

The agreement

This agreement is part of the terms of service and applies automatically to every organization and account that puts personal data on Sailfork. There is nothing to sign.

If your team needs a signed copy for its records, ask through the contact page with your organization name and the legal name of your company, and we send back a countersigned PDF of this page.

Where this agreement and the terms of service disagree about personal data, this agreement wins.

Roles

You, the customer, decide why and how personal data in your repositories, issues, pull requests, CI runs and organization settings is processed. You are the controller, or a processor acting for your own client.

Sailfork processes that data only to run the service for you. We are your processor, or your subprocessor when you are a processor yourself.

For the data we need to run accounts, such as sign-in records, billing and security logs, Sailfork is its own controller, and the privacy policy covers it.

What we process

Details of processing
ItemDetail
Subject matterHosting git repositories and the work around them: pull requests, reviews, issues, comments, attachments, CI runs and sandboxes.
DurationFor as long as you use Sailfork, then until deletion finishes as described below.
PurposeStoring, serving and showing your content to the people you share it with, and running the jobs you set up.
Data subjectsYour members, collaborators, and anyone whose personal data appears in your content, such as commit authors.
Personal dataNames, handles, email addresses, commit metadata, and any personal data you put in code, issues, comments, files or logs.
Special categoriesNone expected. Do not put them in your content unless you have a lawful basis to do so.

Your instructions

We process personal data only on your documented instructions. The terms of service, this agreement, and the settings and actions you take in Sailfork are those instructions.

If we believe an instruction breaks data protection law, we tell you and do not follow it until you confirm or change it. If the law makes us process data in another way, we tell you first unless the law forbids it.

Confidentiality

Anyone at Sailfork who can reach personal data is bound to keep it confidential and reaches it only when running, supporting or securing the service needs it.

Security measures

Every connection to Sailfork uses TLS. Passwords are hashed, API tokens are stored only as hashes, and GitHub tokens and other secrets are encrypted at rest.

Accounts can require two-factor authentication and passkeys. Organizations control who reaches each repository, and an audit log records changes to access for 2 years.

Production access is limited to the people who run Sailfork, behind two-factor authentication. Database backups let us restore the service after a failure.

Our security page describes these measures in more depth, and the security disclosure page explains how to report a vulnerability.

Subprocessors

You authorize us to use the subprocessors on the Subprocessors page. Each one is bound by a written agreement that protects personal data at least as well as this one, and we stay responsible to you for their work.

Before a new subprocessor starts handling personal data, we email the owners of every organization at least 30 days ahead. You can object in that time on reasonable data protection grounds. We then try to find a way to avoid the new provider for you, and if we cannot, you can end your paid plan and get a refund of fees paid for the time after it ends.

International transfers

Sailfork stores and processes data in the United States. When personal data from the European Economic Area, Switzerland or the United Kingdom reaches us, the EU Standard Contractual Clauses (module two, or module three when you are a processor) and the UK International Data Transfer Addendum apply, and this agreement fills in their annexes.

For the clauses, the governing law and courts are those of Ireland, and the optional docking clause applies. The UK addendum is completed with the same details.

Requests from individuals

Most requests can be handled directly in Sailfork: export, correction and deletion are all in Settings, and organization owners control what their members can see.

If someone sends us a request about personal data you control, we pass it to you instead of answering it ourselves. We help you answer requests and carry out impact assessments and consultations with regulators, as far as our role allows.

Personal data breaches

If a breach affects personal data we process for you, we tell your organization owners by email without undue delay and within 72 hours of confirming it.

The notice says what happened, what data and how many people it affects as far as we know, what we are doing about it, and who to talk to. We send more as we learn it.

Return and deletion

You can export repositories and data at any time while you use Sailfork, with git or from Settings.

When you delete an organization, a repository or your account, we delete the personal data it holds on the schedule in the privacy policy. Copies in backups and in our providers’ logs are removed on their own schedules and are never restored into the service.

Audits

We give you the information you reasonably need to show you meet your obligations, including answers to security questionnaires, through the contact page.

If that is not enough, or a regulator asks, you or an independent auditor you choose can audit us once a year, with 30 days notice, during business hours, under a confidentiality agreement and at your cost.

California

Under the CCPA we are your service provider. We do not sell or share personal data you give us, do not keep, use or disclose it for any purpose other than running the service for you, and do not combine it with personal data from other sources except as the CCPA allows.

Liability and term

The limits of liability in the terms of service apply to this agreement. This agreement lasts as long as we process personal data for you.

We publish every change on this page. For a change that matters to you, we email organization owners before it takes effect, and a change never lowers the protection this agreement gives your data.

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

Loading Sailfork