Forge Clicker: Privacy Policy
Last updated: November 9, 2026
Forge Clicker is a single-player game. There is no account to create and no sign-up. Your game progress is stored in a save file on your own device and stays there unless you turn on the optional cloud-save backup described below; uninstalling the app deletes the local save.
The game uses the services described plainly below: our own anonymous usage statistics, optional rewarded ads (Google AdMob), in-app purchases (Google Play / App Store), and the platform's optional game services (Google Play Games on Android, Apple Game Center on iOS). That is the complete list. There are no other SDKs, trackers, or data recipients.
Anonymous usage statistics (first-party)
To understand how the game is played and to catch crashes, the game sends us a small number of gameplay events: things like “a session started”, “first boss defeated”, “prestige completed”, “daily bonus claimed”, which screen and which in-game panel you moved to and from, when a session was paused, when a setting was changed, when a part of the game unlocked, which permanent upgrades you bought, when you first reached one of the game's milestones (first craft, first dungeon, first prestige and the like), when a tower climb, Gauntlet attempt, challenge, or weekly raid was started or finished, when you gained a Tower key and which of its sources it came from (the daily grant, forging one, an ad, or the key a Remove Ads purchase grants in place of that ad), when time spent away was totted up, how far the game's tutorial has got, whether an idle reminder was scheduled, opened, or swiped away (and which of the handful of reminder kinds it was), and errors the game hits (file, line, error message, and what kind of error it was; warnings are not reported, and the same fault repeating is sent once rather than over and over). It also records that a rewarded ad was offered, watched, or dismissed (which of the game's few ad spots it was and whether the reward was earned, never anything about the ad itself); plus that one could not be shown when you asked for it, as the reason it failed and the store's own error code, never anything about the ad that did not arrive; and that an in-app purchase completed, as the product's catalogue name. On iOS that record also says whether the App Store marked the purchase as a real one or as one of Apple's test purchases (the kind Apple's reviewers and testers make, where no money changes hands), so test purchases are not counted as sales. That label is the only thing read from the store's record of the purchase: never the price, your payment details, or anything else in it. The first event of a session carries a little context with it: how long you were away, how long the game took to load, your device’s language (never its region), whether notifications are permitted, a count of any events that had to be dropped while you were offline, and a rough marker of overall progress (your level, how many times you have ascended, and how far your current run has got relative to your own best depth), the numbers that tell us whether the game has stalled on you. It also carries two facts about the phone itself: roughly how much memory it has, and its operating system version. Those two tell us which devices the game is too heavy for; neither is unique to you, and there are millions of phones that would answer both questions identically. Two further facts about the hardware ride with every batch rather than with this event; they are listed below.
Gauntlet events record when it unlocks, which level was attempted, whether it was a new best, party size, the outcome, waves cleared, fight time, knockouts, party roles (tank, damage, support), and whether autopilot was on. They contain no minion names and no per-hit log.
When you forge a piece of minion gear, the game records which of the four slots it was (weapon, helm, armor or trinket), the tier it reached, the minion's total gear tier, and how much Valor you had left. It does not record which minion it was.
When you break a Gauntlet seal, the game records which seal it was, the grade of ore and embers it cost (uncommon, rare or epic), and whether autopilot broke it. It does not record the amounts.
When you send minions on an expedition, the game records how long it was (4, 8 or 12 hours), how many minions went, and how many of its traits they answered; when you collect one, how many boss cores and shards it paid and whether it found a relic; and when you call one back early. It does not record which minions went.
When the game opens, it also asks the operating system how the game closed the last time: whether it crashed, ran out of memory, or was simply closed by you, whether it was on your screen at the time, roughly how much memory it was using, when it happened, and which version of the game it was. We do this because a game that crashes cannot report its own crash: the report has to come afterwards, from the system that watched it happen. It is a single line about the app, describing nothing you did and containing nothing about you, and it is covered by the same opt-out as everything else on this page.
On Android, the game also asks Google Play where the install came from, normally the first time it opens, and sends the answer once per installation (a reinstall counts as a new one). That answer is the campaign tags on the store link that led to the install (for example "google-play" and "organic" for someone who found the game by browsing the store, or the name of an ad campaign), whether the link came from a click on an ad, and when the link was clicked and the install began. We never send the full link or anything else in it, and of an ad click we record only that there was one, never the code that identifies it. It says how the game reached your phone, not anything about you. If Google Play cannot answer, we record that it could not, as a short error code. It is covered by the same opt-out: with usage statistics turned off, the game does not even ask.
When the game goes to the background it also records how well it ran during the sitting that just ended: an average frame rate, a low-end one for the roughest moments, how many times it sampled, the single longest frame, and a count of the noticeable freezes. Alongside it rides how long the opening took to become playable. That is a measurement of the app on your hardware, not of you or of anything you did, and it is what separates “the game is slow for everyone” from “the game is slow on this phone”.
When the game goes to the background it also records a snapshot of your in-game progress: how much of each in-game currency and crafting material you are holding, how deep you have reached, how many times you have ascended, and how many ore veins you have found and dug (and how many of those you dug by tapping). This is how we find balance problems: a resource that piles up with nothing worth spending it on looks obvious across many players and is nearly invisible in any single one. Large amounts are recorded only as a size (“about ten billion”), not an exact figure. All of it is in-game progress in a single-player game: none of it is money, none of it is purchase history, and none of it says anything about you.
- Events are tied to a random ID generated on your device at first launch. It is not derived from your identity, your device identifiers, or your Google account, and we cannot connect it to you. Alongside it, each batch of events carries the app's version, the platform (Android or iOS), a short-lived random session ID so events from one sitting can be grouped, and two facts about the hardware: the phone's model name (the manufacturer's, such as “Pixel 7a”) and the name of its graphics chip. Those two tell us which hardware the game runs badly on. None of these identify you or your device; millions of phones answer every one of them identically.
- We do not collect your name, email, contacts, precise or approximate location, advertising ID, or any file on your device, and we do not store your IP address.
- Data goes only to our own self-hosted service over an encrypted (HTTPS) connection. It is never shared with or sold to anyone.
- Opt out any time: Settings → Privacy → “Share Usage Stats”. Turning it off records that single decision (that usage statistics were declined, with no gameplay data attached) and then sends nothing further. We keep that one record because a withdrawal we kept no trace of is one we cannot show we honoured, and because without it we cannot tell how many players a given statistic actually speaks for. Any gameplay events still queued on your device are discarded.
- Delete: Settings → Privacy → “Reset Analytics ID” abandons the old ID (past events can no longer be associated with your device) and discards any queued gameplay events. One event (the reset itself) is recorded immediately before the new ID is created, so that starting over is not counted as a brand-new install. It carries no gameplay data, and the old and new IDs are never sent in the same batch. You can also email us to request deletion.
- Where the law requires us to ask first (the EEA, the UK, Switzerland, and anywhere else a consent form is required), we do. Nothing is collected before you answer: no events are sent, and the random ID above is not even written to your device while the question is open. If you decline, nothing is stored and nothing is sent, not even a record that you declined, and we do not ask again. You can still turn usage statistics on later from Settings > Privacy > “Share Usage Stats” if you change your mind.
- That question is ours and is separate from the ads consent form described below. The ads form governs how ads are served and is Google’s; it has never asked you about usage statistics, so we no longer treat it as though it had. The usage-statistics toggle in Settings is always available and is the single place your answer lives.
Rewarded ads (Google AdMob)
Forge Clicker shows ads only when you choose to watch one for an in-game reward (for example, doubling an away haul). There are no banner ads, no interstitials, and no forced ads of any kind.
Ads are served by Google AdMob. When an ad is loaded or shown, Google may collect device information such as the advertising ID to serve and measure ads, as described in Google's Privacy Policy and how Google uses information from sites or apps that use its services. In regions where consent is required (for example the EEA and UK), a consent form is shown before any ad is loaded, and you can revisit your choices any time via Settings → Privacy → “Ad Privacy Options”.
If usage statistics are on (see above), the game also records for itself that an ad was offered, watched, or dismissed: which of the game's few ad spots it was and whether the reward was earned, nothing about the ad content. That record is part of the same first-party stream and opt-out described above; it is separate from anything Google collects to serve the ad.
In-app purchases
The game offers optional one-time purchases (a drop-rate boost, a cosmetic supporter pack, and an ad-removal pack). Payments are processed entirely by the app store you downloaded this from (Google Play or the App Store); we never see your payment details. Your entitlements are stored in your local save and restored through that store's own purchase records (“Restore Purchases” in the Forge Shop). Nothing for sale is required to play or finish the game.
If usage statistics are on, the game records that a purchase completed: the product's catalogue name and, on iOS, whether it was a real purchase or one of Apple's test purchases, as described in the usage-statistics section above. We never see or store what you paid or how.
Achievements, leaderboards, and cloud backup (Google Play Games / Apple Game Center)
Forge Clicker can connect to your platform's game service (Google Play Games on Android, Apple Game Center on iOS) for achievements and leaderboards, and on Android also for an optional cloud backup of your save. This uses the gaming profile you already have with Google or Apple; the game never sees your account credentials, and we run no accounts or servers of our own for any of this.
- Signing in: on Android, Google Play Games may sign you in automatically if your device is set up for it, and a manual sign-in button lives in Settings; on iOS, Game Center sign-in is handled entirely by the system and the game shows no sign-in controls of its own. If you are not signed in, everything in this section simply stays off and the game plays normally.
- Achievements and leaderboards: while signed in, achievement unlocks and leaderboard scores (deepest dungeon floor, prestige count, highest Gauntlet level, lifetime gold) are reported to your Google Play Games or Game Center profile. Leaderboard entries appear to other players under that profile's public player name, as governed by Google's Privacy Policy / Apple's Privacy Policy and your profile's own visibility settings.
- Cloud-save backup (Android only, off by default): Settings → “Cloud Save” enables two manual buttons, Backup and Restore. Backup stores a copy of your save file in your own Google Play Games account storage; Restore fetches it back (for example on a new phone). The backup lives in your Google account, not on our servers; we cannot read it. Leave the toggle off and your progress never leaves your device. On iOS there is no cloud backup: your save stays on the device.
On Android, the game may also ask Google Play to show its standard rate-this-game card after your first prestige; that flow is run entirely by Google Play. If usage statistics are on, the game records that it asked, and whether Google Play's flow then finished or could not start. Google Play does not tell the game whether the card was actually shown, or anything you rated or wrote, so none of that is recorded.
Idle reminders (local notifications)
While Settings → “Idle Reminders” is on (it is on by default, and you can turn it off at any time), the game schedules reminder notifications (for example, “your forge is full”) entirely on your device. The reminders themselves are scheduled and delivered locally: nothing is scheduled remotely, and the notification text never leaves your device. Where the phone needs your permission to show notifications (Android 13+ and iOS), the game never asks for it out of the blue. It first asks in its own words whether you want to be told about something specific (for example, when the master's order will be ready), just after the tutorial ends or when you come back to something still under way. On Android it may ask once more on a later day if reminders still aren't allowed; after that it stops asking. The system's own permission prompt appears only if you say yes, or if you turn the Settings toggle on yourself. Reminders are cancelled whenever you're actually playing.
If usage statistics are on (see above), we do record that a reminder was scheduled, opened, or swiped away, and which of the handful of reminder kinds it was, and whether you said yes or no to the game's question about reminders and at which moment it was asked, so we can tell whether reminders are useful or merely annoying, and drop the ones nobody wants. That record is part of the same anonymous event stream described above and is covered by the same opt-out; turn usage statistics off and reminders keep working with nothing recorded.
Children
Forge Clicker is intended for players 13 and older and is not part of any child-directed program (e.g. Google Play's Designed for Families or Apple's Kids Category).
Changes
If a future update changes any of the above, this policy will be updated before that version ships, and the Play Store Data Safety section and App Store App Privacy answers will be revised to match.