Slime Wars — privacy & data

Anonymous play statistics (daily report)

Lifetime match counters - matches, wins, losses and time in matches; wins and losses per difficulty and per mode (w and l under each difficulty’s and mode’s own name); shards and gems earned and spent, with the reasons each was earned or spent (only reasons with a total above zero); and progression - research and building unlocked, crates, items, campaign wins, best wave, runs started and completed, season tiers and prestige - plus how many times the game has been opened and how many minutes it has been played. It carries no per-screen minutes; those are in the screen-time batches.

When: At most once a day (by the UTC date): one try a session, about a minute after the game starts, skipped if today’s report has already gone. A report that does not arrive is tried again at the next start.

Sent to: https://lostphantom.live/api/slimewars/report

Every name in it, read out of the game’s code: anon version platform sessions playtimeMin matches wins losses matchSeconds byDifficulty byMode economy shards gems w l in out sources sinks progression research_unlocked build_unlocked crates items campaign_wins best_wave runs_started runs_completed season_tiers prestige

Platform: the platform as Unity names it, one word: WindowsPlayer, OSXPlayer, LinuxPlayer or Android (a Steam Deck is not told apart - it reports Linux, or Windows under Proton).

Identifier: A random install id: twelve characters the game makes up on this machine the first time it prepares a report (about a minute into a session, and only with the switch on) and then keeps. It is not made from your Steam account, your hardware or a hash of anything, it is not copied to Steam Cloud or to an account, and turning the switch off does not delete it. It lets us tell one install’s reports from another’s; nothing in them says whose install it is.

Turning it off: the Share anonymous stats switch, on Settings → the Privacy tab (one switch covers both of this game’s statistics channels). It is ON by default. Off stops the report before it is built. RESTORE DEFAULTS on the Gameplay or Privacy tab turns it back on, and the choice travels to your other machines through the game’s Steam Cloud settings and, if you use one, your Slime Universe account. Turning the Studio link switch off (Settings → the Interface tab) stops this report too, before it is built.

What we keep: The latest whole report from each install, deleted 180 days after it last arrives, plus the same per-install record and daily totals the other games have (deleted after 400 days unheard and after two years). This is an older address than the other games use, and unlike theirs it stores the report as sent without refusing name-shaped fields; the game sends none. Your IP address reaches our server with the request, as it does for any connection; it is held in memory for a few minutes to limit how often a report is accepted, and it is never written to a table or a log.

Where this is read from: SlimeWarsByPhantomStudios2025: Assets/scripts/Stats/WebStats.cs BuildPayload, Records, Currency and Progression (the body) and ReportLater (the Privacy-tab switch, then the Studio link switch, then the day, then the send - the Studio link gate since a2f6e55f); Settings/SettingsCatalog.cs "sharestats" (the row); Settings/GameSettings.cs ShareAnonymousStats (the default) and RestoreDefaults; Settings/SettingsCatalog.cs "studiolink" (the Studio link row, on the Interface tab)

Screen-time batches

The game’s name, the per-launch id, the kind of device, the game version, and one row per screen opened since the last batch - its name, how many times it was opened and how many seconds it was shown - plus a few event counts recorded the same way (for example how often the cloud-save conflict prompt appeared). No install id, no account, no play-time total.

When: About every two minutes while the game is running, and again when it is paused, sent to the background or closed. A batch that fails is dropped, not kept for later.

Sent to: https://lostphantom.live/api/universe/analytics

Every name in it, read out of the game’s code: game session platform version screens name views seconds

Platform: the kind of device as one word: desktop (Windows, Mac, Linux and Steam Deck alike), android, ios, console or web.

Identifier: A random id made fresh every time the game starts and never saved on your device, so two launches cannot be linked to each other.

Turning it off: the Share anonymous stats switch, on Settings → the Privacy tab (the same switch as the daily report). It is ON by default. Off stops the batches and drops the one waiting to go. RESTORE DEFAULTS on the Gameplay or Privacy tab turns it back on. Turning the Studio link switch off stops these batches too.

What we keep: Only totals per day, per screen and per kind of device - how many times each screen was opened, for how long, and by how many launches - kept for two years; and the per-launch id, for two to three days, only so one launch is not counted twice. Nothing else from the batch is kept, not even the version. Your IP address reaches our server with the request, as it does for any connection; it is held in memory for a few minutes to limit how often a report is accepted, and it is never written to a table or a log.

