Privacy Policy
Last updated: October 30, 2026
1. Introduction
Welcome to Idle Forge.
This Privacy Policy explains what information Idle Forge collects, why, how it is used, who receives it, how long it is kept, and what choices and rights you have.
Idle Forge is published under the name Pieters Studios by Solusiv, the sole proprietorship (eenmanszaak) of Joey Pieters, registered with the Netherlands Chamber of Commerce (KvK) under number 67882552, Haselackers 49, 7824 LL Emmen, the Netherlands. Solusiv is the controller of the personal data described here; in this policy "Pieters Studios", "we" and "us" mean Solusiv. You can reach us about privacy at privacy@pietersstudios.com. We have not appointed a data protection officer; the law does not require one for a business of our size and kind.
2. Information We Collect
Idle Forge does not ask you to register. When you first start the game it creates a game account for you automatically, so your progress can be saved online.
Account and identifiers
- An Idle Forge player account identifier, created for every player at the first session
- A player name. The game generates one for you; you can change it in your profile
- An avatar you choose from the game's own set. It is not a photo
- A cloud identity identifier and a local installation identifier, used to recognise your device and sign your requests
- An invite code and a public profile reference. Both are random-looking codes that stand for your game account; they do not contain your name or contact details
- If your device is signed in to Apple Game Center or Google Play Games: the player identifier and display name that service gives the game (see section 6)
- If you open Forge Chat, clans or another social feature, or choose your own player name: the result of the age question (your age band, where the answer came from and when) and, if you answered while under 18, the month from which you count as 18. We never store the birth month and year you enter, but that month shows the month and year of birth (see "Age check for social features" in section 5)
- Where your app store reports it: whether a parent or guardian must approve chat for you, their decision, and identifiers of the app installation that Apple gives the game (see "Age check for social features" in section 5)
- When the game proves its app store age check to our server (see "How the game proves the store's answer" in section 5): which platform the last proven check came from and when, and on iPhone and iPad an identifier of the key that Apple's App Attest service created for that installation of the game
- If you report something: a short status line for each report, which you can read in the game under Forge Chat › Activity (see "Clans, Clan Chat and moderation" in section 5)
Gameplay
- Your game progress: currencies, equipment, forge level, world and stage, abilities, souls, dungeon and contract progress, settings and notification preferences
- Your public Hero profile, your ranking entries and your activity entries (see section 5)
- Your friends in the game, when you last played (rounded to a few minutes), and who invited whom (see section 5)
- Messages from the team that you received and claimed
- If you use clans: your clan and your role in it, what you write in Clan Chat, Clan Rules or a clan name, the reports you make and the players you block (see "Clans, Clan Chat and moderation" in section 5)
- If you use World Chat: what you write there and when, the recruitment cards you post, the reports you make and the players you block (see "World Chat" in section 5)
Purchases
- For each in-app purchase: the product, the store's transaction identifier, the purchase time and status, and the platform. On Google Play the purchase token is kept only as a one-way hash
- If a purchase is refunded by the store: a record of the refund, what was taken back, and your balances before and after, kept with your game account (see section 8)
Device, usage and diagnostics
- Device model, operating system, app version and language
- Approximate country or region, which Firebase derives from your IP address. The game itself does not read or store your IP address or your location
- App instance identifiers that Firebase uses to measure app usage
- Idle Forge does not read your device's advertising ID (Android advertising ID or Apple IDFA)
- Gameplay events, such as progression, crafting, boss completion, rewards, shop views and feature usage
- Purchase events: the product, price and currency, and a purchase reference that is created on your device and cannot be matched to our purchase records
- Which of our own advertising campaigns led to an install, where the store provides it (see section 3)
- Crash reports, handled errors, app hangs, startup timings and other diagnostic events
- If you allow clan notifications: a push notification token for your device (see section 7)
Idle Forge does not collect or ask for:
- Your real name
- Your email address or phone number
- The contacts, photos or messages on your device (the messages you write in Clan Chat or World Chat are described in section 5)
- Precise GPS location
- Payment card information
If you contact us by email, we receive your email address and your message. When you start a support email from inside the game, the draft already contains technical details that help us find your account: app version and build, platform, operating system, device model, your player support ID, your save identity and your current progress. You can read and remove these lines before you send the email. We use support emails only to respond to your request.
When you visit our websites (idleforgegame.com and pietersstudios.com), our hosting provider records standard server logs: your IP address, the time, the page requested, the referring page and your browser type. We use them only to keep the websites running and secure. Our websites use no cookies, no analytics and no third-party scripts.
3. Analytics, Crash Reporting and Advertising Measurement
Idle Forge uses:
- Firebase Analytics (Google)
- Sentry, for crash and error reports
- Firebase Crashlytics (Google), for crash reports
These services help us:
- Understand how players use the game
- Improve gameplay balance
- Detect crashes
- Monitor handled errors and cloud-save reliability
- Improve performance
- Fix bugs
Firebase collects technical device information (such as device model and operating system), app instance identifiers and, on iOS, Apple's identifier for vendors, gameplay and purchase events and approximate location (country, region and city, which Google derives from your IP address; Google does not store the IP address of users in the European Union), according to Google's Privacy Policy. Analytics events never contain your player name, your player account identifier, your Game Center or Google Play Games identifier, your friends, your invite code or anything you write in chat. We do not set a user ID in Google Analytics and the game does not read your advertising ID. A purchase event carries the product, its price and currency, and a purchase reference: from version 1.13.0 this is a one-way hashed reference created on your device with a key that never leaves it, so it cannot be linked to your game account or to our purchase records. Versions up to 1.12.0 sent the store's transaction identifier instead. Those identifiers are still on the older purchase events, in Google Analytics and in our analytics copy in Google BigQuery, until they are removed: at the latest when the 14-month retention removes those events, by the end of 2027. We do not use them to connect analytics to players. A copy of these analytics events is exported to Google BigQuery in the European Union, where we analyse them; the export holds the same pseudonymous data. Google Analytics starts when you first open the game, before the game knows your age; for a player we learn is under 13 it is switched off, as described in section 14.
Idle Forge sends crash reports to two services: Sentry and Firebase Crashlytics (Google). Crashlytics receives a report when the game crashes or records an error: the error and where in the game's code it happened, the app version, the device model and operating system, and a Crashlytics installation identifier. Crashlytics reports contain no player name, player account identifier or anything you write. Sentry receives a report when the game crashes, stops responding or records an error: the error and where in the game's code it happened, the app version and build, the platform, the device model, operating system and version, memory and other technical state of the device at that moment, timestamps and recent log lines needed to investigate the problem. We have configured Sentry not to send personal information by default, not to attach screenshots, to remove the device name you gave your phone and your IP address before an error report is stored, and to store its data in the European Union (Frankfurt, Germany). We do not attach your player name, your player account identifier or your Game Center or Google Play Games identifier to crash and error reports.
Analytics and crash reporting do not use advertising identifiers and are not used to show you ads. In Google Analytics we have switched off data sharing with Google's other products and services, and we tell Google through its Consent Mode that the data may not be used for ad personalisation or remarketing, so Google may not use the data for its own purposes.
Idle Forge is built with the Unity game engine. The engine sends Unity Technologies anonymous technical statistics about the device's hardware and software, such as the device model, operating system, processor, graphics chip and memory. They contain no player name, account identifier or gameplay data, and Unity processes them under its own privacy policy: https://unity.com/legal/privacy-policy.
We use analytics, crash reporting and diagnostic data to understand app usage, reliability and stability. We do not sell this data.
Advertising
Idle Forge shows no third-party advertisements in the game, does not use the Apple Identifier for Advertisers (IDFA), does not ask for permission to track you, and does not track you across other companies' apps and websites.
We advertise Idle Forge itself, for example through Apple Search Ads and Google Ads. To learn which of our campaigns bring players to the game:
- On iOS, the game asks Apple for an attribution record of the install. If the install came from one of our Apple Search Ads, the game records the campaign, ad group and keyword identifiers in analytics. This record does not identify you to us.
- On Android, Google Play tells the game whether an install came from one of our Google Ads campaigns, through the Play install referrer. Analytics then records the campaign and Google's click identifier for that ad click. The game does not read your advertising ID for this.
- On Android, the game can read the Google Play install referrer to see whether you arrived through a friend's invite link. It keeps only the invite code.
Our Google Analytics property is linked to our Google Ads account. From the Android version, Google Ads receives four analytics events as conversions: the first craft, the first boss defeated, completing World 1, and a purchase (its price and currency). Google Play also tells Google Ads about installs from our campaigns. We use these conversions only to see which of our install campaigns bring players who keep playing. We do not use analytics data for advertising audiences or remarketing, and ad personalisation is switched off as described above.
For a player under 13, the game switches off Google Analytics and these attribution reads on the device (see section 14).
Google Privacy Policy: https://policies.google.com/privacy
Sentry Privacy Policy: https://sentry.io/privacy/
4. Local Save Data
Idle Forge stores gameplay progress locally on your device.
This may include:
- Coins
- Gems
- Arcane shards
- Equipment
- Forge level
- World progress
- Boss progress
- Ability research progress
- Daily dungeon progress
- Contract progress and rewards
- Inventory
- Settings
- Notification preferences
This information is used solely to provide gameplay functionality.
5. Cloud Save and Online Features
Idle Forge uses online services and Cloud Save to back up, restore and protect gameplay progress across installs or devices.
Cloud Save stores the same types of gameplay progress listed in the Local Save Data section, together with technical sync data such as:
- A local installation identifier
- A cloud identity identifier
- Your Idle Forge player account identifier and player name
- Save version and revision numbers
- Save creation, last played and last sync timestamps
- Conflict or migration status used to avoid overwriting progress
- Limited save summaries, such as forge level, world, stage, coins and gems, when needed to help you choose between local and cloud progress
Idle Forge currently uses Amazon Web Services, including Amazon Cognito and the Idle Forge backend API, to issue temporary credentials, authenticate cloud-save requests, run server-authoritative gameplay actions, check required app versions and store save data. Cloud-save data is used to provide backup, restore, sync, account linking, update checks, abuse prevention, anti-cheat, migration and support functionality. The data is stored in the European Union (Frankfurt, Germany).
Cloud Save does not give the game access to the contacts, photos or messages on your device, to precise GPS location or to payment card information.
Public profile and rankings
Other players can see your public Hero profile: your player name, avatar, current world, forge level, combat power, equipped items and hero stats. It is shown in the in-game rankings, in the activity feed (for example when you reach a new world) and to your friends. It does not include your real name, contact details or your player account identifier. Other players' games refer to your profile by a public reference code that stands for your account without revealing it.
A Hero profile that has not changed for 90 days is removed. Ranking and activity entries carry your player name and avatar and are removed automatically: weekly leaderboard entries after 180 days, Power Ranking entries after 90 days and activity entries after 30 days. When you delete your account they are removed straight away (see section 11).
Friends
You can add friends in the game. Idle Forge stores who your friends are, since when, and whether you met through an invite or by entering a friend's code. Friends can see each other's player name, avatar, public profile and whether the other has played in the last few minutes ("Online"). To show this, Idle Forge records when you last used the game, rounded to a few minutes, and deletes that record after one day; the time itself is never shown to other players. You can have up to 100 friends and remove a friend at any time, which ends the friendship for both of you. Idle Forge never reads the contacts on your device.
Forge Together invitations
Every player has one invite code, which can be shared as a code, a link or a QR code. The code does not contain your name or contact details, but it stands for your game account: whoever enters it is connected to you. If a new player enters your code, Idle Forge stores which player invited them and when, and when they cleared World 1, and the two of you become friends. The player who invited you sees your player name, avatar and World 1 progress and, while you are friends, your current world, forge level, combat power and online status; you see the same for the friends who entered your code. A player who already plays can enter your code to add you as a friend, which is not an invite. The top three players of an event are shown in the game with their player name, avatar and number of successful invites, and we may name them with the same details in our community announcements. See the Forge Together rules.
Clans, Clan Chat and moderation
You can found or join a clan. Players write three things in clans: the clan name (typed by the player who founds the clan, or picked from the game's suggestions), the Clan Rules (written by the Clan Lead) and Clan Chat (written by members). Before you can write in Clan Chat or Clan Rules, the game asks you to agree to the Community Rules.
When you use clans, Idle Forge stores:
- Clan membership: which clan you are in, your role (Lead, Captain or member), when you joined, when you last played, and your part in the clan's weekly Marks and wars
- Clan Chat messages: the text, when it was sent, who sent it and their role at that time, and up to which message you have read
- Clan Rules and clan names: the text and when it was last changed
- Your agreement to the Community Rules, and which version you agreed to
- Reports: who reported, what was reported (a message, a clan's rules or a player), the reason chosen, and a short excerpt of the reported content
- Blocks: which players you blocked
- Report status: for each report you make, a line saying that it was received and, once a person has decided on the case, whether action was taken. It never names the other player, the content or what the action was. Only you can read it, in the game under Forge Chat › Activity. Each line is deleted after 90 days, or earlier with your account. Players under 13 get none
- Moderation records: messages hidden by the filter or by a moderator, mutes, warnings, chat suspensions and bans on your account; moderation cases; and a log of every moderation action with who took it, when and why
Everything you write is checked automatically when you send it. Links and contact details are refused, words that are not allowed are hidden or refused, and the number of chat messages you can send per minute is limited. We do this to keep clans safe and free of spam.
Who can see what
- Your clan's chat can be read only by the members of your clan. Each message shows your player name, avatar and role.
- Any player who looks at a clan can see its name, its Clan Rules and its members' player names, avatars, roles, forge level and combat power.
- Inside the clan, members also see each other's world, weekly Marks, when each member was last active, and whether a member is currently muted in chat.
- Who you block is never shown to anyone. Blocking only changes what you see.
- Who reported something is never shown to the reported player, to the clan or to any other player, including Clan Leads and Captains. Only our moderation team can see it.
Moderation
Reports, moderation cases and the moderation log are read by our moderation team: the studio owner and any moderator the owner adds. Moderators work in a separate moderation tool. Nobody can create their own moderator account, and every moderator sign-in requires a password and a second factor (multi-factor authentication). When a case opens, it keeps a copy of the reported content and of up to 10 messages before and after it, so the conversation can still be understood after the chat itself has expired. Clan Leads and Captains can also remove messages and mute members inside their own clan. Our moderators can hide content, warn a player, mute a player, suspend a player from chat for a number of days, ban a player from chat permanently, and undo each of these. Every moderation action is logged.
When a case opens, the moderation team gets a notice through Discord and by email. A notice contains only a case reference, the kind of case, the report categories, the number of reports and reporters, and the time. It never contains chat text, player names, clan names or account identifiers; the details can only be read in the moderation tool after signing in.
Server logs and analytics events about clans record what kind of action happened, for example that a message was sent or a report was filed. They never contain the text of a message or who reported whom.
Clan data is stored by Amazon Web Services in the European Union (Frankfurt, Germany), like the rest of your game account.
World Chat
World Chat is a chat room for all Idle Forge players aged 13 and over. It works like Clan Chat: you agree to the Community Rules first, you need forge level 10 and an account that is at least 3 days old to write, everything you write is checked automatically, our filter refuses the links and contact details it recognises, and you can report and block other players and delete your own messages. Every player who opens World Chat can read what you write there, with your player name, avatar and forge level and the name of your clan, and can open your public Hero profile from it. A clan's recruitment card shows the clan's name, banner, members and settings, and the player name of whoever posted it. Idle Forge stores the text, when it was sent and who sent it, and your World Chat status, for example a mute. World Chat messages are removed from the chat after 24 hours (see section 11). When two different players report the same message, or one player who can take part in the chat reports it for a threat, self-harm or child safety, it is hidden for everyone until a moderator has looked at it. Reports and moderation work as described above for clans.
Age check for social features
Clans, Clan Chat, World Chat, choosing your own player name, and adding friends or using Forge Together are for players aged 13 and over. The game does not ask your age when you start it. It asks the first time you open Forge Chat or another of these features, or when you choose your own player name.
Your app store's age information. From version 1.16.0, on devices where Apple or Google offer it (Apple's Declared Age Range on iOS 26.2 and later, and Google Play Age Signals), the game asks your app store for your age range when you open these features. If the store gives a clear answer, the game uses it instead of asking you. A store answer can fill in your age band or make it stricter, never looser. We use this information only to give you the features that fit your age, never for analytics, advertising or profiling, and we do not store the store's response itself, only the result described below.
A parent's approval. In some places, such as Texas, the law requires the app store to ask a parent or guardian to approve a new feature for a player under 18. Where your app store tells the game that approval is needed, chat (World Chat and Clan Chat) stays closed until the parent or guardian approves it in the store, and closes again if they withdraw it. The rest of the game is not affected.
How the game proves the store's answer. From version 1.16.0, the game proves to our server that the store's answer came from the genuine, unmodified Idle Forge app on a genuine device, so that a modified copy of the game cannot fake it. Our server gives the game a one-time code. The game asks Google Play (Play Integrity) or Apple (App Attest) to sign a summary of the store's answer together with that code, and our server checks the signature itself; it does not contact Google for this. Google and Apple handle that request on your device under their own terms. A proven check shows only that the genuine game on a real device reported this answer for your game account, once. It does not prove your age or that a parent approved: those remain your app store's own statements. Only a proven answer can open chat once your app store has said that a parent's approval or an age check is needed; an unproven message from the game can only keep chat closed.
A proven check counts for 24 hours where Google Play says a parent's approval applies, and for 7 days otherwise; after that the game checks again, without asking you, when you open Forge Chat. A check that fails because of a temporary problem is not sent to our server: chat stays closed on that device and the game tries again the next time you open Forge Chat. On a device that cannot produce such a proof, for example one without Google Play services, chat can stay closed where our server requires a proven check. The rest of the game is not affected.
Why we ask. We use your birth month and year to determine which features are available for your age. We don't ask for your exact birthday. After you choose a month and year, the game asks you to confirm them, so that a wrong tap does not close features by mistake. The same confirmation appears for every answer.
What we store. We do not store the month and year you enter. Our server works out the result and stores that with your game account:
- your age band: under 13, 13 to 17, or 18 and over;
- where the answer came from (your own answer, Apple or Google) and when it was given;
- if you are under 18: the month from which you count as 18, which is the first day of the month after the month of your 18th birthday. The game uses it to open social features at 13 and to treat you as an adult at 18 without asking again. For a player under 18 this date shows the month and year of birth, so we treat it as confidential: it is never shown to other players or sent back to the game, it is never sent to analytics, crash reporting or advertising, our moderators see only the age band and its source, and only the studio owner can see it in our database. If the answer came from your app store, or you were 18 or over when you answered, we store only the band. If you answered while under 18, the month stays in the record after you turn 18; we do not use it for anything else;
- whether the answer has been reset through support (see "If the age was entered wrongly" in section 14);
- where your app store says a parent's approval is needed: that it is needed and which store said so, the decision (approved, declined or withdrawn), where the decision came from, which feature it covers (chat) and when;
- whether your age band and a parent's approval came through a proven check, and which platform your last proven check came from and when;
- on iPhone and iPad: the identifier and public key of the App Attest key that Apple created for that installation of the game, with a counter, so that our server can check later proofs from it. A key can be linked to at most 10 game accounts;
- on iOS, when a parent approves: the identifiers Apple gives to the installation of the game on that device (the app transaction identifier). We keep them so that, if the parent later withdraws the approval and Apple tells us which installation it concerns, we can close chat again on every game account that installation was used with.
We do not keep the Play Integrity token, Google's assessment of your device, the store's age range itself or a one-time code once it has been used; an unused code expires after 10 minutes. We use this record only to apply the age rules and the parent's decision, and to show that we did. We keep it, including the Apple installation identifiers and App Attest key identifiers, with your game account for as long as the account exists and delete it when the account is deleted. An App Attest key that no other game account uses is deleted with it; the key itself contains no information about you. When a parent withdraws an approval, we keep a note of the installation's app transaction identifier and the time Apple told us the approval was withdrawn, without any link to a game account and without anything else Apple sent, so that the same withdrawn approval cannot be presented again. We keep this note only while it is needed for that, and delete it at the latest two years after that installation was last linked to a game account. Deleting the note never makes the withdrawn approval valid again: every game account it was withdrawn for keeps the withdrawal. What happens for a player under 13 is described in section 14.
6. Apple Game Center and Google Play Games
Idle Forge uses Apple Game Center on iOS and Google Play Games on Android to link your game account to your platform account, so your progress can be restored on a new device.
If your device is signed in to one of these services, the game links your game account to it automatically when it starts. You do not have to press anything. If you do not want this, sign out of Game Center or Google Play Games for Idle Forge in your device settings.
The game receives and stores:
- The player identifier the platform gives the game
- On Android, the identifier of the Google account behind your Google Play Games profile
- Your display name, alias or gamer profile name (up to version 1.15; from 1.16.0 the game no longer stores it, and a name stored earlier is removed the next time the link is used)
- Authentication result, server authorization code, signature, salt, timestamp or similar verification information needed to verify the platform account
Idle Forge does not request or receive your email address from Apple or Google.
We use this information only to link or restore game progress, resolve account-link conflicts, prevent abuse and support your account. We do not use platform profile information for advertising or marketing. Apple and Google process your platform account information according to their own privacy policies.
Apple Privacy Policy: https://www.apple.com/legal/privacy/
Google Privacy Policy: https://policies.google.com/privacy
7. Notifications
Idle Forge may ask for permission to send optional notifications. Most are local notifications: they are scheduled on your device and nothing about them is sent to a server.
Notifications may be used to remind you when:
- A forge upgrade is ready
- Your offline reward is full
- Arcane Forge research is complete
- A soul has finished summoning
- Daily dungeon keys are ready
If you are in a clan and allow notifications, the game can also tell you when a clanmate mentions you in Clan Chat. For this, your device gives the game a push notification token, which we store with your game account and send, through Google Firebase Cloud Messaging (and Apple's push service on iOS), only to deliver these notifications. The notification shows the clan name and the name of the player who mentioned you. The token is deleted 90 days after it was last registered, when you delete your account, and for a player under 13 (see section 14).
You can allow or disable notifications at any time in the game's settings and in your device settings.
Idle Forge does not use notifications to collect location data or to track you across apps and websites.
8. In-App Purchases and Refunds
Idle Forge offers optional in-app purchases for digital game content such as virtual currency, resource bundles, dungeon keys and permanent unlocks.
Payments are processed securely by the relevant app store:
- Apple App Store
- Google Play Store
To validate purchases and grant rewards, Idle Forge processes purchase-related information such as product identifiers, transaction identifiers, purchase tokens, purchase status, platform, timestamps and entitlement status. This information is used for purchase validation, reward delivery, restore functionality, fraud prevention, support and legal compliance.
If Apple or Google refunds a purchase, the store tells us, and the content of that purchase is taken back from your game account. Idle Forge keeps a record of the refund with your account: the product, the time, what was taken back and your balances before and after. Repeated refunds of delivered purchases can lead to a warning and, after that, to purchases being suspended for the account. These records are used for fraud prevention and support.
We never receive or store your payment card information.
9. How We Use Information, and on What Legal Basis
Collected information is used to:
- Improve gameplay
- Balance progression
- Improve game stability
- Fix crashes
- Improve performance
- Develop new features
- Back up, restore and synchronize gameplay progress
- Provide account linking through supported platform services
- Run online gameplay actions and reconcile progress safely
- Provide rankings, friends and invitations
- Provide clans and Clan Chat, World Chat, and keep them safe: filter what players write, handle reports and blocks, and moderate
- Apply the minimum age of 13 for social features, and protect players under 13 (see section 14)
- Check whether an app update is required for your platform
- Validate purchases, handle refunds, and detect abuse and cheating
- Measure which of our own advertising campaigns bring players to the game
- Improve the overall player experience
Where the General Data Protection Regulation (GDPR) applies, we rely on these legal bases:
- Performing our agreement with you (the Terms of Service): your game account, cloud save, online gameplay, rankings, friends, invitations, purchases and support
- Our legitimate interests in keeping the game working, secure and fair, and in understanding how it is used: analytics and our analytics copy in Google BigQuery, crash and error reporting (Sentry and Firebase Crashlytics), the game engine's hardware statistics (Unity), fraud and abuse prevention, refund records and our team's internal alerts (Discord), server logs and our websites' server logs, and measuring our own advertising campaigns (Apple Search Ads attribution through Apple's AdServices, the Google Play install referrer and Google Ads conversions)
- Performing our agreement with you, at your request: clan notifications, when you allow them (push notification tokens, Firebase Cloud Messaging and Apple's push service)
- Our legitimate interest and, for requests about your rights, our legal obligations: answering your support and privacy emails and keeping them as a record of how we handled your request
- Legal obligations, for example keeping records of purchases where tax or consumer law requires it
- Legal obligations and our legitimate interest in protecting children: your age record and any parent's approval record, including the Apple installation identifiers, and the proven store checks with their App Attest key identifiers (section 5), and the protected mode in section 14
- Legal obligations under the EU Digital Services Act: the report status lines that confirm your reports and tell you our decision (section 5)
For clans and World Chat we rely on:
- Performing our agreement with you: your clan membership and role, Clan Chat, World Chat, Clan Rules, clan names, blocks and your agreement to the Community Rules, because that is how these features work
- Legal obligations under the EU Digital Services Act: handling notices of illegal content, telling you why we restricted something you wrote, and informing the police when someone's life or safety may be at risk
- Our legitimate interest in keeping players, especially younger players, safe from harassment, threats, sexual content, scams and repeated abuse: the automatic filter, automatic short mutes, reports, moderation cases, moderation actions and the moderation log, and keeping that evidence for a limited time. We have weighed this interest against your privacy, with extra care for players under 18, and limited what we keep and for how long
You do not have to use clans or chat to play Idle Forge. If you do, we need the data listed in section 5 to provide them.
Automatic decisions
Our filter decides automatically whether a message is refused or hidden; in World Chat, a message that two different players report is hidden automatically until a moderator looks at it, and so is a message or Clan Rules text that a player who takes part in that chat reports for a threat, self-harm or child safety; and three hidden or removed messages within 7 days lead to an automatic chat mute of 24 hours, 3 days or 7 days. These decisions only affect chat, they are temporary, and nothing else in the game changes. A person reviews any of them if you ask: email support@pietersstudios.com with the subject "Moderation appeal". We do not use automatic decisions for anything else, and we do not profile you.
10. Data Sharing
We do not sell your personal information.
Information is processed by service providers required to operate, analyze, secure and improve the game:
- Amazon Web Services: game accounts, cloud saves, online features and server logs, stored in the European Union
- Google Firebase: analytics, crash reporting (Firebase Crashlytics) and delivery of clan notifications (Firebase Cloud Messaging)
- Google Ads: measuring our own install campaigns with the conversions described in section 3. Google Ads receives no player name, account identifier or advertising ID from us
- Sentry: crash and error diagnostics, received in the European Union
- Unity Technologies: anonymous hardware and software statistics sent by the game engine (section 3)
- TransIP (the Netherlands): hosting of our websites and our email
- Discord (United States): our team's internal alert channel. Alerts about a refund or a purchase problem contain a shortened one-way hash of your account identifier, the product and the amounts involved, so that we can act on them. They do not contain your player name or your account identifier. Notices about a moderation case contain no personal data: no chat text, no player or clan names and no account identifiers
- Police and other authorities: only when the law requires it, for example when we suspect a crime that threatens someone's life or safety (Article 18 of the Digital Services Act), and only the information that is needed. We report suspected child sexual exploitation or abuse to the US National Center for Missing & Exploited Children (NCMEC), which passes reports on to the competent police, including the UK's National Crime Agency, and, where it applies, to the Dutch police and Offlimits (the Dutch hotline)
If you use Apple Game Center or Google Play Games, relevant platform account information is processed by Apple or Google to provide those platform services.
If you make an in-app purchase, purchase-related information is processed by Apple or Google and by Idle Forge services to validate the purchase and deliver the correct game content.
Some of these providers are based in the United States or may process data there. Game accounts, cloud saves, clan data, moderation records and the age record stay in the European Union (AWS, Frankfurt). Sentry stores its data in the European Union. Our analytics copy in Google BigQuery is stored in the European Union. Google (Firebase, Google Analytics, Firebase Crashlytics, Firebase Cloud Messaging and Google Ads) may process data in the United States: Google LLC is certified under the EU-U.S. Data Privacy Framework, for which the European Commission has decided that the protection is adequate, and Google's data processing terms also include the European Commission's standard contractual clauses. Where another provider processes data for us in the United States, we rely on its certification under the Data Privacy Framework or on the standard contractual clauses in its data processing terms. Discord stores our alerts in the United States; they contain only the shortened one-way hash described above, never a player name or account identifier. Apple (App Store, Game Center, App Attest, its push service and AdServices), Google (Google Play, Google Play Games and Play Integrity), Discord and Unity Technologies process data under their own terms and privacy policies as independent companies. Our websites and email are hosted by TransIP in the Netherlands.
We may disclose information if required by law or to protect the security and integrity of Idle Forge.
AWS Privacy Notice: https://aws.amazon.com/privacy/
Sentry Privacy Policy: https://sentry.io/privacy/
Discord Privacy Policy: https://discord.com/privacy
11. Data Retention and Deletion
We keep personal data only for as long as we need it for the purpose we collected it for. Local save data remains on your device unless you delete the app or clear the app data through your device settings.
How long we keep data
For as long as your game account exists: your game account and its identifiers, cloud save and progress, settings, player name and avatar, platform account links, friends, invitation records, clan membership, Community Rules agreement, blocks, purchase records and refund records, your age record, any parent's approval record, your store-check record and the App Attest key identifiers linked to your account (section 5).
Removed automatically after a fixed period:
- Online status: after one day
- Activity feed entries: after 30 days
- Public Hero profile: 90 days after it last changed
- Power Ranking entries: after 90 days
- Weekly leaderboard entries: after 180 days
- Clan Chat messages: after 7 days
- World Chat messages: removed from the chat after 24 hours and deleted from our database shortly after
- A chat message that has been reported: kept, hidden, as evidence while the moderation case about it is open, within the case period below
- Push notification tokens: 90 days after they were last registered
- Report status lines in Forge Chat › Activity: 90 days after they were written
- One-time codes for a store check: 10 minutes, or as soon as they are used
- History of your in-game transactions (what was earned, spent, granted or claimed, used to investigate missing items and lost progress): after 60 days
- Server logs: after 30 days. They identify a player only by a shortened one-way hash of the account identifier and do not contain your IP address
- Technical access logs of our game servers, which contain no IP address and no account identifier: after 7 days
- Moderation cases, including the copy of the reported content and the messages around it: up to 180 days, or until the period for appealing the decision has ended
- Reports (including a short excerpt of the reported content of at most 120 characters) and the moderation log: up to 180 days after the last decision
- Strike history and chat standing (warnings, mutes and suspensions): 2 years after the last strike or change. A permanent chat ban is kept for as long as the account exists
- Support emails with ordinary questions and bug reports: 12 months after the request is closed
- Emails about an account dispute, a parent's request or consent, or an appeal against a moderation decision: 24 months after the matter is closed
- Emails about a payment dispute: for as long as our bookkeeping and tax rules require us to keep them as records (up to seven years); emails about a serious safety incident: as described for evidence below
- Evidence we have reported to the police or another authority: until that authority no longer needs it, or for longer only where the law requires a minimum period. We keep the report's reference number separately, and keep the reported content itself only where the law requires it, stored apart from everything else
- Backups of our game database (used to restore data after a fault): 35 days
Analytics data in Google Analytics is kept for 14 months (for a player who keeps playing, counted from their last activity), and the analytics export in Google BigQuery, including any copy or table derived from it that can still be linked to an installation, for 14 months. Sentry crash and error reports are kept for 30 days, and Firebase Crashlytics crash reports are kept by Google for 90 days after they were received. After that they are deleted by those services. Website server logs are kept by our hosting provider only for as long as it needs them to run and secure the websites, and we keep no copies.
Deleting your account
You can delete your game account and the data that belongs to it in the game (Settings → Delete account) or by email; see the account deletion page. Deletion in the game happens straight away. We complete a request by email within 30 days and email you when it is done. Deleting cloud-save data makes it impossible to restore gameplay progress from the cloud.
When your account is deleted, we delete your cloud save, your player name, your friendships, your online status, your public Hero profile, your invitation records, your refund records, your age record and any parent's approval record, your store-check record and the links to App Attest keys (a key that no other game account uses is deleted too), your report status lines and your push notification tokens; your former friends no longer see you. When Google Analytics is running on the device at that moment, the game also resets its analytics identifier there, so new analytics data cannot be connected to the old data. Deleted data can remain in encrypted backups for up to 35 days before it is overwritten.
Your platform account links work differently. After deletion, the link between your Game Center, Google Play Games or Google sign-in (and your device's sign-in identity) and the deleted account no longer leads to any game account, but we keep the link record itself: it holds the platform's player identifier and the deleted account identifier, and makes sure the deleted account is never created again from the same sign-in. The platform display name stored with it is removed the next time that platform account is used with Idle Forge. We do not use these records for anything else.
When your account is deleted we keep a record of each in-app purchase (the store's transaction number, the product, the date and whether it was refunded) but no longer linked to your game account by name or account identifier. We keep these records for up to seven years after the end of the year of purchase, because Dutch tax law requires us to keep our administration for that period (Article 6(1)(c) GDPR), and so that we can handle refunds, chargebacks and disputes about a purchase. For this the record carries a coded (hashed) reference to the deleted account (our legitimate interest, Article 6(1)(f) GDPR). Purchase details that are not needed for these purposes are deleted with your account.
After deletion we keep a note of the account identifier and the date of deletion, so that the deleted account cannot come back to life and nothing we keep is linked to a new account. The note contains nothing else and is deleted two years after the deletion.
When your account is deleted we remove you from your clan (if you lead it, the next member in line becomes Lead; a clan with no other members is closed), hide the Clan Chat messages you wrote in your current clan and remove your name and avatar from them and from that clan's activity (the messages are deleted for good when the 7-day chat period ends), and delete your blocks and your Community Rules agreement. Your entries in the leaderboards, the Power Ranking and the activity feed are removed, and in finished Forge Together results your place shows as "Deleted player". Messages and activity in clans you left earlier keep your name until they expire (chat after 7 days, activity after 14 days). The account deletion page lists everything that is removed, anonymised or kept.
The World Chat messages you wrote are hidden straight away and your name, avatar and text are removed from them; a message that another player reported, or that an open moderation case uses, keeps its text, hidden, until the case no longer needs it or the message expires.
Reports made by you or about you, moderation cases and the moderation log are kept after your account is deleted for the rest of their normal period, listed above, because they are evidence we need to keep other players safe, to review decisions and to deal with repeated abuse. They are then deleted automatically. Your strike history and chat standing are deleted with your account. If we have reported something to the police or another authority, the evidence is kept until that authority no longer needs it, or for longer only where the law requires it.
12. Your Rights
Where the GDPR or a similar law applies to you, you have the right to:
- Ask what personal data we hold about you and receive a copy
- Have incorrect data corrected. You can change your player name and avatar yourself in the game
- Have your data deleted
- Object to processing that is based on our legitimate interests, or ask us to restrict it
- Receive the data you gave us in a portable form
- Ask a person to review an automatic decision (see "Automatic decisions" in section 9)
- Have your age record corrected if the age was entered wrongly (see section 14)
Some of this you can do yourself in the game: change your player name and avatar, turn notifications off, block players, delete your own World Chat messages, and delete your whole account (Settings → Delete account).
To use these rights, email privacy@pietersstudios.com and include your player support ID, which you find in the game under Settings. We may ask you to confirm the request from the game, so that nobody else can get or delete your data. We answer within one month. When we give you a copy of your data, we leave out information about other players, such as who reported you.
A parent or guardian can use these rights for their child in the same way.
You also have the right to complain to a data protection authority, in particular in the country where you live. In the Netherlands this is the Autoriteit Persoonsgegevens: https://www.autoriteitpersoonsgegevens.nl. In the United Kingdom it is the Information Commissioner's Office: https://ico.org.uk/make-a-complaint/.
13. Data Security
We take reasonable measures to protect information collected through Idle Forge.
All communication between the game and our services is sent over HTTPS and authenticated with temporary credentials. The game does not include long-lived AWS credentials. Stored game data is encrypted. Only the studio owner has access to the production systems. Moderators use a separate moderation tool that requires a password and a second factor, and every moderation action is logged. If a personal data breach happens that is likely to put you at risk, we report it to the Autoriteit Persoonsgegevens within 72 hours and tell you if the risk is high.
However, no method of electronic storage or transmission over the internet is completely secure.
14. Children's Privacy
Age and safety at a glance
- Chat and the other social features are for players aged 13 and over. The game does not ask your age when you start it; it checks the first time you open Forge Chat or another social feature, or choose your own player name.
- Where your app store offers it (Apple's Declared Age Range, Google Play Age Signals), the game asks the store for your age range. When the store gives a clear answer, the game does not ask you; otherwise it asks for your birth month and year.
- A player under 13 keeps playing in a protected mode: no chat and no other social features, while progress, purchases and the player's clan seat, role and rewards are kept.
- Where the law requires it, your app store asks a parent or guardian to approve chat; chat stays closed until they do. Purchases follow your app store's own parental controls, such as Apple's Ask to Buy and Google Play's purchase approvals.
- Our moderators can record a player as under 13 when they have reason to believe so, and can undo their own record. Every record and every undo is logged with a reason.
- Once the game knows that a player is in the protected mode, it sends no analytics to Google Analytics from that device.
The details follow below and in "Age check for social features" in section 5.
Idle Forge is intended for players aged 13 and over, and its social features are only for players aged 13 and over. If we learn that a player is under 13, their account is not closed: it continues in a protected mode without chat and other social features until they turn 13. We do not knowingly collect personal data from children under 13 beyond what is needed to provide and maintain the game, described below.
Before clans, chat, friends or a name of your own, the game asks your age (see "Age check for social features" in section 5). If we learn that a player is under 13, the player keeps full access to their game account: progress, purchases, sign-in and account recovery stay exactly as they were, so they can keep playing. The account switches to this protected mode:
- Social features are closed. The player cannot use Clan Chat or World Chat, choose their own player name, join or create a clan, add new friends or use invite codes. Their clan seat, role and rewards are kept.
- Hidden from other players at once. The name the player typed, their avatar, chat messages and social activity are no longer shown to anyone: leaderboards, clan rosters, mentions in chat, Forge Together lists and block lists show no name. An under-13 player never appears under a name they typed; they may appear under a generated name. Clan Rules the player wrote as a clan Lead are hidden. Pending clan applications are withdrawn. On leaderboards the player's row stays, without a name or avatar. If an entry with a name the player typed reappears because of an error on our side, we remove it as soon as we find it.
- Removed promptly. The player's push notification tokens, their entries in the activity feed, and their name and avatar on their clan's activity entries are deleted, and the player receives no push notifications.
- Analytics and ad measurement off. On that device, at the latest shortly after the game next starts and connects to our server, the game stops sending analytics to Google (Google Analytics for Firebase), does not ask Apple for a Search Ads attribution record, and does not read the Google Play install referrer.
- What we keep. Only what the game needs to work, stay secure and meet the law: the game account and its identifiers, progress, settings, purchases and refund records, the age record, moderation records, server logs, and crash and error reports in Sentry and Firebase Crashlytics, which contain no player name or account identifier (see section 3). These identifiers are used only to run the game, never for advertising or to build a profile.
Earlier analytics data deleted. When we learn that a player is under 13, the game sends its analytics identifier for that install to our server once. We then ask Google to delete the analytics data that device sent to Google Analytics before we learned the player's age, and we delete that install's rows from our own analytics copy in Google BigQuery. Because Google can still add data for recent days for up to three days, we check our copy again three days later and delete anything that has appeared since. Google completes its part under its own deletion process. An automatic deletion job does this work; for now our team starts that job by hand, until its schedule is switched on. We store the identifier without any link to the game account and delete it when the deletion is finished, and at the latest 60 days after we received it.
Moderators. Our moderators can record a player as under 13 when they have reason to believe so. The account then switches to the same protected mode. A moderator can undo their own record, giving a reason; every record and every undo is logged.
If the age was entered wrongly. Contact us at support@pietersstudios.com. The studio owner reviews each request, a correction can be made once per account, and every correction is recorded. Something that has already been removed, such as push notification tokens or activity entries, cannot be brought back.
At 13. If the player gave their birth month and year, the restrictions are lifted automatically from the first day of the month after their 13th birthday month: social features, the public name, notifications and analytics come back. If we learned the player's age from the app store or from our moderators, contact us at support@pietersstudios.com once the player has turned 13, and we will check again.
Players aged 13 to 17 can use clans and Clan Chat and World Chat. To protect them, the game refuses links and contact details in everything players write, there are no private messages, no images and no voice, and a report about the safety of a child goes to our team straight away.
If you believe that a child under 13 is playing, or that personal information has been collected from a child, please contact us and we will look into it.
Notice to parents in the United States (COPPA)
Idle Forge is not directed to children under 13, and we do not ask for or allow a child under 13 to share personal information with other players. When we learn that a player is under 13, we handle the account as described above and as follows.
Who we are. Solusiv, trading as Pieters Studios, Haselackers 49, 7824 LL Emmen, the Netherlands; email privacy@pietersstudios.com; telephone +31 6 35659049. No other operator collects personal information through Idle Forge.
Persistent identifiers used only for internal operations. For a player under 13 we use persistent identifiers only to support the internal operations of the game: the game account identifier, the device's installation and sign-in identifiers, the Game Center or Google Play Games player identifier, the App Attest key identifier on iPhone and iPad (used only to check the store age check, section 5), and the technical identifiers in crash and error reports. We use them to keep the account signed in and its progress saved and restorable, to deliver and restore purchases and handle refunds, to keep the game secure and prevent fraud and cheating, to enforce our rules and meet legal duties, and to find and fix crashes and errors. We make sure they are not used to contact the child, to build a profile of the child, or for advertising: on that device the game switches off Google Analytics and the reading of advertising attribution, the game never reads the device's advertising identifier, push notifications are switched off and their tokens deleted, crash and error reports contain no player name or account identifier, and no identifier is shared for advertising.
Who processes a child's information. Only service providers that run the game for us, for the internal operations above: Amazon Web Services (our servers and database, in the European Union), Sentry (crash and error reports without a player name or account identifier, stored in the European Union) and Google Firebase Crashlytics (crash reports with a Crashlytics installation identifier and without a player name or account identifier). The Unity game engine sends Unity Technologies anonymous hardware and software statistics (section 3). Apple and Google process purchases, sign-in and, where the law requires it, age and approval information as app stores, under their own privacy policies. We do not give a child's information to anyone for advertising.
How long we keep a child's information. We keep personal information of a player under 13 only as long as reasonably necessary for the purpose we collected it for, and then delete it:
- Game account, identifiers, progress, settings, purchases, the age record, any parent's approval record and the store-check record: for as long as the account exists, because the child keeps playing; deleted when the account is deleted in the game or at a parent's request. A record of each purchase, no longer linked to the account by name or identifier, is kept for up to seven years for our tax administration.
- A player name the child typed earlier: hidden from everyone at once and kept with the account only so that it can be shown again if the age was entered wrongly or when the player turns 13; deleted with the account.
- Chat messages the child wrote in World Chat and in their current clan's chat: hidden at once and deleted when the chat period ends (World Chat after 24 hours, Clan Chat after 7 days), unless a message is evidence in a moderation case. Messages in a clan the child left earlier are deleted when that clan's 7-day chat period ends.
- Push notification tokens and activity feed entries: deleted at once.
- If a child's account has not been used for 12 months, we review whether we still need the child's information. At the latest 24 months after the account was last used, we decide for each kind of information whether to delete it or make it anonymous, and record that decision. Purchase records we must keep for our tax administration follow their own period.
- The analytics identifier the game sends us to delete the child's analytics data: kept without any link to the account, for at most 60 days.
- Moderation cases and reports: up to 180 days; strike history and chat standing: 2 years after the last change; evidence we report to the police or another authority: as long as that authority needs it, or a minimum period the law sets.
- Emails from a parent or a child: 12 months after an ordinary question is closed; 24 months after a request about the account, consent or a moderation decision is closed. Please do not send us photos or screenshots that show a child; we do not need them and delete attachments we do not need.
- Server logs: 30 days. Crash and error reports: 30 days in Sentry, 90 days in Firebase Crashlytics. Database backups: 35 days.
Your rights as a parent. You can ask to see the personal information we hold about your child, have it deleted, and refuse further collection or use; refusing means the account is deleted. Email privacy@pietersstudios.com with your child's player support ID (in the game under Settings). We may ask you to confirm the request from the game, so that nobody else can get or delete the data. We never require a child to share more information than the game needs in order to play.
15. Changes to this Privacy Policy
We may update this Privacy Policy, for example when we add features or the law changes. We tell you about important changes in the game before they take effect.
The latest version will always be available at:
https://idleforgegame.com/privacy.html
16. Contact
If you have questions regarding this Privacy Policy, please contact us:
Email: privacy@pietersstudios.com
Thank you for playing Idle Forge.