Scope of this policy
This policy applies to Blackwater version 1.0.1 as distributed as a Chrome extension. It covers the submarine simulation, sonar and navigation interface, vessel systems, crew state, expedition progression, upgrades, mission results, and the local save mechanism included with the game.
It does not govern Google Chrome, the Chrome Web Store, the operating system, device backup products, enterprise management, or other extensions. Those systems may process information independently.
The saved information is fictional expedition state
Blackwater stores a local game state so an expedition and longer progression can continue after the popup closes. The state contains fictional variables describing the research vessel, crew, contacts, cargo, systems, upgrades, credits, science, and current mission.
It is not a log from a real submarine and does not contain data obtained from marine navigation equipment, sonar hardware, AIS, GPS receivers, research institutions, or maritime authorities.
- Fictional vessel position, heading, depth, target depth, and seafloor model state.
- Power allocation, reactor availability, battery charge, oxygen, carbon dioxide, and temperature.
- Compartment integrity, flooding, sealing, and repair state.
- Crew fatigue and current fictional assignments.
- Sonar contacts, survey results, salvage state, cargo, science, credits, and upgrades.
- Objective and mission-progression state required to resume the game.
Local storage only
Blackwater saves progress with window.localStorage inside the extension's own browser origin. Version 1.0.1 uses the key blackwaterStateV1 for its primary persistent game state.
The extension does not intentionally upload this save to a developer-operated server. There is no Blackwater account, online captain profile, multiplayer service, cloud save slot, or remote expedition database in this release.
No Chrome permissions requested
Blackwater version 1.0.1 requests no Chrome permissions. Its manifest does not request activeTab, tabs, scripting, storage, history, cookies, downloads, bookmarks, geolocation, notifications, or host access.
The game runs within its own popup and uses ordinary localStorage for persistence, so it does not need the chrome.storage permission or access to the user's web pages.
No browsing or webpage inspection
Blackwater does not inject scripts into websites and does not read page content, URLs, titles, form entries, search queries, account pages, browsing history, or website cookies.
Sonar contacts, wrecks, vents, terrain features, and expedition destinations are generated or stored as part of the fictional game world. They do not correspond to webpages visited by the player.
No account or identity collection
The game has no sign-in process and does not request a real name, email address, phone number, social identity, profile image, home address, or date of birth.
Blackwater does not assign a developer-side account identifier. The browser itself manages the installed extension and its local storage context.
No analytics or telemetry
The packaged extension does not include Google Analytics, Firebase Analytics, Mixpanel, Amplitude, Segment, PostHog, remote Sentry telemetry, advertising analytics, or a similar third-party measurement service.
The developer does not receive routine gameplay events such as depth reached, contacts surveyed, salvage selected, power allocations, crew fatigue, hull damage, mission failures, or expedition duration.
No advertising or behavioral profiles
Blackwater does not display third-party advertising and does not contain ad-network code, conversion pixels, affiliate trackers, retargeting systems, or cross-site behavioral profiling.
The local expedition state is not sold, rented, or provided to data brokers or advertisers by the extension.
No gameplay network upload
The reviewed production code for version 1.0.1 does not use fetch, XMLHttpRequest, or WebSocket to upload expedition data. It does not send sonar state, vessel condition, mission choices, or progression to a developer backend.
The game does not require an internet connection to calculate its simulation after installation, apart from any browser or store functions outside the extension itself.
No remote code
The JavaScript simulation, interface, CSS, icons, and other resources needed by Blackwater are packaged with the extension. The game does not download executable JavaScript from a remote server during play.
A packaged-code model helps keep the behavior of the reviewed release tied to the extension version installed by the browser.
Sonar and navigation are simulated
The sonar scope is a game interface. It does not activate or listen to a physical sonar device, microphone, speaker array, marine sensor, GPS receiver, compass sensor, or navigation unit.
Bearing, range, contact depth, echoes, seafloor depth, vessel coordinates, and return-to-base navigation are calculated by the local fictional simulation.
No microphone, camera, or location
Blackwater does not request or use the microphone, camera, GPS location, motion sensors, contacts, Bluetooth, USB, serial ports, local-network equipment, or external maritime devices.
The word "location" in an expedition context refers to coordinates inside the game world, not the player's physical location.
Power, life support, and crew values
Values such as reactor output, battery charge, oxygen reserve, carbon dioxide concentration, temperature, flooding, hull stress, and crew fatigue are fictional gameplay variables.
They are not health information about the user, readings from environmental sensors, medical measurements, or power data from the user's device. The extension does not infer the user's physical condition from how the game is played.
Files, clipboard, and downloads
Version 1.0.1 does not request permission to read local documents, inspect download history, write exported mission files, or access clipboard contents.
Chrome and the operating system necessarily maintain application and extension files as part of normal software operation. Those browser-managed files are not a Blackwater file-upload feature.
Retention
The local save can remain in the Chrome profile until later gameplay replaces it or the user/browser removes the relevant storage. There is no developer-side save retention schedule because normal expedition data is not stored on a Blackwater server.
Browser-profile backup systems, operating-system backups, enterprise tools, or other software may independently copy browser files and retain them under their own rules.
Deletion and starting over
Users can use the game's reset or new-progress controls where available, or remove local extension data through Chrome. Uninstalling the extension or removing the associated browser profile can also remove the save according to browser behavior.
Because version 1.0.1 has no developer cloud backup, the developer normally cannot recover an expedition save after it has been permanently deleted from the user's browser environment.
Security characteristics
Blackwater minimizes its data footprint by requesting no Chrome permissions, keeping game state local, avoiding accounts, and not integrating remote telemetry or remote code in version 1.0.1.
Local browser storage is not equivalent to an encrypted password manager. Someone with sufficient access to an unlocked device, Chrome profile, browser files, developer tools, or profile backup may be able to inspect or alter local game data. Sensitive personal information should not be intentionally placed into game-state storage.
Safety and simulation limitations
Blackwater is entertainment software. Pressure, hull behavior, gas management, sonar, navigation, power distribution, flooding, salvage, crew operations, and emergency response are simplified fictional systems designed for gameplay.
The game does not provide diving guidance, submarine-operating procedures, marine navigation, salvage instructions, scientific advice, emergency guidance, or vessel-safety information. It must not be used to plan or conduct a real underwater operation.
Scientific and salvage content
Science points, specimens, wrecks, research contacts, merchant wreck labels, vent fields, and salvage rewards are game content. They do not indicate the presence of real artifacts, protected wrecks, archaeological sites, wildlife, or scientific discoveries.
No real-world salvage ownership claim or scientific record is created by completing a game objective.
Children and general audience use
Blackwater is a general fictional systems-management game. It does not include public user profiles, chat, direct messaging, targeted advertising, gambling, or a developer-hosted social account database.
The developer does not knowingly maintain a remote database of children's personal information through normal game operation. Local game state is handled in the same manner for all players.
International use and transfers
Because normal expedition state is not intentionally uploaded to Blackwater infrastructure, version 1.0.1 does not ordinarily transfer that local save between developer-operated data centers or countries.
Chrome distribution, device backups, browser-profile synchronization configured outside Blackwater, and operating-system services may have their own international data practices.
Third-party services
The packaged game does not integrate a third-party analytics SDK, ad network, cloud-save provider, social login, remote AI service, mapping API, weather API, maritime tracking API, or sonar service.
Google Chrome and the Chrome Web Store are separate products and may provide installation, update, account, crash, or store functionality under their own policies.
Legal requests and disclosure
Because normal Blackwater saves are not held in a developer database, the developer generally does not possess a server-side copy of a player's sonar contacts, expedition path, salvage choices, crew state, upgrades, or mission results.
If the developer receives a legally valid request, only information actually possessed by the developer can be disclosed. This policy does not alter legal obligations that may apply in a particular jurisdiction.
Future product changes
If a later Blackwater version introduces accounts, online leaderboards, multiplayer, cloud saves, analytics, remote AI, content downloads, broader Chrome permissions, external maritime data, or other materially different processing, the privacy disclosures should be updated for that release.
The policy date and version at the top identify the specific packaged behavior described here.
Policy updates
This policy can be revised for clarity, changes in law, Chrome Web Store requirements, or changes to the game. A materially different data flow should be accompanied by an updated policy rather than silently relying on this version's local-only description.
Users of a later release should review the policy associated with that version.
Contact
Privacy questions about Blackwater can be sent through the developer contact information displayed on the Chrome Web Store listing used to obtain the extension.
Support messages should not include passwords, payment information, private browser data, medical information, precise location, or other sensitive material that is unnecessary to explain the question.