Privacy Policy
What information Battleship collects, why it is needed to run your GitHub Actions jobs, who it is shared with and the choices you have.
Last updated: 18 November 2026
About this policy
This Privacy Policy explains how we collect, use and share information when you visit thebattleship.dev (the "Website") or use Battleship, the service that runs your GitHub Actions jobs on dedicated machines, and its dashboard (together, the "Services").
"We", "us" and "the Company" mean Xava DAO and its affiliates, as in our Terms of Service. This policy forms part of those terms. By using the Services you agree to it.
This policy covers the service we operate. If you run the software yourself on your own installation, the operator of that installation decides how its data is handled.
What information we collect
We collect the information needed to sign you in, route your jobs to a machine and run them.
| Information | What it covers |
|---|---|
| Account | Your email address. You sign in with a code or a link that we send to it. There are no passwords. A name, if you or an administrator of your organisation provides one. |
| Organisations and members | The organisations you create or join, their names, each member's role, pending invitations and the email addresses they were sent to. |
| Sign-in and sessions | Records of sign-in attempts and active sessions. Sign-in codes, links, invitations and session identifiers are stored only as keyed digests. The network address of a request is used to limit repeated sign-in attempts. |
| GitHub App installation | The GitHub organisation or account where the App is installed, the installation's identifier and the repositories you selected for it. |
| Repository and workflow metadata | What GitHub sends us about a job so that we can route it: the repository, the workflow and job names and identifiers, the labels and runner group the job asked for, and whether it is queued, running or complete. |
| Job data on the machines | While a job runs, its machine handles whatever the job handles: your source code, the job's output and log stream, the files it produces and the secrets GitHub passes to that job. GitHub keeps your workflows, secrets, checks and job logs. |
| Build caches | Dependencies, build outputs and workspace history that your jobs store to make later jobs faster. These stay on your machines and, if you have two or more machines, in the cache they share. |
| Machine inventory | For the machines that run your jobs: the machine's name, processor, memory, graphics hardware, operating system, network address, status and the organisation it belongs to. |
| Activity records | An audit log of administrative actions in your organisation, such as who invited a member or changed a setting, and records of which jobs ran on which machine. |
| Billing | Payment is not yet taken on the Website. When billing exists we will collect the details needed to invoice and charge you, such as a billing name, address and payment method, and we will update this policy first. |
| Messages | Your email address and the content of anything you send when you contact us. |
We do not ask for, and the Services do not need, special categories of personal information. Please do not put any in organisation names, labels or other fields.
How we count page views
We count visits to the public pages of the Website ourselves. The pages load no third-party script and set no cookie. There are no advertising cookies and no advertising trackers.
When a public page loads, our server sends one record to a product analytics tool. The record holds:
- the path of the page and the host name it was served from;
- the host name of the site that referred you, if there was one;
- the campaign tags
utm_source,utm_mediumandutm_campaign, if the link you followed carried them; - a country code;
- a visitor identifier, described below.
The record never holds the full address of the page, your network address or your browser's user agent.
The visitor identifier is a short one-way hash. It is calculated from your network address, your browser's user agent, the host name and a secret value that changes every day (UTC). Only the hash is sent. Because the secret value changes daily, the identifier is different each day. It cannot be turned back into your network address, and identifiers from different days cannot be linked without our key. The analytics tool keeps each identifier as an anonymous visitor that cannot be contacted.
We also count three actions on the public pages in the same way: selecting one of the main buttons (sign in, see the fleet, choose a ship), copying the set-up prompt and replaying the race animation. Only the name of the action and the page it happened on are recorded.
Nothing is counted if your browser sends a Global Privacy Control or Do Not Track signal. Crawlers and page prefetches are not counted either. The dashboard is not covered by this counting.
Cookies
The public pages of the Website set no cookies.
The dashboard sets one cookie when you sign in. It keeps you signed in, lasts up to eight hours, cannot be read by scripts on the page and is sent only to the dashboard. It is necessary for the dashboard to work. We do not use it for advertising or to follow you on other sites.
How we use information
We use the information described above to:
- sign you in and keep your account and organisation secure;
- receive job events from GitHub, check that a job is allowed to use your machines, start a runner for it and remove the runner afterwards;
- run your jobs and keep the caches you asked for;
- show you your machines, jobs and members in the dashboard;
- send sign-in codes, invitations and notices about the Services or changes to our terms and policies;
- answer your questions and provide support;
- understand in aggregate how the Website is used and improve the Services;
- invoice and charge you, once billing exists;
- prevent abuse and fraud, keep audit records and comply with the law;
- protect our rights and enforce our Terms of Service.
We do not read your source code, job output or caches except where that is needed to run the Services, to fix a problem you have asked us to look at, to investigate a suspected breach of our terms or to comply with the law. We do not sell your information and we do not use it for advertising.
If we ever send marketing email, each message will include a way to unsubscribe.
Who we share information with
We do not rent or sell your information. We share it only as described here.
We use these service providers to run the Services:
| Provider | What it does for us |
|---|---|
| Cloudflare | Cloud and edge provider. Serves the Website and the dashboard and carries requests to the Services. |
| GitHub | Sends us job events through the GitHub App you install and receives the results of your jobs. Your use of GitHub is under your own agreement with GitHub. |
| A dedicated server provider | Supplies the rented machines that run your jobs, in France, Germany, Canada and US East. |
| An email delivery provider | Delivers sign-in codes and invitations to your email address. |
| A product analytics tool | Receives the cookieless page-view records described above. |
We may also share information:
- with other members of your organisation, who can see its members, machines and jobs according to their role;
- with our affiliates, where needed to provide the Services;
- with an actual or potential buyer, successor or assignee as part of a merger, sale, reorganisation or other transfer of all or part of our business, including in insolvency proceedings;
- where the law requires it, or where we believe in good faith that it is needed to comply with legal process, to answer a request from a public authority, to enforce our terms, or to protect our operations, rights, safety or property or those of others.
We may use and disclose aggregate information that does not identify any person.
We are not responsible for how third parties handle information that you give to them directly. Please read their own privacy policies.
Where information is processed
Rented machines are located in France, Germany, Canada and US East. Our cloud and edge provider operates in many countries, and our other providers may process information outside your own country.
Your information may therefore be stored and processed in countries whose data protection rules differ from those of the country you live in. By using the Services you agree to this. We do not promise that information will stay in any one country or region.
How we protect information
No transmission over the internet and no system is completely secure, and we cannot guarantee the security of information you send to us. We use technical and organisational measures intended to protect it. For example:
- there are no passwords, and sign-in codes, links, invitations and session identifiers are stored only as keyed digests;
- each job runs in a new virtual machine made from an image that contains no credentials, and that virtual machine is deleted when the job ends;
- the GitHub App's private key and other long-lived credentials stay on our controller and never enter a job's virtual machine;
- requests from GitHub are verified before anything is started.
The permissions guide describes what the GitHub App can do and what reaches a job's virtual machine.
You are responsible for keeping access to your email account and your dashboard session safe, for choosing which repositories and workflows may use your machines, and for the code your jobs run.
How long we keep information
We keep information for as long as it is needed to provide the Services, and for as long as needed afterwards to meet legal obligations, resolve disputes and enforce our terms. We have not set fixed retention periods for every kind of information. In general:
- account, organisation and member records are kept while the account or organisation exists;
- sign-in codes and links expire after 10 minutes, invitations after 7 days and sessions after 8 hours;
- a job's virtual machine and its disk are deleted when the job ends;
- build caches are kept until they are replaced, removed to stay within the limit you set, or deleted when the cache or the machine is no longer in use;
- job and audit records are kept while they are useful for operating, supporting and securing the Services.
You can ask us to delete information about you using the contact details below. Some records may be kept where the law requires or allows it.
Your choices and rights
You can decline to give us information, but we may then be unable to provide some or all of the Services.
- To stop page-view counting, turn on Global Privacy Control or Do Not Track in your browser.
- To stop us receiving job events for a repository, remove it from the GitHub App installation or uninstall the App. The permissions guide explains how.
- To leave an organisation, ask one of its administrators to remove you.
Depending on where you live, the law may give you rights to see, correct, delete, restrict or receive a copy of the personal information we hold about you, or to object to how we use it. To make a request, contact us using the details below. We will respond as the law that applies to you requires. We may need to confirm your identity first.
If your account belongs to an organisation, such as your employer, we may refer requests about that organisation's information to its administrators.
No use by minors
The Services are not directed to anyone under the age of eighteen (18). Please do not use them or give us personal information if you are under 18.
Changes to this policy
We may change this policy. The date at the end of this page shows when it was last revised. If we make material changes we may tell you through the Services or by email. The current version is always on the Website. By continuing to use the Services after a revision takes effect, you agree to the revised policy.
Contact us
If you have questions about this policy, or want to make a request about your information, contact us at legalnotices@xavadao.com.