Parcel 17

Scope and plain-language summary

Parcel 17 is a self-contained parcel-sorting simulation and narrative game that runs inside its extension popup. Every sender, address, tracking number, weight, scanner result, routing rule, anomaly, and shift result shown on the desk is generated locally for the game.

The practical privacy summary is that the depot is fictional and local. Parcel 17 stores shift progress in the extension page’s localStorage and does not connect to a real carrier, postal network, logistics database, analytics service, account system, or advertising platform.

Parcel labels are game objects. They are not records of real mail, and the X-ray, scale, and tracking instruments do not communicate with physical scanners or shipping systems.

Chrome permissions

The production manifest declares an empty permissions array. Parcel 17 does not request tabs, history, activeTab, scripting, storage, downloads, clipboard, notifications, geolocation, camera, microphone, or host access.

The game uses localStorage belonging to its own extension page, which does not require the Chrome extension storage permission. No optional permission prompt is introduced later in the shift.

• No host permissions are declared.
• No website content script is packaged.
• No carrier or account permission is requested.
• No background browser activity is required for the sorting loop.

Information created during play

Parcel 17 creates a local game state containing processed and correct counts, streak, shift number, narrative stage, scanner unlock status, routing-card revision, the current parcel queue, recent routing history, pseudo-random generator state, and the latest desk message.

Each fictional parcel can contain a generated tracking ID, sender, destination, zone, printed and simulated weight, priority or damage flags, hazard status, temperature, anomaly type, inspection count, acoustic BPM value, fictional internal volume, and tracking chronology. These are game variables, not measurements of a real shipment.

What the player provides

The player provides routing decisions by choosing Local, Express, Hold, Return, or Special and may request a Scale, Tracking, or X-ray inspection. Those choices are inputs to the local rule engine. Parcel 17 does not ask the player to type a real address, tracking number, name, phone number, email address, or payment information.

A wrong route and a correct route are both recorded only in the local progress state so that accuracy, streak, narrative progression, and returning fictional parcels can function.

Local storage and save format

The game stores one JSON save record under the localStorage key parcel17-v1. The record contains the current fictional depot state and queue. It does not contain data read from shipping websites, browser tabs, the clipboard, local files, or a device scanner.

The queue persists so that closing and reopening the popup does not silently replace the parcel on the desk. The rule revision and narrative stage also persist so that later anomalies remain consistent with the player’s shift history.

Retention and deletion

Local progress remains in the browser profile until the player uses Reset desk, clears extension data, removes the extension, or the browser deletes that site data. Parcel 17 does not keep a remote backup or a second server-side history.

Reset desk replaces the local shift with a fresh state after confirmation. Removing the extension or clearing its local site storage provides a browser-level way to remove the same information.

Procedural parcel generation

Parcel labels are generated by a bundled pseudo-random game system from fixed pools and rules. Normal shifts can produce local zones, priority stamps, damaged seals, hazard flags, different weights, and invalid fictional routes. Later progression unlocks anomaly classes such as Morrow Street, BELOW transfers, inertial-weight mismatch, recursive containment, impossible chronology, or operator-addressed parcels.

The pseudo-random seed is part of local game state so the simulation can progress consistently. It is not a device fingerprint and is not combined with browser characteristics, IP address, hardware identifiers, or webpage information.

Scale, tracking, and X-ray instruments

The Scale button reads fictional weight properties already stored on the current game parcel. The Tracking button formats fictional depot timestamps and route codes. The X-ray button reveals fictional content classifications, acoustic values, or impossible internal-volume readings after the instrument is unlocked.

These features do not access a physical scale, camera, X-ray machine, microphone, barcode scanner, Bluetooth accessory, USB device, shipping API, or operating-system sensor. The names are part of the simulation interface.

Routing rule engine

The expected bin for each parcel is calculated locally from the current routing-card revision and the parcel’s generated flags. Hazard markers route to Special, damage or very heavy printed weight can route to Hold, priority can route to Express, invalid ordinary addresses can route to Return, and ordinary Zone A–C parcels route to Local.

