Privacy, in plain sight.

This policy covers ECHO VAULT version 1.0.0, a turn-based time-loop puzzle game delivered as a Chrome extension. It describes the included game page, its local progress record, the backup tools and this bundled privacy page. Playing does not require a registered account, a real name, an email address or access to a game server.

The game’s time-loop fiction should not be confused with monitoring a person. An echo is a sequence of game commands that you intentionally create inside a vault. Those commands are processed on the device to animate a fictional operator and solve a puzzle; the shipped extension does not send them to the publisher.

A recording consists of a small alphabet of gameplay commands: move up, down, left or right, wait, and interact. The sequence describes actions in a grid-based puzzle. It does not include your screen, camera, microphone, typed documents, browsing session, physical movements, real-world location or the content of a webpage behind the popup.

Keyboard listeners belong to the game document and are used for the displayed controls while that document has focus. The extension does not install a content script or a global keyboard listener across websites. The word recording in the interface refers only to this intentionally limited game mechanic, not to media capture or general keystroke collection.

The save includes the product and format identifiers, completion records for the twenty-four included vaults, the current vault number, committed echo tapes, the current live-operator tape, and sound and motion preferences. A completion record contains a star rating, total command count and number of echoes used for the best stored result.

The current run can contain up to three echo tapes and one live tape, each with at most eighty commands. The game reconstructs positions, guard behavior, power and device states by replaying those commands. It does not need to save a video, a browser capture or a continuously growing record of every puzzle attempt.

Command tapes are used to continue the current puzzle, undo a beat, display the score and replay actions already taken. Completion records are used to show progress in the vault index and retain the best result. Settings preserve whether sound and ambient motion are enabled. Product and version fields distinguish valid backups from unrelated files.

These records are not used for targeted advertising, identity resolution, audience segmentation or behavioral predictions outside the game. The publisher does not receive a live feed of your moves. No service ranks your performance against other people, sells your solution data or builds an account history from the local progress record.

ECHO VAULT requests a local save after accepted actions and changes such as committing an echo, undoing, restarting a loop, changing vaults, importing a backup or updating preferences. A successful storage transaction updates the save indicator. Because the world advances by commands, it does not take extra turns while the popup is closed or while you read another page.

The browser may close a popup or terminate a process before a pending save finishes. The latest action could be lost in that situation. The game reports save failures and offers a backup export, but it cannot promise to restore data after a storage wipe, a damaged profile or an interrupted operating-system write.

This release uses IndexedDB in the extension’s own browser origin. The product database is named echo-vault-v1 and holds its local save in a state store. It does not use chrome.storage.sync, chrome.storage.local, a hosted account database or an online synchronization service. A save in one browser profile is not automatically available on another device.

The extension does not add its own password or encryption layer to this database. People or software with access to the browser profile may be able to inspect its contents. Browser-profile exports, enterprise management and operating-system backup tools are separate systems and may copy local files according to their own configuration.

The manifest for this version declares no permissions, optional permissions, host permissions or optional host permissions. There are no content scripts and no background service worker. The game does not request access to browsing history, bookmarks, tab contents, downloads history, notifications, clipboard, location, microphone or camera.

The optional Open in a tab control creates a tab for the bundled game page; it does not enumerate or inspect your other tabs. Backup import reads a file you select, and export uses a normal download link for a locally generated JSON file. These specific user controls do not grant the game general access to your filesystem.

The vault is rendered in its own extension page. It does not inspect the website behind the toolbar popup, capture page text, scrape accounts or read form fields. It does not replace links, change search results, insert advertisements or alter a site’s scripts. Puzzle guards and cameras have access only to the fictional grid defined by the game.

In particular, a camera shown in a vault is a drawn game object with a computed line of sight. It does not correspond to your device’s camera and cannot see your room, screen or other browser tabs. The alarm mechanic evaluates positions in the puzzle, not information about the person playing it.

The extension package includes its levels, scripts, styles, icons and artwork. It does not fetch levels, fonts, images, analytics configuration or executable code from external hosts. The Content Security Policy disallows connections for extension pages, and the game code includes no network request, web socket, remote module or game-server endpoint.

