SQUAD SURGE privacy

The short version: no accounts, no tracking, and the game itself sets no cookies. The only things about you that are ever saved on the server are the ones listed below, and only when you post a score to the shared leaderboard.

What is collected when you post a score

Your initials, score, wave, kills and the posting time are public, together with the score's row number in the leaderboard's list: anyone can see them on the leaderboard or read them from the address the game loads it from. The duration is stored but not shown. Each posted run also gets a random run number and the game's rules version; neither says anything about you.

To limit abuse, the server also stores short keyed hashes derived from the IP address the score was posted from, alongside the score: one for the address itself and, for IPv6 addresses, a second one for the wider network that address belongs to. The stored hashes are used for three things and nothing else: to limit how many scores one network can post in a day, to keep only each network's best scores of the day on the boards (three per address and six per wider network; any others are stored but not shown), and to let the owner hide everything one source posted. They are not your IP address, cannot be turned back into it without a secret key, and are different every day. A clean-up that runs once a day clears them from scores more than 48 hours old, so each is kept for between 48 and 72 hours; in the same step it deletes the scores that were stored but not shown. Your IP address itself is not saved with your score and is not logged by the game.

One more thing uses the same daily hash, worked out from your address while a request is being handled, without saving it with any score: the request counter described under “When scores are posted” below.

What is not collected

There are no accounts, no email addresses, no device identifiers, no analytics and no advertising or tracking of any kind. The game itself sets no cookies.

What stays on your device

These are kept in your browser's local storage and are not sent anywhere: your local top-10 scores, your best wave, your last initials, the mute setting, your posting choice, your best posted score of the week, a wait-until time if the server asked the game to slow down, and up to five scores waiting to be posted. A waiting score is sent only while posting is on, and is discarded when its run ticket expires (six hours after that run started), if the server says it cannot be posted, or as soon as you turn posting off. Clearing this site's data in your browser removes all of it.

How long posted scores are kept

When scores are posted, and how to turn posting off

Nothing is posted until you press SAVE on an initials screen that says “Posts your initials and score to the public board”. On that screen Esc (or the SKIP / DON'T POST button) declines for that run. After you have posted once, a run that beats your best posted score of the week is posted automatically under the same initials.

To stop, open the leaderboard and press O (or tap the POSTING button) so it reads off. While posting is off the game sends no scores, waiting scores are discarded, and you can still view the shared boards and use the local board. Press O again to turn it back on; you will be asked on the initials screen before anything is posted.

Unless posting is turned off, the game asks the server for a one-time run ticket at the start of each run, including before you have ever posted. The request contains nothing about you or your play, and the server saves nothing when it issues a ticket. The ticket contains a random run number, the time it was issued and the rules version, sealed so it cannot be altered, and nothing about you, your device or your network. Your browser keeps a ticket only while its run is being played or its score is waiting to be posted, six hours at most. A score can be posted from a different network than the run started on (Wi-Fi to mobile data, for example); it then counts against the limits of the network it is posted from.

To stop floods, requests to the leaderboard from each address are counted for about a minute at a time, by the server and by Cloudflare's rate limiting service, under a daily keyed hash rather than the address. Those counts are not saved with any score and expire on their own.

Hosting

The game and its leaderboard are hosted by Cloudflare. As the host, Cloudflare processes every request to the site, including the IP address it comes from, in order to deliver it and protect it, under its own privacy policy; that is true whether or not you post a score. Any cookie you see on this site would come from that delivery service, not from the game.

Removing a score

To have a posted score removed, write to privacy@criffelstudios.com with the initials, the score and roughly when it was posted. Removal happens in two steps: the score is first hidden, which takes it off the boards within about a minute, and the daily clean-up then deletes it for good once the day it was posted is more than 14 days in the past. A hidden score is never kept as part of the all-time top 1,000.

Back to the game