Last updated: July 9, 2026 · Effective for Peace War Game v0.1.1 and later
This page is the technical companion to our Privacy Policy: a plain breakdown of exactly what data exists when you play Peace War Game, where it physically lives, and how long it sticks around. It reflects the architecture as actually built, not an aspirational design.
Peace War Game is a Unity client with an embedded ASP.NET Core + SignalR game server bundled inside the install. When a player creates a room, their own computer runs that server process for the lifetime of the match ("peer-hosted"). Other players connect to it directly or via Unity's Relay service (used for NAT traversal, not data storage). Identity and a handful of cross-session services are the only pieces that run on infrastructure outside any individual player's PC, and those are operated by Unity Gaming Services (UGS), not by Studio Kudo.
| Data | Where it lives | Retention |
|---|---|---|
| Account credentials username, password, auth tokens |
Unity Gaming Services (Unity's cloud) | Per Unity's own policy; not accessible to Studio Kudo |
| Display name | Unity Cloud Code username registry | Until you change or your account is deleted via Unity |
| Friends list & presence | Unity Friends service | Until removed by you; presence is live-only |
| Friend/lobby chat messages | In-memory on your device and the recipient's, relayed via Unity | Session only, cleared on quit, not logged by Studio Kudo |
| Lifetime leaderboard stats capital earned, weapons sold, endings reached |
Unity Leaderboards | Until account deletion via Unity |
| Per-match session data game session record, per-player round stats, in-game action audit log |
A local SQLite database on the hosting player's own PC (%AppData%\ArmsFair\armsfair.db) |
Persists on that PC until the host clears it; never transmitted to Studio Kudo |
| AI opponent API key (Claude/OpenAI, host-supplied) | Held in the host server process's memory for that session only; optionally cached on the host's own PC encrypted with Windows DPAPI, tied to that Windows user account | Memory copy cleared when the match ends; never written to the SQLite database or sent to any client, including Studio Kudo |
| Game/negotiation content sent to AI providers | Sent directly from the host's PC to Anthropic's/OpenAI's API when AI opponents are active | Governed by that provider's own retention policy |
| AI-filled game logs phase transitions, bot decisions, for balance reference |
JSONL file on the host's own PC (next to the install, or %LocalAppData%\PeaceWarGame\GameLogs) |
Only written for games with AI opponents; stays local until the host deletes it; not auto-uploaded |
| World seed data fetch Global Peace Index / SIPRI derived country stats |
Fetched from Studio Kudo's small data server, with a bundled offline fallback in the install | Not personal data; standard web request logging may apply at the fetch endpoint |
| Website visits | Static web hosting; Google Fonts and esm.sh CDN see requester IP as a normal side effect of loading fonts/scripts | No first-party analytics or cookies are set by us |
Account, profile, friends, and leaderboard data: manage or delete via your Unity account. Local per-match data, API key cache, and game logs: these live only on whichever PC hosted a given match. Deleting the relevant files or uninstalling the Game on that machine removes them, since Studio Kudo never held a copy.
Questions about this Data Policy: support@peacewargame.com
See also: Terms of Service · Privacy Policy