Scope of this policy
This policy applies to Grid Command version 1.0.1 as distributed as a Chrome extension. It covers the game popup, the power-grid simulation, the user interface, persistent game progress, upgrades, service-day results, and the local save mechanism packaged with the extension.
It does not describe the independent data practices of Google Chrome, the Chrome Web Store, your operating system, browser-profile backup software, device-management software, or other extensions installed in the same browser. Those products can process information separately from Grid Command.
The data model is a game state
Grid Command stores a fictional simulation state so a service day or longer progression can continue after the popup closes. The state consists of game variables such as the in-game clock, weather, generator dispatch, battery state of charge, line conditions, district demand, incidents, score, credits, upgrades, logs, and progression.
The save represents the fictional city network shown inside the game. It is not a copy of a real utility network, a map of the user's location, or operational information obtained from an electricity provider.
- Fictional generator output and dispatch targets.
- Fictional district demand and service levels.
- Battery charge, transmission line status, and incident state.
- Game credits, upgrades, score, reliability, emissions, and service-day progress.
- UI-relevant game choices required to resume play.
Local storage only
Grid Command saves progress with the browser Web Storage API, using window.localStorage inside the extension's own origin. Version 1.0.1 uses the key gridCommandStateV1 for its primary saved state.
The extension does not intentionally transmit this save to a developer-operated server. There is no Grid Command account, online profile, remote save slot, leaderboard upload, or cross-device sync service in this version.
No Chrome permissions requested
The version described by this policy requests no Chrome permissions. The manifest does not request activeTab, tabs, scripting, storage, history, cookies, downloads, bookmarks, geolocation, notifications, or host permissions.
Because the game is self-contained in its popup, it does not need privileged access to the user's browsing activity. Its persistent state uses ordinary localStorage available to the extension page rather than the chrome.storage permission.
No webpage access
Grid Command does not inject a content script into websites and does not read, modify, summarize, record, or monitor webpage content. It does not inspect page titles, URLs, form fields, search queries, account pages, or text typed into sites.
The game therefore does not build a browsing-history profile and cannot use visited pages to change generation, demand, incidents, weather, or any other game mechanic.
No account or identity system
Grid Command version 1.0.1 has no sign-in flow and does not ask for a name, email address, phone number, username, date of birth, profile picture, or social account.
The game does not assign a developer-side player identifier. A local save exists only in the browser storage context used by Chrome for the installed extension.
No analytics or telemetry
The packaged extension does not include Google Analytics, Firebase Analytics, Mixpanel, Amplitude, Segment, PostHog, Sentry telemetry, advertising analytics, or a comparable remote measurement service.
The developer does not receive routine events describing how often the game is opened, which buttons are pressed, how many outages occur, what score is earned, how long a service day lasts, or which upgrades the user buys.
No advertising or profiling
Grid Command does not contain an advertising network, ad auction, conversion pixel, retargeting tag, affiliate tracker, or behavioral marketing system. Gameplay is not used to infer interests for advertising.
The local simulation state is not sold, rented, licensed, or shared with data brokers or advertisers by the extension.
No network upload in version 1.0.1
The reviewed production source does not use fetch, XMLHttpRequest, or WebSocket to upload game state. It does not contact a remote gameplay API, account server, analytics endpoint, AI service, or cloud database.
All game logic, CSS, JavaScript, icons, and interface assets needed for normal operation are packaged inside the extension.
No remote code
Grid Command does not download JavaScript or executable game logic from the internet. The simulation executes code packaged with the installed extension.
This design keeps the behavior reviewed for version 1.0.1 tied to the files delivered through the extension package rather than an unreviewed remote script that can change independently.
How weather and incidents are generated
Weather fronts, renewable variation, equipment faults, overloads, repair timing, district demand, and other operational events are generated by the local game simulation. They are not derived from real weather, real utility telemetry, the user's region, browsing activity, or a third-party data feed.
The city, substations, generators, districts, loads, and incidents are fictional abstractions created for gameplay.
Location, sensors, and device access
Grid Command does not request or read GPS location, IP-derived location through a developer service, camera input, microphone input, motion sensors, contacts, Bluetooth devices, USB devices, serial ports, or local network equipment.
A weather label in the game is part of the simulation and must not be interpreted as local meteorological information.
Files, clipboard, and downloads
The game does not request permission to read local files, enumerate downloads, inspect the clipboard, or write exported save files in version 1.0.1.
The browser can of course maintain its own application files and extension storage as part of normal Chrome operation. Those browser-managed files are not a Grid Command document-upload feature.
Retention
The local save can remain in the Chrome profile until it is replaced by later gameplay or removed through browser or extension controls. Grid Command does not impose a developer-side retention period because the save is not maintained on a developer server.
The browser, operating system, enterprise administrator, or backup software may retain copies of browser-profile files independently. Their retention behavior is outside the extension's control.
Deletion and reset
A user can reset game progress through the game interface where that control is provided. Users can also remove extension data using Chrome's extension and site-data controls, delete the relevant Chrome profile, or uninstall the extension.
Because there is no developer cloud backup in version 1.0.1, the developer normally cannot restore a local save after the browser has permanently removed it.
Security characteristics
Keeping gameplay data local and avoiding privileged Chrome permissions reduces the amount of information exposed through the game. The package also avoids remote code and remote telemetry in this version.
Local browser storage is not an encrypted secrets vault. A person or process with sufficient access to the same unlocked device, Chrome profile, profile backups, or browser files may be able to inspect or alter locally stored extension data. Users should not attempt to store sensitive personal information inside game-state fields or developer tools.
Simulation limitations
Grid Command is entertainment software. Its network flow, frequency response, equipment behavior, reserve calculations, emissions, repair process, costs, and protection behavior are deliberately simplified and fictionalized for playability.
The extension does not provide professional electrical-engineering advice, grid-operation instructions, emergency guidance, utility forecasts, or real infrastructure monitoring. No game outcome should be used to make a real-world utility or safety decision.
Children and general audience use
Grid Command is a general game about a fictional power network. It does not provide public profiles, chat, direct messaging, targeted advertising, gambling, or a developer-side account database.
The extension does not knowingly maintain a remote database of personal information about children. The local game state is handled in the same manner regardless of the player's age.
International use and transfers
Normal gameplay in version 1.0.1 does not upload the local save to Grid Command infrastructure, so the extension does not ordinarily transfer that save between developer-operated data centers or countries.
Chrome distribution, operating-system services, browser-profile synchronization configured outside the extension, or device backup systems may have their own international processing practices.
Third parties
No third-party analytics, advertising, cloud-save, social-login, remote-AI, or gameplay backend is integrated into the packaged version described here.
Google Chrome and the Chrome Web Store remain separate third-party products. Their operation, update delivery, crash handling, account features, and store services are governed by their own terms and policies.
Legal requests and disclosure
Because normal Grid Command game state is not held in a developer database, the developer generally does not possess a server-side copy of a player's service days, scores, incidents, upgrades, or local save.
If the developer receives a legally valid request, only information actually possessed by the developer can be disclosed. This policy does not promise resistance to lawful process where applicable.
Future features
A future release could change the product. If Grid Command later adds accounts, online leaderboards, cloud save, multiplayer, analytics, remote AI, broader Chrome permissions, webpage interaction, or other materially different data handling, the extension disclosures and this privacy policy should be updated before those features are represented as covered by this version.
The version and effective date at the top of this document identify the behavior described here.
Policy updates
This document can be revised for clarity, legal requirements, Chrome Web Store requirements, or changes in the extension. Material changes to data handling should be described in a corresponding updated policy.
Users reviewing a later release should rely on the policy published for that release rather than assuming every future version has exactly the same data flow as version 1.0.1.
Contact
Privacy questions about Grid Command can be sent through the developer contact information displayed on the Chrome Web Store listing from which the extension is distributed.
Because the game does not need personal gameplay data to answer ordinary support questions, users should avoid including passwords, payment information, private browser data, or other sensitive material in a support message.