Privacy policy
Last updated November 18, 2026
Gachafeed is a free fan site for gacha redeem codes and news. There are no accounts, and we never ask for your password or game login. Here’s everything the site keeps, and where.
On your device
Your picked games, which codes you marked as redeemed, how you set up My feed (Full feed or Codes only, and its layout), your theme and language, and any player ID or nickname you type in are saved in your browser’s local storage, and clearing your browser data removes them. So are how many times we’ve suggested you pick a hunter name and when, the comments you voted on or reported and your poll answers, with the random ID that goes with them (see Comments below). A visit that arrived from a tagged link (see below) keeps that tag in session storage until the tab is closed. Your player ID and nickname never leave your device (a comment nickname goes out only with a comment you post), and your redeemed marks go to the leaderboard under a random name (see below), unless you remove yourself from it; which games you follow and language switches are only counted anonymously, as described below.
What reaches our server
- Visit counts: once per browser session, the page you’re on (for example
/hsr/codes/) is counted, as a total and per day. Nothing else is sent with it. - Anonymous usage counts: when you copy a code, open a redeem page, tap a new-code alert, pick games (and, when your feed opens, which games it shows), open a section or tab, follow a link to another site, or switch language, the page sends a count of that action with the page it happened on (and, for codes, the game and code). It carries no cookie and no identifier, and nothing is stored on your device for it; our server adds only the country Cloudflare reports for the request and whether it came from a phone or a computer. If a page hits an error, the error message is counted the same way so we can fix it. If you arrived from a link tagged with
?ref=(for example?ref=redditon one of our ads), that tag is counted too: it’s kept in your browser’s session storage for that visit only, so codes copied on the next pages count against it, and it’s gone when you close the tab. We see totals only, such as “this code was copied 40 times this week”. - “It worked” votes and “Didn’t work?” reports: to count one vote per person, we keep a shortened one-way hash of your IP address (not the address itself) with the code you voted on, for 30 days.
- Comments (optional): a comment or reply stores the nickname you type, its text and the time, together with a random ID your browser keeps for comments (in local storage: no cookie, no account) and a one-way hash of your IP address (salted, never the address itself), used for posting limits and to stop abuse. Nothing else. Comments are public on that game’s page in every language and in My feed (the achievements comments: on the profile page in every language) until they’re removed. Votes and reports store the same random ID and IP hash, so each counts once; answers to the polls under Gachafeed’s own comments, and to the site’s own polls (such as My feed’s layout poll), store only the random ID. The hourly limits on votes, reports and poll answers use the hash for an hour only. To have a comment removed, email contact@gachafeed.moe with the game and the comment’s nickname and text.
- New-code alerts (optional): if you turn them on, your browser’s push address, the games you picked and your language are stored so we can send the alert. Alerts travel through your browser’s own push service (for example Google for Chrome, Mozilla for Firefox, Apple for Safari), which passes them to your device. Turning alerts off deletes what we stored, and so does the push service telling us the address no longer works.
- Feedback (optional): what you write, an optional name, the page you came from, your language and device type go to a private Google Form we read.
The site and its server run on Cloudflare, which briefly processes IP addresses to deliver pages and block abuse (for example, rate limits on reports).
We also use Cloudflare Web Analytics to see how many people visit and where they come from (for example, a search engine or Reddit). It uses no cookies and doesn’t track you across sites; we only see totals such as page views, countries and device types.
We use Google Analytics to count visits, see which pages are used and which sites send visitors who go on to use Gachafeed. Besides page views, it receives a few actions: copying a code or opening a redeem page, picking a game, an “It worked” vote and opening a new-code alert (each with the game, never the code), turning on alerts (with how many games), and switching language, each with the page’s language. Never a code, a comment, your player ID or anything else you typed. It sets cookies in your browser. In the EEA, the UK and Switzerland it only does so after you agree in the consent message Google shows on the page. Google’s privacy policy explains how Google uses this information.
Your profile, achievements and the leaderboard
You can create a code hunter profile: a name, an icon and achievements counted from what you do here. It is still not an account — no email and no password. Your achievement unlock dates, the days you visited and a small log of your activity on the site (for example when you redeemed or copied a code, and which pages you opened — the achievements are counted from it) are saved in your browser’s local storage, next to your other settings, and never sent to us. The log starts with your first visit, profile or not, so achievements unlock with a small notice on the page from the start. “Remove me from the leaderboard” or deleting your profile stops it (deleting the profile also clears it), and clearing this site’s data in your browser removes it.
Everyone who marks codes as redeemed is on the public leaderboard. Without a profile you are there under a random name (anon_ and six letters, with a random icon): the first time a redeemed mark is sent, your browser joins the board anonymously and sends your marks. Making a profile gives that same hunter the name and icon you pick, and its points stay. Profiles made before November 4, 2026 join on their next visit. For the leaderboard:
- Public: your hunter name, icon, points and ranks, the badges in your showcase, the title you wear, your favourite game if you chose one, your season titles, the day you joined the board, how many of your codes were counted, and your daily streak (days in a row and your best). Anyone can see them on the leaderboard and on your hunter’s page.
- Kept on our server, not shown: which codes you marked as redeemed and when (each mark is sent as a claim, and undoing the mark deletes it); for the daily streak, once a day your browser sends its time zone offset (for example UTC+9, never your location), and we keep that offset, the date and time of your last visit that counted, your streak and its points for each month; a one-way hash of the IP address you joined from (salted, never the address itself), used to limit new hunters per network and to spot abuse; and a hash of a long random secret that only your browser keeps (in the profile, or in local storage until you make one), so only it can change your hunter. The hourly limits on claims use hashes for an hour only.
- Moderation: we can rename a hunter or hide it from the leaderboard (for example for an offensive name or for gaming the board).
- Leaving: “Delete profile” deletes your hunter from our server — its claims, streak, points, season titles and places on past boards — and removes the profile, the visit days, the unlock dates and that log from your browser. There is no way to stay on the profile without the leaderboard. Without a profile, “Remove me from the leaderboard” on the profile page deletes your anonymous hunter the same way, and nothing more is sent from that browser unless you make a profile. Clearing your browser data loses the secret, so an anonymous hunter left behind can no longer be changed by anyone; write to us to have it removed.
Your hunter card is an image your browser draws. If you share the card or copy its link, the card’s content (name, icon, title, numbers, badge icons and theme) is encoded in the link itself, so only share it if you want those seen.
The lounge (beta)
The lounge is a room where visitors see each other as little characters. Opening it connects your browser to our server for as long as the page is open. Everyone in the house can see your name there (your hunter name, or a random name, anon_ and six letters, made from a random ID kept in your browser), your character’s colour, where it stands or sits and in which room, the emotes you send, the café item you carry and your favourite game if you chose one. There is no chat: nobody can type anything.
- Not kept: what you do in the lounge is passed on to the others in it and not stored; it is gone when you leave. Your network address is used only while you are connected, to limit how many connections one address can open.
- Kept in your browser: that random ID, your colour, your emote bar, the music setting and volume, your favourite game, and whether you’ve seen the how-to-play and name boxes.
- A name and a favourite game: picking a name in the lounge makes a profile, exactly as described above. A favourite game is saved to your hunter (when you have one) and is public, like its name.
- Videos: when an official livestream is on air, the livestream room plays it with YouTube’s or Twitch’s player, which contacts that service from your browser (YouTube through its “no cookie” address). The Discord and Ko-fi signs are ordinary links.
- Music: the lounge’s music is made in your browser; no audio is downloaded or sent.
Google Drive backup (optional)
The profile page can back up your save data (your settings in this browser: redeemed marks, picked games, the profile, including your hunter’s secret, so restoring it is the same hunter) to your own Google Drive. It uses Google’s own sign-in, in your browser, and asks for one permission only: a hidden, private app folder that only Gachafeed can open (drive.appdata). The save file goes from your browser straight to your Google Drive — it never touches our servers, and we never see your Google account, your files or your sign-in; the short-lived access token stays in the page’s memory and is gone when you leave. Restoring reads that same file back. Google’s handling of the sign-in is covered by Google’s privacy policy. To remove the backup, delete Gachafeed’s hidden app data in Google Drive’s settings (Settings → Manage apps), or just overwrite it with a new backup.
The Android app
The Gachafeed app for Android works like the site, with these differences:
- On your phone: your picked games, your alert choices and the last list of codes it loaded (so it works offline) are saved in the app's own storage on your phone. Uninstalling the app removes them. There's no account.
- Codes: the app asks our server for the list of working codes. That request carries no identifier.
- Anonymous usage counts: the same counts as the site (copying a code, opening a redeem page, tapping an alert, picking a game, opening a tab, following a link), marked as coming from the app, plus a count each time the app is opened. No identifier, nothing stored on your phone for it.
- Code alerts (optional): if you turn them on, Google's Firebase Cloud Messaging gives the app a push token, and we store that token, the games you want alerts for, your phone's language and whether you also want "ending soon" alerts. Alerts travel through Firebase to your phone. Turning alerts off, for every game or in your phone's settings, deletes what we stored, and so does Firebase telling us the token no longer works (for example after you uninstall). Google's handling is covered by Google's privacy policy.
- Crash reports: if the app crashes, Firebase Crashlytics sends a report so we can fix it: where in the app it broke, your phone model, Android version and app version, and a random ID Crashlytics uses to count crashes. It doesn't include your games, codes or anything you typed.
- Pictures: each game's header art loads from the same place as on the site (the game's official X profile, YouTube channel or store page), so that site sees the request.
- News, videos, X and Reddit on a game's page: the first time you open one of those tabs, the app asks our server for that game's lists (no identifier), and their pictures load from the news site, YouTube, X or Reddit, as on the site.
- Videos: a video you tap plays in YouTube's own player inside the app, using YouTube's privacy-enhanced ("no cookie") address, so YouTube sees that you watched it, as it does on the site's livestream room. "Watch on YouTube" opens it in the YouTube app instead.
- Home-screen widgets: they show what the app saved on your phone and send nothing anywhere. Their Copy button puts a code on your clipboard.
The app has no ads and doesn't use your location, contacts or photos.
Ads
Gachafeed shows ads from Google AdSense to cover its costs. Google and its partners use cookies to serve ads based on your visits to this and other sites. Visitors in the EEA, the UK and Switzerland are asked for consent first, and can change their choice at any time from the privacy link Google shows on the page.
You can turn off personalised ads in Google’s ad settings, and read how Google uses information from sites that use its services.
Links to other sites
Redeem buttons, news, videos and posts open the official game pages, YouTube, X, Reddit or Ko-fi. Those sites have their own privacy policies.
Questions
Ask anything through the feedback page, or email contact@gachafeed.moe.

