Your data

Privacy and cookies

This page describes what Tether Game actually records when you visit the site, create an account, sign in, download the game or send a report. It is limited to what the code does today.

Who is responsible?

Jean-Marie Clouet, sole proprietor (micro-enterprise, SIREN 898 244 959), 32 rue du Maréchal Leclerc, 59147 Gondecourt, France, publishes tether-game.com and is responsible for the data described on this page.

For any question or request about your data, write to contact@tether-game.com. The publisher’s and host’s details are also in the legal notice.

Visiting the site

The presentation pages (home, what’s new, report, contact, credits, privacy) set no cookies. They load no font, script or image from another site, and contain no audience measurement and no trackers.

The cookies we use

When you sign in to your account, a cookie is set. It is strictly necessary: without it, the site could not tell that you are signed in. Signing in with Google or Steam adds another, very short-lived one. No other cookie is set, and nothing is written to your browser’s local storage.

  • __Host-tether_session: keeps you signed in. Page scripts cannot read it (HttpOnly), it is only sent over HTTPS (Secure), it is not sent by requests coming from another site (SameSite=Lax) and it only applies to tether-game.com. Lifetime: 30 days at most, and it stops after 7 days without activity. Signing out removes it immediately. It holds only a random identifier: the server keeps just its fingerprint.
  • __Host-tether_sso: set only during a sign-in with Google or Steam, to tie the service’s return to the browser that started it. Same protections as above, ten minutes at most, removed as soon as you come back.
  • __Host-tether_sso_pending: set only when Steam gives no e-mail address, to find your pending sign-in again while you give and confirm your address. Page scripts cannot read it (HttpOnly), HTTPS only, not sent by requests coming from another site (SameSite=Lax), 30 minutes at most.
  • No language cookie: the language of the page comes from its address.

No audience measurement, no advertising, no banner

No audience measurement, no trackers, no advertising, and the pages load nothing from another site. One exception only: if you choose “Continue with Google” or “Continue with Steam”, your browser is sent to that service (see below).

Because only strictly necessary cookies are used, no consent banner is shown. If that ever changes, this page will be updated along with it.

What your account records

When you create an account, the server keeps:

  • your e-mail address and, if you choose one, your username;
  • your password as a fingerprint (Argon2id): the password itself is never kept;
  • your account status (pending, approved or declined), the reason for a refusal if any, and the dates of registration, e-mail confirmation and decision;
  • the devices linked to your account (for example “Lanceur Windows”), with their connection date and last activity. A device is signed out after 90 days without activity, or when you revoke it from “My account”.

What this data is for, and on what ground

The account gives you access to the download and the game. Each account is approved by hand by the publisher: no automated decision is made about you.

The account and what comes with it (signing in, downloading, playing) rely on performing the service you ask for. Manual approval of accounts, security (attempt limiting, access logs) and reports rely on the publisher’s legitimate interest in protecting the service.

How long an account is kept

An account is kept as long as it exists. No automatic deletion of inactive, declined or unconfirmed accounts is in place today.

Retention periods adopted: an account whose address was never confirmed, 7 days; a confirmed account not yet approved, 60 days, with an e-mail notice before deletion; a declined account, 6 months; an approved account left inactive, 3 years.

The matching automatic deletion is being put into service. Until then, you can ask for your account to be deleted at any time by writing to contact@tether-game.com.

What downloading records

Downloading the installer requires an approved account. Each download is recorded on the account: which account, on what date, which version. This record holds no IP address. Anonymous visitors of the download page are not recorded. No retention period is set for this record yet.

During a game

To play, the launcher asks the API for a signed game ticket, valid for 10 minutes. It contains in particular your username and your account identifier: the game host and the relay server can see them.

IP addresses and abuse protection

To slow down repeated sign-in attempts, the server counts failures per IP address and per e-mail address typed, over a 15-minute window. It does not keep these addresses themselves but fingerprints computed with a secret key, removed by a daily purge: they are kept between 15 minutes and 24 hours.

Server access logs

Like any web server, the hosting server notes in its access logs the IP address, date, requested page (with its parameters), browser and status of each request, for security and diagnosis.

These logs rotate by size (10 MB): the last three files are kept, and a file older than 30 days is removed when a rotation happens. This is therefore not a guaranteed period: with little traffic, one file can cover more than 30 days. The log of the service that distributes launcher updates has no age limit, only the size limit.

Bug and idea reports

A report keeps: your text, your username if you give one, the date, the versions, your system (from the launcher) or your browser (from the site), the game logs if you attach them, and a fingerprint of your IP address.

When you send a report from the launcher, it requests a signed report ticket from the API, valid for 10 minutes, and attaches it to the submission, over HTTPS only. The ticket contains your account identifier, your username and a trust indicator. The reports service checks it without querying your account: a trusted account has no limit on submissions, any other is counted per account. Without a ticket (unvalidated account, no username, site unreachable), nothing is attached and the submission is counted by address. The report keeps the trust indicator and a fingerprint of your account, never its identifier; the ticket is not kept. Older launcher versions still attach their device token instead: only its fingerprint then serves, for five minutes, as a cache.

