Privacy Policy
Idle Forge is an idle/clicker game. It has no accounts and no sign-in. This policy describes the small amount of data that is involved in running it, including the anonymous play statistics and crash reports you can switch off.
Data the game itself handles
Your game progress is stored only on your device. Saves live in the app's private storage. We (the developer) never receive, see, or store your progress.
- Save codes. You can export your progress as a text code from Settings. The code contains only game progress (resources, upgrades, timestamps). It is placed on your clipboard and goes only where you choose to paste it.
- Settings (sound, notifications, display options) are stored on your device only.
- Reminders. If you enable them, the game schedules local notifications on your device. Nothing is sent anywhere.
- Clock check. To keep offline earnings fair, the app may contact a server to read the current time. This request carries no personal data and no game data; only a timestamp is read back.
- Deleting your data. Use Settings → Reset all progress, or uninstall the app. Because everything is on your device, that removes it completely.
Advertising (Google AdMob)
Idle Forge shows ads through Google AdMob (the Google Mobile Ads SDK). All rewards offered by ads can also be earned by simply playing.
Like most ad SDKs, Google's SDK may collect and process:
- Device identifiers, including the advertising ID
- IP address (which implies approximate location)
- Device and app information (model, OS version, app package)
- Ad interaction data (impressions, clicks) and diagnostics
This collection is performed by Google under Google's own policies:
- How Google uses data from apps that use its services
- Google Privacy Policy
- Ad personalization controls
Consent (EEA/UK). Where the GDPR applies, a consent form is shown before any ad is requested. You can change or withdraw your choice at any time in Settings → Ad privacy settings. Declining personalized ads does not remove any game content: ads only ever offer shortcuts.
App Tracking Transparency (iOS). On iPhone and iPad the game asks for permission to track before the consent form, using Apple's App Tracking Transparency prompt. Saying no keeps every feature and every ad; the ads are simply less tailored. You can change the answer at any time in the iOS Settings app, under Privacy & Security → Tracking.
Analytics and crash reports
To see how the game is played and where it breaks, Idle Forge sends anonymous play statistics to Amplitude and crash reports to Sentry. Both are optional: Settings → Privacy → Usage statistics switches them off together, at any time, and nothing is recorded after that.
What is sent:
- Play statistics: which things were bought or unlocked and when, session length and the number of anvil strikes per session, ad button use and whether an ad paid out, the estimated value of an ad impression, and changes to the settings toggles.
- Crash reports: the error or crash, the game's own log lines, and the device model and OS version.
- A random install id. Generated once when the game is first opened and stored on your device. It is not an advertising id, not linked to any account, and a progress reset keeps it so the same phone stays the same player. Uninstalling removes it.
- Technical details: app version, platform, OS version, device model and language. Your IP address reaches these services in transit, as with any internet request, and is not stored by the game.
What is never sent: your save, your name or contact details, precise location, or any advertising identifier.
Amplitude (in the United States) and Sentry (in the European Union) process this data on the developer's behalf, under their own policies:
Where the GDPR applies, statistics are held back until the ad consent form has been answered, and the switch above withdraws them at any time.
Children
Idle Forge is not directed at children under 13. Ad content is configured for a general audience.
Changes
If this policy changes (for example, if a cloud-save option is added), the updated version will be published at this address with a new effective date.
Contact
Questions about this policy: tobdev237@gmail.com