The browser and Chrome Web Store can have their own installation, update and account communications. Those activities are distinct from this game’s code. A publisher may also host a public copy of this policy for the store listing; visiting that hosted page uses its website infrastructure, whereas the bundled policy can be read as a local extension document.

ECHO VAULT version 1.0.0 includes no advertising system, analytics SDK, tracking pixel, affiliate mechanism, in-app purchase workflow, crash-report uploader or attribution identifier. It does not create a publisher-side player ID. There is no remote leaderboard, multiplayer service, chat room or public solution gallery connected to the saved tapes.

The beat counter, echo count and star rating are gameplay feedback. They remain in the local state or in a backup you explicitly export. The publisher does not automatically learn how many times you tried a vault, whether you used a hint, what routes you recorded or how much time you spent thinking between commands.

There is no automatic transfer of game data to the publisher or to an external processor. This release does not bundle third-party telemetry packages or load assets from a content-delivery network. Browser-supplied APIs provide rendering, storage and optional tone generation without introducing a game-operated online service.

You can choose to send a screenshot, backup or support message through another application. A recipient could then see the information you included, and that application’s own rules would apply. The game does not make that sharing decision for you and does not gain ongoing access to a conversation or file-sharing account because you sent a backup.

Export backup serializes the current local record as JSON and asks the browser to save it under a suggested ECHO VAULT filename. The file contains game progress, current command tapes and preferences, not a recorded video or a list of visited websites. The game does not read the final download destination or your existing download history.

A downloaded backup is a separate copy under your control. It remains after you restart a vault or erase the installed game’s local data. Anyone who can read the file may inspect the included solution and preferences. A filename or accompanying message that you add yourself can disclose personal information even when the underlying game record does not ask for it.

Import backup reads the single file you intentionally select through the file picker. Files larger than one megabyte are rejected. The game parses JSON, checks the product and schema, validates command characters and bounds, and reconstructs recorded loops to reject impossible or incompatible records before replacing the current save.

Import does not execute uploaded code or treat file content as HTML. A rejected file produces an explanation without replacing the existing run. A valid file replaces current progress and settings, so exporting a backup first can be useful. The file picker does not authorize scanning the selected file’s folder or uploading its contents anywhere.

Undo removes the most recent live command and deterministically reconstructs the preceding world state, including guards, power, doors and the prism. Restarting a loop removes current live commands while preserving committed echoes. Removing the last echo also resets the live loop so that the changed ensemble begins consistently at beat zero.

Replay this loop displays prefixes of commands already present in the current run. Moving the replay slider does not change the saved score or create a separate playback history. There is no video stream, exported recording, screen capture or remote watch session associated with this feature. It is another local calculation from the same bounded command data.

The current record stays in the browser profile until replaced, erased, removed with extension data or cleared by the browser or device. There is no publisher-side retention schedule because no server copy is created. Changing vaults discards the previous unfinished run while keeping the best completion records and current preferences.

The game retains a bounded set of twenty-four completion entries and one current score, not every historical attempt. The maximum number and length of tapes limit save growth. Browser storage can nevertheless become unavailable or be cleared. The extension does not request unlimitedStorage and should not be used as the only archive of a solution you want to keep.

The erase control is in Local data & settings. Enter ERASE in the confirmation field and select Erase local data. The game clears the existing saved record and creates a fresh default state for the first vault. This resets stored progress, tapes and preferences without relying on an account deletion request to an online service.

This action does not search for exported backups or remove files that you previously shared with someone else. Delete those copies separately using your device or the service where you placed them. Browser and operating-system backups may also contain earlier profile data that the extension cannot locate or erase on your behalf.

The game requests a browser-managed lock for its own origin while an active game window controls the save. A second ECHO VAULT window shows a message instead of silently overwriting the first window’s score. Opening the game in a separate tab transfers control locally; it does not sign in to a server or register another device.

The lock is not an advertising identifier, account credential or persistent player ID. It exists to coordinate pages within the same installed game and is released when the owning page closes or yields control. Local coordination cannot recover a write that was interrupted before completion, so backups remain a separate safeguard.

Sound is disabled initially. Enabling it produces short locally synthesized tones for gameplay feedback. The code does not request microphone access, record audio or contact a sound service. Ambient motion can be disabled independently; logical turns, devices and puzzle outcomes do not depend on decorative animation.