Where this is read from: SlimeWarsByPhantomStudios2025: Assets/scripts/Shared/SlimeAnalytics.cs Payload (the body), Flush and Post (when, and the Studio link gate), Allowed (the default); Settings/GameSettings.cs ApplyPrivacy mirrors the Privacy-tab row into it

Bug reports and suggestions

Only what you write, and only when you press SEND. With it go eight things the game already knows: the game version, whether this is a live or a testing build, the build’s own word for itself (release, testing or demo — a demo is filed apart from the full game, because "the campaign stops here" is correct behaviour in one and a serious bug in the other), the platform (the word Unity uses — "WindowsPlayer", not your machine), the language you are reading, the screen you were on, the difficulty you were playing, and — for a bug report only — a short tail of the game’s own log. No name, no account, no email, no device name, no location, and no install id: this game neither sends nor mints one, so two reports from you cannot be joined to each other, by us or by anybody. Your screenshot stays on your machine and the box says so rather than quietly dropping it. Your home folder, your Windows account name and your computer’s name are folded out of that log tail on your own machine, before it is written to disk, copied to your clipboard or sent anywhere.

Honesty note: there is no switch in front of the box, because there is nothing running: the game composes a report only after you have written one and pressed SEND. The "Share anonymous stats" row above deliberately does NOT silence it — turning statistics off says you do not want to be measured, not that you no longer want to be able to report a crash, and taking the box away with that switch would leave the people most careful about their data with no way to tell anybody anything.

Where this is read from: SlimeWarsByPhantomStudios2025: Assets/scripts/Studio/FeedbackCore.cs (Body() is the whole payload and the only place a field name is spelled; installId is deliberately neither sent nor minted) and Studio/StudioSubmit.cs (the press, and the legacy fallback), held by Tools/feedbackcheck.py, which compiles FeedbackCore and RUNS the body the press builds

• Your name, username, email address or any account of any kind - no game sends one. The studio’s statistics address (/api/<game>/telemetry) REFUSES a report carrying a field named like one of those, or any value shaped like an email address, with an error saying so. Slime Wars’ daily report goes to an older address that stores it as sent without that check, and it carries no such field.
• Your IP address is never stored. It reaches our server with every request, as it does for any connection, and the server holds it in memory for a few minutes to limit how often reports are accepted, then forgets it. No table has a column for it and it is not logged. (What our hosting provider’s own network logs keep is outside our code.)
• Anything you type. No chat, no search, and no bug-report text travels with the statistics.
• Your location, contacts, files, other running programs, or anything at all from outside the game.
• No advertising and no third-party analytics service runs in any of these games, and nothing is sold, rented or shared with anybody. Outside this studio’s own statistics, and not governed by its switch: every game is built with Unity, whose engine can report basic hardware details and crashes to Unity; Winter Is Here and Slime Wars tell Steam which achievements you unlock, and Slime Wars also reports lifetime playtime, kills, wins and losses to its Steam stats and leaderboards and signs in to Unity’s player-account service with your Steam login for its online features. Slime Wars and Slime Dominion include Unity’s ad library for a possible phone version and never start it, and Winter Is Here carries PlayFab and Photon code from an older project that nothing calls.

What this adds up to on our side is mostly charts. Per game and per day the dashboard shows:

• how many installs were heard from that day, and how many were new
• total sessions and total minutes played
• which screens took the most time, added up across everybody
• which versions are still in the wild
• whether an install came back a day or a week later

For the games that send a daily report (Winter Is Here, Dug Out, Smokestack Valley, Pencil and Paper and Slime Wars) we also keep one record per install - its latest totals and the first and last day it was heard from - and the dashboard lists a few of them under a short label that stays the same between visits. So we can tell one install from another, but not who is behind it: there is no name, account, Steam id, email or IP address anywhere in it, and the id is random. The screen-time batches keep no per-install record at all.

• A Slime Universe account is optional and separate: if you create one, the name and friend code you chose are covered by the studio privacy policy, and none of the anonymous statistics above are ever joined to it.
• Survey answers send exactly what you typed, when you send them.