ARTEMIS: SALVAGE PROTOCOL — PRIVACY AND LOCAL STORAGE

The reviewed preview runs in your browser. Its game code has no account system, advertising, analytics, telemetry, cloud saves, or live AI connection.

The game uses localStorage key artemis.salvage-protocol.v1 for banked cargo, discovery unlocks, settled-sortie identifiers and preferences. Recovery of an unsupported or corrupt save can create backup keys beginning artemis.salvage-protocol.v1.preserved. Exports are browser downloads to a location you choose; they are not automatically uploaded. Active sorties are held in memory, not saved for later resumption.

Storage belongs to the exact site origin and browser profile, not an account. It does not synchronize between devices, browsers, ports or hostnames. Clearing site data, private browsing, storage pressure or reset can lose progress. A new preview hostname has separate storage from the existing game. The standalone Salvage package does not include a service worker. On the combined Salvage/legacy website, a site-level service worker caches public game files for offline use after a complete online installation. Browser eviction can remove that cache; it is not a save backup. The legacy games use separate save keys on the same origin.

The game requests same-origin application files. The hosting provider still receives ordinary web requests and may process IP address, request time, user agent and requested path according to its own privacy terms and retention practices. Your workplace network or managed device may also monitor access. No promise of anonymous browsing or zero host logging is made. Do not submit personal or workplace-confidential information in feedback or exported diagnostics.