This fingerprint, computed with a key kept alongside the data, is used to slow down repeated submissions. It is not your address in the clear, but it is not anonymous data either: someone with access to the data could recover an address by trying the possibilities. Do not write in a report what you do not wish to entrust to us.

We cannot reply to a report: it carries no contact address. For a question that calls for an answer, use the Contact page.

Reports are kept for 12 months, then deleted automatically. A report can also be deleted earlier on request. Separately, a disk-space ceiling blocks new submissions if the service is full.

To read and sort them, the publisher relies on an artificial intelligence assistant: Claude, from the company Anthropic, used from the publisher’s own computer. The content of a report (text, versions, system or browser, after the filter below) is then sent to Anthropic to be analysed. Before analysis, a filter removes the username and the address fingerprint, replaces the sender with an alias, masks IP addresses, e-mails, identifiers and personal paths, and does not send game logs by default. This filter relies on patterns: the free text itself cannot be filtered reliably (a name written in a sentence may get through): do not put any personal information in it, nor that of another player.

The contact form

The Contact page lets you write to the publisher. The server receives your e-mail address, the chosen subject and your message, and stores none of it: it forwards them at once, by e-mail, to the publisher’s mailbox, with your address as the reply-to, then forgets them. If that forwarding fails, your address, the subject and the message wait on the server, out of reach, and forwarding is retried every hour for at most seven days; after that, they are deleted. This goes through the same provider as the site’s other e-mails, Brevo, which receives your address and the content of the message for that purpose. Your message then lives in the publisher’s mailbox, like any other mail.

As for a report, your IP address is not kept as is: a pseudonymised fingerprint of it is kept to slow repeated submissions, and a short proof of work is asked of your browser instead of a captcha, which would involve a third party. The server’s technical log keeps only the time, the subject and the outcome of the submission: never the text nor the address.

E-mails

The site writes to you to confirm your address, for a forgotten password, to tell you of the decision on your account and of a password change. These messages are sent by a sending provider, Brevo, which receives your address and the content of the message (for example a confirmation link) for that purpose. The site’s sending register keeps only timestamps, no address.

The site also e-mails the publisher about each new account to approve, with its address.

Signing in with Google

If you choose “Continue with Google”, your browser is sent to Google, which identifies you under its own responsibility. We only ask for basic identity and the e-mail address: we receive a Google identifier, your e-mail address and the indication that Google has verified it.

We keep the Google identifier attached to your account (provider, identifier, date). If an account already exists with the same address and Google vouches for it, the Google sign-in is linked to it. An account created this way has no usable password: “Forgot password” gives you one.

Google keeps its own record of the authorisation: to withdraw it, use your Google account settings.

Signing in with Steam

If you choose “Continue with Steam”, your browser is sent to the Steam website (steamcommunity.com), which identifies you under Valve’s responsibility. Our server checks the answer directly with Steam. All we receive from Steam is a public identifier, the SteamID (17 digits): Steam gives us no e-mail address.

Since we need an address to reach you, the next page asks for yours. Meanwhile your sign-in is put on hold: the server keeps the SteamID, the address you typed (in the clear), fingerprints of two tokens (your browser’s and the link’s) and the number of sendings. The __Host-tether_sso_pending cookie, 30 minutes at most, ties your browser to this pending state.

A confirmation link, valid for one hour, is sent to the address you typed, by Brevo. The page answers the same way whether or not the address already has an account. Sendings are limited to 3 per sign-in and 3 per address per hour. Giving another address replaces the previous one: the old link stops working.

Nothing is created until you click the link. The click does not sign you in (it may come from another device): it creates your account, always pending approval by the publisher, or attaches your SteamID to an account that already exists with that address. If that account had never confirmed its address, its password is deleted. An account created this way has no usable password: “Forgot password” gives you one.

We keep the SteamID attached to your account (service, identifier, date). A pending sign-in that is never confirmed is deleted when it expires, by the daily purge.

When you choose Steam, your browser is sent to Valve, which handles your sign-in under its own responsibility and its own privacy policy. Our server queries Steam to verify its answer, without sending it any data about you other than that answer. From Steam we only receive your public Steam identifier.

Who sees your data, and where it is

The site and the accounts database are hosted by OVHcloud, which also hosts the relay server, the logs and the backups. The database is backed up every day; these backups are kept for 14 days on the same server.

Brevo sends the e-mails (see above). Google and Valve (Steam) are involved only if you choose their sign-in.

OVHcloud is a French company. The server that hosts the site, the accounts database, the logs and the backups is located in France (Gravelines): this data stays within the European Union.

Google and Valve, if you choose their sign-in, handle your data under their own responsibility and may do so outside the European Union, notably in the United States.

Your rights

You may ask for access to your data, rectification, erasure, restriction or objection, and portability. If you believe your rights are not respected, you may lodge a complaint with the CNIL (cnil.fr), the French data protection authority, or with the authority of your country of residence.

To exercise your rights, write to contact@tether-game.com. The legal response time is one month.

Deleting an account and exporting your data are not yet available from “My account”: until then, make the request by e-mail at the address above.

Minors

To create an account you must be at least 15, or have the permission of a parent or legal guardian. A tick box at sign-up, to declare it, is being prepared.

Last updated: 11 October 2026.