The initial motion preference can take the device’s reduced-motion setting into account. The renderer also uses the viewport size, display pixel ratio and frame time to draw the vault clearly. These runtime values are not stored as a fingerprint or sent to analytics, and the game does not use them to identify the person playing.

The implementation avoids webpage injection and remote executable code, restricts extension-page connections, validates imported records and uses local storage transactions. Dialog text derived from data is escaped. The game reconstructs a world from a small set of allowed commands rather than trusting an uploaded object to define arbitrary executable behavior.

These choices reduce unnecessary exposure but are not a warranty that any software is invulnerable. The local save is not encrypted by this game, and a person with access to an unlocked profile or backup file may inspect it. Device security, browser maintenance and careful handling of files remain relevant even for an offline puzzle game.

A storage failure is reported in the interface instead of being silently described as a successful save. The current in-memory score can be exported through the backup control. If a loaded record fails validation, the recovery interface offers a stored-record export, retry and an explicit erase action rather than automatically overwriting the record as a new game.

The publisher has no account-based recovery system and cannot pull your tapes from a game server. Recovery therefore depends on what remains in the browser or in a backup that you kept. A malformed file may be refused even if parts of it resemble valid progress, because inconsistent command histories can change puzzle outcomes.

The game does not ask for age, date of birth, school, a child’s name or guardian details. It has no public chat, friend list, player directory or user-to-user messaging. These are statements about the included data flows, not a claim that game-rating rules or publisher responsibilities are identical in every place of distribution.

People sharing a browser profile may see or alter the same puzzle progress. A parent, guardian or device owner can reset the local record using the erase control and manage downloaded files separately. There is no hidden reporting channel that sends a child’s command tapes to the publisher or a remote monitoring service.

The game includes no feedback uploader, support inbox or contact form. To ask the publisher a question, use the developer contact or support route shown in the Chrome Web Store listing through which you obtain ECHO VAULT. Include the exact product name and version so that the message can be matched to this release.

A message sent through a separate email or support service may include the contact details and attachments you provide there. You decide whether to attach a backup or screenshot. Avoid unrelated browser tabs, credentials, personal documents and identifying filenames when they are not needed to describe a puzzle problem.

Installing the extension does not give the publisher a dashboard containing your game record. The publisher cannot search your IndexedDB database, read your tapes remotely or erase a backup from your device through this version. Local export, replacement and deletion controls are provided precisely because the user controls the existing copies.

If you voluntarily send a file during support, that particular file is information you have chosen to disclose. It does not create access to future turns or future saves. A request concerning information held by an independent support provider or hosting service may need to be addressed through that service’s own contact and data controls.

This text describes version 1.0.0 and carries the effective date shown above. Any future release that changes permission requests, adds an account, sends data outside the device or changes retention would require a corresponding policy update and appropriate disclosure. The present offline design should not be assumed to describe an unrelated future feature.

The extension does not fetch policy updates or additional terms in the background. The bundled page belongs to the installed package. Browser-store installation and update notices are separate from this document. Keeping the release package and its policy can help you retain a record of the specific version you chose to install.

The publisher must make a working developer or support contact available when distributing ECHO VAULT. The relevant contact is the one associated with the product’s own Chrome Web Store listing, not an unrelated game with a similar name. This bundled document contains no automatically inferred email address and does not itself transmit a request.

No legal identity or mailbox has been fabricated from game data. Questions about this product’s local processing should identify ECHO VAULT 1.0.0; questions about the browser’s account services, the store or a separately hosted policy page may also involve the organization operating that service. A publisher should provide its distribution contact before public release.

ECHO VAULT remembers a bounded set of puzzle commands and completion records on your device. Echoes are fictional command replays, not recordings of your computer or surroundings. The game does not inspect websites, run analytics, upload solution tapes or keep an online account. Its normal controls let you inspect progress, export it, replace it or erase it locally.

Check the save indicator before closing a session that matters, keep your own backup when appropriate, and consider the contents of any file or screenshot before sharing it. Those choices stay with you. They do not activate a hidden data service, grant new webpage access or alter the no-permissions manifest included with this version.