Privacy Policy
Last updated: October 11, 2026
- No accounts, no sign-up, no passwords.
- No ads, no tracking cookies, no selling or sharing of your information.
- Your player name, look, settings, story progress and Explore worlds stay in your own browser.
- We count visits and matches anonymously, without cookies and without storing IP addresses.
- We only learn your name and email if you write to us with the Contact form.
Who we are
SugarStrike is a free candy tag game played in the web browser at sugarstrikeapp.com. "We" means the small team that makes it. You can reach us with the Contact us form on the home page.
What stays on your device
The game saves these in your browser's local storage so they're there next time. They are never sent to us:
- the player name you type in (any nickname works; please don't use your full real name),
- your character's look,
- your settings (sound, controls, graphics and Performance),
- your Story mode progress and difficulty, and whether you've seen a tip,
- your Explore worlds: each world's random number (its "seed", made on your device from randomness and the date and time, never from anything about you) and what you've found there.
You can delete all of it any time by clearing this site's data in your browser settings.
Playing with friends
Multiplayer rooms connect players' browsers directly to each other (peer to peer, using WebRTC). To set up that connection, the game uses the free PeerJS service (0.peerjs.com, and its relay servers if a direct connection isn't possible) and a Google connection-check server (stun.l.google.com). Like any connection on the internet, these services and the other players in your room can see your device's IP address while you play. What players send each other is game information: player names, looks, positions, scores and preset quick-chat messages. There is no open text or voice chat, and nothing from a match is saved by us.
Rooms are private: only people who have your room code or invite link can join.
Anonymous play counter
On the public website, the game tells our server when the page opens and when a match starts, so we know roughly how many people play. To avoid counting the same device twice in a day, the server makes a scrambled code (a one-way hash) from the IP address, browser type and date with a secret key, and keeps only that code, for that day. We don't store IP addresses, don't use cookies for this, and can't follow a device from one day to the next. What we keep are daily totals of visits and matches.
Contact form
If you send us a message, we receive your name, email address and message by email so we can reply. We use them only to answer you and delete them when they're no longer needed. To stop spam, the server keeps a scrambled code of your IP address and the time for up to one day; it doesn't keep the message itself.
If you're under 13, please ask a parent or guardian to write to us for you.
Other services the game loads
| Service | Why | What it sees |
|---|---|---|
| Hostinger (our web host) | Delivers the game's files | Standard web server logs (IP address, browser, pages requested), kept by the host for a limited time |
| Google Fonts | The game's lettering | Your IP address and browser (Google's privacy policy) |
| PeerJS and Google STUN | Connecting players in a room | Your IP address and a random connection ID |
| icanhazdadjoke.com | Jokes shown while the props hide in Hunters vs Props | Your IP address (no cookies are sent) |
Children
SugarStrike is made for players aged 8 and up and for families. We don't ask for, and don't knowingly collect, personal information from children. Children don't need to give us anything to play. If you think a child has sent us personal information through the Contact form, tell us and we'll delete it.
Your choices and rights
- Clear your browser's site data to remove everything the game saved on your device.
- Play solo against bots to avoid connecting to other players.
- Ask us to see, correct or delete anything you sent through the Contact form. Depending on where you live (for example under the GDPR, UK GDPR or CCPA), you may have further rights, and you can complain to your local data protection authority.
Changes
If this policy changes, we'll update the date at the top of this page. We won't start collecting more information without saying so here first.