Later rule revisions add fictional containment exceptions such as BELOW transfers or depot-contained parcels. These changes are deterministic game rules associated with narrative progression, not policy updates received from an external depot.

Network behavior

Parcel 17 does not need a network connection for gameplay and does not use fetch, XMLHttpRequest, WebSocket, remote JavaScript modules, carrier APIs, cloud saves, or online leaderboards. Sorting decisions and generated parcel records remain inside the extension origin.

Because the game does not transmit the queue, we do not receive fictional addresses, routing decisions, accuracy, anomaly encounters, play duration, IP addresses, or browsing activity from Parcel 17 itself.

The Chrome browser may independently perform extension installation or update checks as part of the browser platform. Parcel 17 does not use those requests as a game-data channel.

Analytics and advertising

Parcel 17 includes no advertising SDK, analytics SDK, attribution library, engagement tracker, fingerprinting routine, or sponsored parcel system. There is no remote event when a user sorts a package, makes an error, opens an instrument, reaches a narrative stage, or resets the desk.

The extension does not sell or rent gameplay information. With no application-level transmission, there is no remote routing-history dataset created by the game.

Webpage and browsing access

Parcel 17 runs only in its extension popup and does not inject into the active tab. It does not read shopping pages, shipping pages, webmail, browser history, bookmarks, downloads, cookies, forms, page text, tracking numbers, or addresses from websites.

The fictional labels on the desk cannot be populated from a webpage because the extension deliberately lacks the browser permissions and code paths that would be required to collect such information.

User controls and invalid state handling

The routing card exposes the currently active game rules. The player can inspect the current parcel, choose a bin, and reset the local desk. Accuracy and processed counts are visible so that game consequences are understandable without hidden remote scoring.

If the stored JSON is absent or fails the game’s basic save validation, Parcel 17 creates a new local shift. It does not attempt to repair a save by contacting a server or importing data from another browser source.

Children and age considerations

The extension is a general-audience local game. It is not designed to request a child’s name, email address, location, school, contacts, photographs, or other identifying information. The game does not provide chat, social posting, public profiles, matchmaking, purchases, advertising, or account creation.

Because no information is transmitted to us, the extension does not build a remote profile of a child or adult player. A parent or guardian who wants to remove the game’s local progress can use the reset control or remove the extension and its local site data through the browser.

Security model

The extension has a deliberately small attack surface: it requests no Chrome permissions, does not inject into websites, does not load executable code from the Internet, and does not accept network-delivered game state. Its HTML, CSS, JavaScript, icons, and game rules are packaged with the extension.

Local browser storage is not a secure vault for secrets. The game therefore does not ask the player to enter passwords, financial details, private notes, authentication tokens, or other sensitive material. Progress data should be treated as ordinary local game state.

No security system can guarantee absolute protection against compromise of the device or browser itself. The policy describes the extension’s own behavior, not the security of the operating system around it.

Third parties and service providers

The extension does not include advertising SDKs, analytics libraries, crash-reporting clients, social SDKs, payment processors, cloud databases, external fonts, remote game engines, or third-party tracking pixels. No third party is given game telemetry by the extension because the extension does not transmit game telemetry.

Chrome and the operating system may independently provide platform-level services such as extension installation, update delivery, browser storage, process isolation, or crash handling. Those are browser/platform functions rather than data integrations implemented by this extension.

Policy changes

If a future version changes what information the extension handles, adds a permission, introduces an online service, or materially changes retention behavior, this policy should be updated before or with that release. The effective date and version record at the top are intended to make that change visible.

A cosmetic rewrite of the game interface does not itself change privacy behavior. A change from local-only processing to network processing would be material and would require a corresponding disclosure.

Contact and questions

Questions about this privacy policy or the extension’s behavior can be sent through the support contact associated with the extension’s official Chrome Web Store listing. Using the listing contact avoids embedding an unrelated personal address in the game package and gives users a channel associated with the published product.

When asking a privacy question, players do not need to send save data, screenshots, browsing history, or device identifiers. A description of the concern and the extension version is normally sufficient.