What FlagForge keeps about you.
This covers flagforge.szalik.dev: your account, your licenses, the license server your FlagForge servers talk to, and the playtest pages. Last updated October 25, 2026.
szalik.dev runs FlagForge and decides what's done with this data. Write to kontakt@szalik.dev about anything on this page.
Your Discord user ID, username and display name, and when you first and last signed in. Signing in asks Discord only for these (the "identify" scope); FlagForge never sees your email, password or servers.
- WHY
- To sign you in and show the licenses that belong to you.
- KEPT
- Until you delete your account.
Which Discord account holds each license, its type, kind and dates, an admin's note about it, and for each key a one-way hash and its last four characters. The key itself is shown to you once and never stored.
- WHY
- To run the license you have: check its keys and its end date.
- KEPT
- As long as the license exists.
For the server each key runs on: its public IP address (for IPv6, only its /64 network), the instance ID FlagForge creates in its folder, its FlagForge version, the detection profile it was sent, and when it first and last checked in.
- WHY
- One license runs one server: this is how the license server knows which one, and refuses a copied key.
- KEPT
- While the server is bound to the key. It's unbound, and its address deleted, when you release it, when an admin does, or after 90 days without a check-in.
What happened to an account or license and when: sign-ins, keys created or replaced, downloads, servers bound, moved or refused, and admin changes. Each entry names the account that did it and the IP address it came from.
- WHY
- Security: to spot a shared or leaked key, to trace what changed a license, and to answer your questions about it.
- KEPT
- IP addresses are removed after 90 days, and entries deleted after 2 years. A deleted account's entries stay until then, so its record of what it did isn't rewritten.
From FlagForge 1.3.0, with each license request: per day, how often each check fired and how many of its findings staff confirmed or marked false, and which detection profile the server ran. Counts only: no player names, UUIDs, findings or chat. A server turns it off with telemetry.enabled: false in config.yml.
- WHY
- To see which checks misfire, and whether a new detection profile is better before it goes to every server.
- KEPT
- Per license for 13 months; after that only totals across all servers, which can't be traced to a license.
For each IP address that runs FlagForge's update check or asks for a license: the day, the FlagForge version it reported, and the license request's outcome.
- WHY
- To know how many servers run FlagForge, how many are licensed, and spot copies running without a valid license or in a version FlagForge never released.
- KEPT
- Addresses for 90 days; after that only each day's totals.
How many license requests came from each IP address in each hour.
- WHY
- To stop anyone hammering the license server.
- KEPT
- One day.
Each FlagForge jar you download is marked with your license ID, and the download is in the activity log.
- WHY
- So a leaked copy can be traced to the license it came from.
- KEPT
- The mark is in the file you keep; the log entry as above.
The reports you send from the playtest page: your name, Discord ID, FlagForge version, results, and your browser's user agent. A report with failed tests is also posted, with your name, to FlagForge's Discord channel. Whitelist requests for the test server keep the Minecraft name and who asked.
- WHY
- To track what was tested and fix what failed.
- KEPT
- Reports for 1 year. The last 30 finished whitelist changes are kept, older ones deleted.
The test Minecraft server's console log, sent to this site so FlagForge's owners can watch it: your Minecraft name and UUID when you join or leave, chat, commands and what the server says about you. Your IP address is removed before the log leaves the test server.
- WHY
- To see what happens during a playtest as it happens, and to run the test server.
- KEPT
- Log lines for 7 days, at most the last 5,000 of them.
On startup and every 6 hours, FlagForge sends its license key, its instance ID and its version to the license server, which sees the server's IP address; from 1.3.0 it adds the check counts above, unless telemetry is turned off. Its update check downloads a small file from this site listing the latest release, sending FlagForge's version, which is noted with the address as above. Nothing about your players is sent to this site: checks and their findings stay on your server, unless you set up Discord alerts to a webhook of your own.
Three cookies, all needed to sign in, and none for tracking or advertising:
- flagforge_session
- Keeps you signed in, for up to 30 days.
- flagforge_oauth
- Checks that a Discord sign-in was started here, for 10 minutes.
- flagforge_next
- The page to return to after signing in, for 10 minutes.
There's no analytics, and no script, font or image from another site.
- SMALL.PL
- Hosts the site and its database in Poland. Its web servers keep their own access logs, under small.pl's policy.
- DISCORD
- You sign in on Discord, under Discord's privacy policy; it tells FlagForge only the account details above. Failed playtest reports are posted to a Discord channel.
- OVH
- Hosts FlagForge's test Minecraft server, which receives the test server's whitelist.
Nothing is sold or shared for advertising.
Your account, licenses and servers are kept to provide the license you have (GDPR article 6(1)(b)). The activity log, rate limiting, download marks and playtest reports are kept in FlagForge's legitimate interest in keeping licenses secure and the software working (article 6(1)(f)).
You can ask for a copy of your data, to correct it, to delete it, to limit or object to its use, and to receive it in a portable form. Your account page lets you download a copy of everything kept about your account at any time, and delete an account without a license; for anything else, write to kontakt@szalik.dev, and you'll get an answer within a month. You can also complain to the data protection authority where you live.