Privacy
What StickFrag knows about you, why, and for how long.
Last updated 31 October 2026
The short version
- No account needed, no real name. You pick a nickname, and that is all we ask. If you choose to sign in with your email, we keep that address (see the table).
- No advertising trackers, no analytics cookies, no profiling, and we never sell data.
- Your browser keeps a random code so you keep your level. Our server stores only a scrambled (hashed) version of it, next to your XP. Unused profiles are deleted after 12 months. Our databases are copied every night, encrypted, to a Cloudflare storage bucket in the EU. A copy is deleted after 30 days, so deleted data leaves the copies within 30 days.
- If you are among the top 100 by XP this week or of all time, the public leaderboard shows your nickname, level and match numbers. The top 5 of each week are also posted in our Discord server. Ask us and we take you off both.
- Our server needs your network (IP) address to send you the game. It does not write the address to its logs or databases.
Who is responsible
The controller for the data on this site and in the game is the operator named in the imprint. Questions and requests go to [email protected].
What we process, and why
| Data | Why | How long |
|---|---|---|
| Your network (IP) address | To connect you to a match and send you the game. To limit how many players and joins one network can start, so one person cannot flood the server. | In the server's memory while you are connected, and for a few minutes after a join. Never written to logs or databases. |
| Hashed network address (a salted, one-way code made from your IP address) | Stored with player reports and anti-cheat records, so we can see repeated abuse from one network without storing the address itself. Also stored when a network tries the server's private admin page twice without permission, to block that network from the admin page. | With a report: 90 days. An anti-cheat flag on a network ends after 24 hours. A count of banned profiles on a network (hashes only) ends 90 days after the latest ban. A network with 3 banned profiles holds new profiles and profiles that never played on it before the hold, for 365 days after the latest ban. A row with the start of that hold (address hash only) ends with it. An admin-page block ends after 12 months. |
| Hashed device code (a salted, one-way code made from signals your browser shares about your computer: graphics card, screen size, processor cores, memory, time zone, languages and a small drawing test) | Sent when you join a match and stored with your hashed browser code and hashed network address. It lets us ban a cheater's computer on a network without banning the other computers there, for example at a school. It never stops anyone from joining by itself. We keep no readable signals. | 90 days after you last played. A ban of a computer on a network holds new profiles only, for 365 days after the ban. |
| Invite code (8 characters, a one-way code made from your hashed browser code) | It rides on the invite links and COPY LINK you share (&ref=). When a new player opens your link and finishes 3 matches, you both get a card pack. We then keep the pair of hashed browser codes, a hashed network address and the time, to pay once, to hold a few rewards a week per player, and to pay no reward between players on one network or one computer. |
90 days after the new player first opened the link. The code goes with your progress profile. |
| Nickname | Shown to the other players in your match, with the title you chose to wear, if you own it, and on the game's server list while you are in one, so friends can find the match. Kept as the "last nickname" of your progress profile, and in reports about you, so moderators know who a report is about. Shown on the public leaderboard while your profile is in the top 100 of the week or of all time. | As long as the profile or report it belongs to (see below), and in server logs. |
| Progress profile: hashed browser code, XP, kills, deaths, matches played, wins, last nickname, first and last play date, and the same numbers for the current week. Also the items you own (such as hats) and your progress towards them: grenade, knife and headshot kills, kill streaks, wins and matches with friends; your counts in an event's hunts (such as pumpkins or windows broken, or crates found that day); and the card packs you earned, with the three cards in each and the one you picked | Your level, XP and items across visits. The public leaderboard: the top 100 by XP this week and of all time, with nickname, level, XP, kills, deaths, wins and matches. Nothing else from the profile is shown, and suspected cheaters are left out. At the end of each week, the top 5 (nickname, XP and kills) are also posted in the #leaderboard channel of our Discord server, where the post stays. Ask us and we take you off the leaderboard for good, and delete a Discord post with your nickname; your level stays. | Deleted 12 months after your last match. The week's numbers are deleted when the week ends (Monday 00:00 UTC); we keep no past weeks. |
| If you sign in with email: your email address, kept encrypted, a coded (hashed) form of it that we use to find your account, and an encrypted copy of your browser code. The 6-digit code we send you works for 10 minutes. We keep only a hash of it, and delete it within 2 days. We never keep your password, because there is none. | To let you sign in on any device and get your progress back, and to send you the sign-in code. We use your address for nothing else: no newsletters, no ads. Signing in is your choice; the game works without it. | Until you press "Delete my account" in the Locker, and deleted 12 months after your last sign-in or last match. Resend keeps a delivery record of the mail for a short time (see the services below). |
| This row takes effect at the Steam launch. Until then Steam sign-in is off and we keep none of this. If you sign in with Steam, in the StickFrag Steam app or on our website: a coded (hashed) form of your Steam ID that we use to find your account, and an encrypted copy of your browser code. In the app, Steam checks a one-time ticket for us. On the website, you sign in on Steam's own page and Steam sends you back to us with a signed answer, which we check with Steam. We do not keep the ticket, the answer, your Steam ID in readable form, your Steam name or your picture. Your browser holds a random number for the few minutes of the trip, in its session storage, and deletes it when you come back. | To let you sign in on any device and get your progress back. Signing in is your choice; the game works without it. | Until you press "Delete my account" in the Locker, and deleted 12 months after your last sign-in or last match. Valve, the company that runs Steam, receives the ticket or the signed answer, and the Steam ID, when it checks them (see the services below). |
| Match statistics and anti-cheat points linked to the hashed browser code. For each match you play, one short summary: map, mode, time played, kills and deaths, shots and hits per gun, and how long you stood still | To find cheaters. A player whose numbers strongly suggest cheating can be matched apart from other players for a while. A person looks at reports before any ban. | The per-match summary: 14 days. Points halve every 14 days without new signs of cheating. The record is deleted when no points are left, or after 12 months without an update. Cheating confirmed by a person (matches only with other cheaters) is deleted after 12 months without an update, or earlier if it is undone on appeal. Reports: 90 days. The daily review of play (a note on a token hash that a week of play looked unusual, with the reason; it changes nothing for the player): 90 days. |
| Player reports you send: the reason, the players involved (hashed codes and nickname of the reported player) and match statistics | To review reports and act on them, as the EU Digital Services Act requires. | 90 days, longer only while a report supports an active ban. When a person bans the player you reported for cheating, we give you a thank-you pack and one card on the home page: a record of the ban, your hashed code and the reported nickname is kept for 90 days. |
| Feedback you send: the text, its type, your nickname and level, the page, your browser type and the hashed browser code | To read your idea or bug report. Good ideas may appear on the public ideas board, in our words. When we build an idea from your message, we may show your nickname with it ("Suggested by"), on the ideas board and on the home page. The home page asks the ideas board, with your hashed browser code, which ideas came from your messages, so it can tell you once that yours is live. We may also show a short part of a message that thanks us, without a name, on our pages. Do not put personal details in the text. | 180 days. A message that led to an idea on the board is kept as long as the idea. Ask us and we delete a message. |
| Likes on the ideas board: the hashed browser code, which idea you liked, and when | To count each player's like once, and to show you which ideas you liked. Before a like counts, the ideas board asks the game server how many matches that code has played, so made-up codes cannot add likes. Ideas on the board are written by us; your messages are never shown there. | Until you take the like back, or we delete the idea. Ask us and we delete your likes. |
| Emails you send us: your address, your message and anything you attach | To answer you: questions, reports, appeals, requests about your data, and brands that ask about ad space. | Until the matter is closed, then up to 12 months, so we can see earlier contact on the same matter. Longer only where a law requires it, for example bookkeeping. |
| Tips: the name and message you give the tip service, the amount, the date, and the email address the service passes on | To thank you if you ask for it, to handle a refund, and for our tax records. | 7 years, as Swedish bookkeeping and tax rules require for income records. |
| Play history: hashed browser code, nickname, map, match type, when you joined and left a match, how many matches you finished there and the XP you earned in it (for kills, for playing, for your place, for a win) | To count players and play time, to plan how many servers the game needs, and to see whether new parts of the game make players come back. Daily totals made from it hold no person and are kept for a year. | 90 days. |
| Server logs: events such as joins, matches, reports and errors, with nicknames and in-match numbers. When you open or join a friends match, we note your hashed browser code and whether you came by a link, a typed code or the menu; when you copy an invite link or code, open the home page or press PLAY on it, your browser tells us so (with your hashed browser code, to count where new players stop). A join also notes your country and the Cloudflare data centre you connect through, as Cloudflare reports them (no address lookup by us). While you play, your browser also sends its frame rate, ping, graphics card name, window size, whether it is an automated browser, and any game script errors | To keep the game running, fix bugs and look into abuse. The country shows us where to put new game servers, so players get a lower ping. | 14 days; frame rate and graphics reports 2 days. The lines about an attack on the game (for example a flood of scripted players) are kept up to 90 days to look into it. Logs never contain IP addresses. |
| Match recordings of public matches: what every player in the match could see (positions, movement, shots, kills, scores) and the nicknames. Not friends matches or training. We keep each recording on the game server and in a storage bucket of Cloudflare, Inc. | To keep play safe and fair, also for children: we watch them to check reports of cheating or abuse, to moderate matches and nicknames, and to improve the game and its safety. We also make videos of the game for our own social media accounts; in a video every nickname is replaced by "Player 1", "Player 2" and so on. We post the videos through Buffer, Inc. (USA) from a public Cloudflare storage bucket, which deletes each file after 14 days. | Up to 1 year; when a server's disk runs low, the oldest go first. A video made from a recording stays up as long as we publish it. |
| Community review: when you watch a short clip of another player's match and vote Cheating or Not cheating, we keep your vote, up to 5 moments you marked with a reason from a list, a hashed browser code and a hashed network address. We also note which clips you saw, so you never get the same player twice. The clips have no names: every nickname is replaced. Chat is removed from the clip. Other players who volunteer to review see the clip; our servers and Cloudflare, Inc. (the storage bucket, in the EU) hold it. For each counted vote you get one standard card pack, up to 5 a day; we keep a note of it. | To keep play safe and fair: players help us check reports of cheating. A vote changes nothing for the player in the clip. A vote alone never bans anyone; a person at StickFrag decides. The network code only stops a second review of the same player and links no profiles. | 90 days after the case is closed, then deleted. |
| Replay studio (invited people only): a person who makes videos for us gets a username and a password that we make for them. We keep the username, a scrambled (hashed) form of the password, the time of each login and a count of logins. A person with an invite can watch the public match recordings above, with the nicknames of the players in them, to film the game. A server log line records which recording they opened, not their password. | To make videos of the game with people who help us. An invite stops the moment we revoke it. | Until we revoke the invite; the invite row is deleted 90 days after that. |
| Room chat: every line you write in a match (the text), your nickname at the time, the room, the time, a hashed browser code and a hashed network address. Lines the automatic filter blocked are kept too, with the name of the list that blocked them. A line that was sent is shown to everyone in the room, and the moderators can read it here. | To keep the chat safe, also for children: to check reports of abuse, threats and hate, to mute or block players who break the rules, and to tune the word filter. The text is never written to the server logs. | 30 days, then deleted. |
| Creator rewards: if you send a link to your own StickFrag video to claim a reward, we keep the link, the account name on TikTok, YouTube, Instagram or X (from the link, or as we saw it on the video), a short code that we gave you, our decision, our note if we refused, the number of views we saw, and the time. We also keep a hashed copy of the link and of the account name, tied to your hashed browser code. We do not ask for a password or a login of that platform. | To check that the video is real and yours, to give each reward once, to stop two players from claiming one video or one account, and to take a reward back if the video turns out to be fake or bought. It is optional: you send a link only if you want a reward. | The link, the account name and our note: 12 months after our decision, then deleted. The code: until our decision. The hashed copies, the tier and the views: as long as your profile, so that a second claim of the same video or account is still refused; they hold no readable link or name. A claim that nobody decides is refused after 90 days. |
Legal basis (this includes the room chat): our legitimate interest in running a fair, safe and working game (GDPR article 6(1)(f)), and for reports our duties under the Digital Services Act (article 6(1)(c)). Tip records are kept because tax and bookkeeping law requires it (article 6(1)(c)). We make no automated decisions with legal or similarly significant effects on you. The automatic steps against cheating (no XP, or matches only with other suspected cheaters) are described in the terms of use.
What your browser stores
We set no cookies. The game keeps these values in your browser's local storage, only so it can do what you asked for. None is used for advertising or tracking.
| Name | What it is |
|---|---|
name | The nickname you typed, so you do not type it again. |
profileToken | The random code that keeps your level. Our server stores only its hash. |
profileXp2 (before 6 October 2026: profileXp) | Your XP, so the menu shows your level before you join. |
profileOwner | Set only in the game owner's own browsers, so their menu shows the owner's badge instead of a level. |
headband, skin | The colours you picked. |
map | The map you picked. |
gameMode | The game mode you picked (team deathmatch or gun game). |
tdmLoadout | The guns (primary, heavy weapon, sidearm) and grenade you picked for team deathmatch and free for all. |
settings | Mouse sensitivity, scoped sensitivity, field of view, HUD size, volume, graphics quality, and the "Show FPS", "Reduce motion" and "Toggle aim" choices. |
noBotsOnly | Whether you switched "No bots" on above the server list, so it lists only servers without bots. |
chat | Whether you switched the room chat off in the settings. |
stickfrag-studio-token | Only on the replay studio page, for invited people: the session code that keeps you signed in for 24 hours. |
hasMouse | That this computer has a mouse or trackpad, so a laptop with a touch screen gets the play menu and not the "play on a computer" note. |
optics | The sight you put on each gun. The other players in your match see it on your gun. The game server keeps it only while you are in the room. |
sightHint | Whether you have changed a sight yet, and how often the "T: change sight" tip came up, so it stops showing. |
fullscreen, keybinds, touchLayout | Whether you chose full screen, the keys you changed, and where you moved the touch buttons. |
hat, outfit, title, titlesSeeded, newItems, ownedColours | The hat, the skin and the title you wear (the game sends them when you join a match, so the other players see them), that your titles got their "NEW" mark once, which items in the locker you have not looked at yet, for the "NEW" marks, and which special body colours you own, so the colour row can show them. |
fhMatches, fhFree | How many matches you played and whether your profile was past its first hour, so the game shows its reward screens step by step. |
route, regionPick | Which game server is nearest to you and which way the connection goes to it (kept for 30 minutes), and the region you picked in the play menu. |
saveOfferLater, profileTokenBefore, profileTokenBeforeAt | When you pressed "later" on the offer to save your profile, and the profile code this browser had before a sign-in replaced it, kept for 7 days so you can undo. |
recruitRef, recruitMine | The invite code a friend's link brought, until the game server has taken it, and your own invite code, so COPY LINK can carry it. |
ideasLiked, ideasShippedSeen, ideasSender, ideasNewDismissed | Which ideas on the ideas board you liked, which shipped ones you were told about, whether you sent us a message, and which "NEW!" cards you closed, so the game can say once that an idea you sent or liked is live. Only in your browser. |
sf-review-intro | That you pressed "Start watching" on the short explanation before a community review clip, so the game shows it once, not on every case. Only in your browser. |
To delete them, clear this site's data in your browser settings. That also resets your level; the old profile on our server can then no longer be linked to you, and it is deleted after 12 months.
Who else handles data for us
- Cloudflare, Inc. (USA) delivers this site and protects the game server from attacks. The site, matchmaking and every request except the game connection pass through Cloudflare, which processes your IP address for us. The game connection goes through Cloudflare too, unless a direct connection to our server is faster for you. Cloudflare may set a strictly necessary security cookie when it checks for bots. Transfers to the USA rely on the EU–US Data Privacy Framework and the EU standard contractual clauses.
- Akamai Technologies, Inc. (USA), through its cloud service Akamai Cloud (formerly Linode), runs the servers that host the game and its databases. The servers are in Stockholm, Sweden, and the data is stored only there. Because Akamai is a US company, its staff could reach the data from outside the EU, for example for support; such access relies on the EU–US Data Privacy Framework and the EU standard contractual clauses.
- HostUp (hostup.se, Sweden) ran the game until 5 October 2026. It keeps a stopped copy of the game's data as it was that day, in Sweden, until we delete it.
- Resend, Inc. (USA) sends the sign-in code to your address, only if you sign in with email. It receives your address and the code, and keeps a delivery record with the address for a short time. Transfers to the USA rely on the EU–US Data Privacy Framework or the EU standard contractual clauses.
- Valve Corporation (USA, the company that runs Steam). From the Steam launch. Our server sends it the one-time ticket from the Steam app, or the signed answer that Steam gave your browser on our website, and it answers with your Steam ID or confirms the answer, only if you sign in with Steam. On the website your browser also talks to Steam directly, on Steam's own page. Valve keeps data about your Steam account under its own terms. Transfers to the USA rely on the EU–US Data Privacy Framework or the EU standard contractual clauses.
- Apple (iCloud Mail) receives and stores the email you send to our addresses, under its iCloud terms. Apple can store mail outside the EU; such transfers rely on the EU–US Data Privacy Framework or the EU standard contractual clauses.
Cloudflare, Akamai, Resend and HostUp act on our instructions under a data processing agreement. We share data with nobody else, except when the law requires it.
Tips go through an outside service (Ko-fi) and its payment providers (PayPal or Stripe). They decide for themselves how they handle your payment data, under their own privacy policies. We never see your card or bank details.
Our Discord server
We run a community server on Discord. Joining it is up to you, and it is separate from the game: we do not link your Discord account to your game progress. The only thing the game sends there is the weekly top 5 of the leaderboard (see below). Discord, Inc. (USA) runs the platform and handles your data there under its own privacy policy. In our server we see your Discord name and what you post, and the answers you pick when you join (such as your region, which helps us decide where to put new game servers). We use them to run and moderate the server, under our legitimate interest (GDPR article 6(1)(f)). Discord also shows us statistics about the server; for those, Discord and we may be jointly responsible. Moderators can delete posts that break the server's rules; you can delete your own posts at any time.
Children
Many of our players are young. The game is for players aged 16 and over, and we ask for no age, real name or photo; an email address only if you choose to sign in with it. Please do not use your real name as your nickname. Offensive nicknames are blocked or renamed. A parent or guardian can ask us to delete a child's data at the address above.
Ads
Today the game shows no paid ads. If sponsors' art appears in the yard later, every player in a match sees the same art. There will be no ad targeting, no profiles and no ad trackers.
Your rights
You can ask us to show, correct or delete your data, to limit how we use it, or to hand it to you, and you can object to how we use it. Email us. We have no real name for you, and an email address only if you signed in with it, so tell us your nickname and roughly when you played; if we need your browser code to find your profile, we explain how to copy it. We answer within one month.
You can also complain to the Swedish data protection authority, Integritetsskyddsmyndigheten (IMY, imy.se), or to the authority in your country.
Changes
When the game starts to use data in a new way, we update this page first and change the date at the top.