1. Overview
Starwreck is a fictional spaceship survival and salvage game that runs inside its Chrome extension popup. Ship resources, fictional crew, module condition, sector events, and encounter choices form the local game state.
This document is intentionally detailed. It explains both what the extension does with information locally and what it does not send to the developer. The goal is to make the relationship between gameplay, saved state, browser storage, permissions, and privacy understandable without requiring the user to infer behavior from the source code.
2. Scope and application of this policy
This Privacy Policy applies only to the Chrome extension identified on this page, including its packaged popup interface, game logic, local state, visual assets, and interactions that take place inside the extension. It describes the practices of the extension developer with respect to information processed by the extension itself.
It does not govern Chrome, the Chrome Web Store, Google services, your operating system, your device manufacturer, your internet service provider, security software, backup software, or unrelated websites and applications. Those products can have their own independent data practices. The fact that you use this extension inside Chrome does not mean that the developer controls Chrome's own diagnostic, synchronization, account, or store-related processing.
If you contact the developer directly by email, the contents of that email are outside the automated game data described in this policy. Such correspondence may naturally contain your email address and whatever information you choose to include. It will be used only to respond to the communication, troubleshoot an issue, handle a privacy request, or maintain necessary records of the conversation.
3. Privacy design principles
The extension is designed around data minimization. Its core gameplay does not require an account, a remote profile, cloud saves, a developer-operated backend, advertising identifiers, user analytics, or access to the websites you visit.
- Local-first gameplay: game calculations and saved run state are handled on the user's device.
- No account system: there is no registration, username, social login, or developer-managed player identity.
- No host access: the extension does not request permission to read or modify arbitrary websites.
- No telemetry: the current version contains no analytics SDK or event-reporting endpoint.
- No advertising: the extension contains no ad network, behavioral advertising system, or retargeting technology.
- No remote executable code: the game's JavaScript, styles, and icons are packaged with the extension.
4. Information collected by the developer
The current version does not collect personal information or gameplay data for the developer. There is no developer-operated server receiving a copy of your run state, score, tactical decisions, generated map, saved progression, or interaction history.
The extension does not intentionally collect your name, postal address, email address, telephone number, precise or approximate location, IP address for profiling purposes, payment information, financial accounts, health information, biometric information, passwords, authentication tokens, private messages, browser history, search history, active-tab content, or advertising identifiers.
Because the game does not transmit its local save state to the developer, the developer cannot remotely inspect your current run, restore it from a cloud account, rank it on an online leaderboard, or associate it with your real-world identity.
5. Data-category disclosure
| Category | Collected / transmitted to developer? | Current behavior |
|---|---|---|
| Personally identifiable information | No | No registration or identity profile is created. |
| Authentication information | No | No passwords, OAuth tokens, session credentials, or account secrets are requested. |
| Financial and payment information | No | The extension has no payment form or in-extension purchase processing. |
| Health information | No | No medical, fitness, biometric, or health records are requested. |
| Location | No | No geolocation permission or location API is used for gameplay. |
| Browsing history | No | The extension does not request Chrome history permission. |
| Website content | No | The game operates in its own popup and does not inspect page text, forms, URLs, or DOM content. |
| Personal communications | No | No email, chat, social message, or communication content is accessed by the game. |
| Gameplay telemetry | No | Run actions are used locally for game logic and local saves; they are not sent to analytics services. |
| Advertising / profiling data | No | No advertising SDK, fingerprinting, retargeting, or cross-site user profile is present. |
6. Starwreck local game state
Starwreck is a compact spaceship survival and salvage game. Its run includes ship resources, crew status, modules, hazards, sector progress, and event decisions. To preserve the run between popup sessions, the game stores its current state locally under starwreckStateV1.
What the saved state can contain
- current sector and run-progress values;
- ship Hull, Oxygen, Power, Fuel, Scrap, and related resource totals;
- module condition, damage, fire, or repair-related state;
- crew names used by the game, fictional traits, and hit-point values;
- current tab/view inside the game interface;
- the active salvage or encounter state and whether it has been resolved;
- short gameplay log/status text needed to explain the latest event;
- run-over or extraction-related status.
The names and traits of crew members are predefined fictional game content. Starwreck does not ask the user to enter a real name, employee information, contact list, or personal biography for crew members.
Event decisions
Choices such as docking with a derelict, scanning, salvaging, leaving a sector, repairing a module, or responding to a hazard are processed locally and can alter the saved run. Those choices are not transmitted to the developer as behavioral analytics.
Resource and hazard information
Terms such as Oxygen, Hull, Radiation, Reactor, Fuel, Crew HP, Fire, and Breach are fictional game-state variables. They do not represent health monitoring, device battery telemetry, real environmental sensors, location, or information about an actual spacecraft or vehicle.
7. Starwreck storage, persistence, and retention
The current run is kept in browser-managed local storage so that closing the popup does not automatically destroy the ship state. There is no developer cloud-save database in the current version.
The local run can persist until game actions overwrite it, the user restarts, browser storage is cleared, the browser profile is reset, the extension is removed, or Chrome otherwise clears extension-origin data. Browser-managed backup or enterprise profile behavior, if any, is controlled by Chrome or other software and not by the Starwreck developer.
Starwreck does not currently provide an online account for restoring a lost local run. If local browser data is cleared, the developer ordinarily cannot reconstruct that run because no copy was uploaded to a developer server.
8. Chrome permissions and browser access
The current Manifest V3 package requests no Chrome extension permissions and no host permissions. It does not request tabs, history, activeTab, scripting, cookies, downloads, notifications, geolocation, or storage through the Chrome extension permission system.
The game can still use ordinary web-platform features available to its own popup, such as JavaScript timers, DOM rendering, and localStorage scoped to the extension's own origin. Using its own localStorage does not give the extension permission to read website storage belonging to unrelated sites.
9. Network activity and external services
The current game code is designed to operate without a developer backend. It does not use fetch, XMLHttpRequest, WebSocket, or a remote API to upload gameplay state. It does not need an internet connection to calculate its core gameplay after the extension has been installed.
There are no third-party analytics scripts, cloud-save APIs, advertising endpoints, social-media SDKs, remote fonts, remote JavaScript libraries, or externally hosted gameplay assets in the current package.
Chrome itself may communicate with Google for browser, extension-store, security, update, or account-related purposes. Your operating system, DNS provider, security tools, or network infrastructure may also create network records independently. Those activities are not initiated as gameplay telemetry by this extension and are outside the developer's control.
10. Analytics, tracking, advertising, and profiling
Analytics
The extension does not currently include Google Analytics, Firebase Analytics, Mixpanel, Amplitude, Segment, PostHog, or a comparable analytics or crash-reporting SDK. The developer does not receive automatic reports about which buttons you press, how long you play, how far you progress, or how often you open the popup.
Tracking and fingerprinting
The extension is not designed to fingerprint the browser or device, correlate your activity across websites, or create a persistent advertising identity. It does not inspect unrelated browser tabs for behavioral profiling.
Advertising
The extension does not display third-party advertisements and does not sell access to its users for targeted advertising. There is no advertising auction, retargeting pixel, sponsored-content SDK, or data-broker integration in the game.
12. Security and data minimization
The security model intentionally minimizes exposure by avoiding a remote account system and broad Chrome permissions. Game state is kept within the extension's browser context instead of being transmitted to a centralized gameplay server.
The extension is packaged with its own scripts, styles, and icons. Avoiding remote executable code reduces dependence on external content that could change independently of the installed package.
No software can be guaranteed absolutely secure or defect-free. Users should keep Chrome updated, install extensions from sources they trust, use appropriate device security, and understand that anyone with access to the same browser profile or local device may potentially gain access to locally stored browser data.
13. Children's privacy
The game does not create accounts, collect age information, request contact details, provide user-to-user messaging, or build advertising profiles. It is not designed to solicit personal information from children or adults.
If a parent, guardian, or other person believes that personal information was sent directly to the developer outside the automated extension—for example in a support email—they may contact the developer to ask questions about that communication.
14. User choices and privacy rights
Depending on jurisdiction, privacy laws can provide rights of access, correction, deletion, restriction, portability, or objection regarding personal information held by an organization. Because the extension does not upload its local game state to the developer, there is ordinarily no developer-side gameplay profile to access, export, correct, or erase.
You retain practical control over the local save state through your browser and device. You can reset the game using in-game controls where provided, clear site/extension storage through browser tools, use a fresh browser profile, or uninstall the extension. These actions can remove or replace local progression depending on Chrome's storage behavior and the action chosen.
If you separately send the developer an email, you can contact the developer regarding that correspondence at tuytrung179227@gmail.com.
15. International use and data transfers
The extension can be used from different countries, but its core save-state design does not depend on sending gameplay records to a developer server in another jurisdiction. Local state remains associated with the browser environment in which the extension is used.
If you choose to copy, screenshot, back up, or otherwise share game information using separate software, those later actions may involve data processing or international transfers by the services you choose. Such processing is not performed by the extension itself.
16. Changes to this Privacy Policy
This policy may be updated to improve clarity, reflect changes to the extension, respond to platform requirements, or address changes in applicable law. The effective date at the top of the page identifies this version.
If a future version introduces a developer backend, online leaderboard, cloud synchronization, analytics, advertising, new Chrome permissions, website access, or other materially different data handling, the privacy disclosures should be revised to accurately describe those practices before or at the time they are introduced.
Users are encouraged to review the policy when installing a materially updated version of the extension.
17. Technical architecture and separation from browsing data
The extension's user interface is an extension popup loaded from files bundled inside the installed package. Game logic runs in that isolated extension context rather than as a content script placed into arbitrary websites. This architecture is important for privacy because the game does not need to inspect or manipulate the page that happens to be open behind the popup.
The current manifest does not grant the extension broad host access. The game therefore does not depend on reading page source, form values, page titles, page URLs, cookies, local storage belonging to websites, or DOM events generated by unrelated sites. The local save described in this policy belongs to the extension's own origin.
The game's local state is serialized as ordinary values needed to reconstruct the fictional run. It is not intentionally combined with browser fingerprints, advertising IDs, IP-based profiles, Chrome account identifiers, or cross-site identifiers. The developer has not built a mechanism that maps the local save to a named user.
18. Direct communications with the developer
If you choose to email the developer, the email service you use will necessarily transmit information required to deliver that message, such as your email address, message content, and standard mail-routing metadata. That processing happens because you chose to communicate outside the extension's automated gameplay.
Information voluntarily sent in a support or privacy email may be used to answer the question, investigate a bug, reproduce a reported issue, maintain the security of the extension, or document the handling of a privacy request. Users are encouraged not to include passwords, payment information, government identifiers, medical records, or other sensitive information that is not needed to explain the issue.
The developer does not use support correspondence to create advertising profiles or sell mailing lists. If you want to ask about deletion of a direct email conversation, contact tuytrung179227@gmail.com; legal, security, abuse-prevention, or recordkeeping obligations may affect whether a particular communication can be immediately deleted.
19. Clearing local game data
The game does not provide a developer-side account dashboard because the save exists locally. Users who want to remove local gameplay state can use the in-game reset function where available or Chrome's controls for clearing extension/site data. Removing the extension can also remove extension-associated local data, subject to Chrome's own profile and data-management behavior.
Before clearing browser data, understand that local progress may be permanently lost. Because the developer does not receive a cloud copy of the run, the developer ordinarily cannot restore locally deleted progress.
If Chrome is managed by an employer, school, administrator, family-management system, backup application, or synchronized profile environment, additional copies or policies may exist outside the extension. The developer does not control those systems and cannot guarantee deletion from independent backups or browser-management products.
20. Automated decision-making, AI, and generated content
The game uses deterministic and randomized local game rules to calculate outcomes, procedural states, enemy behavior, puzzle behavior, resource changes, and other gameplay consequences. These calculations are entertainment mechanics, not automated decisions about employment, credit, housing, insurance, education, medical care, legal status, or another real-world eligibility decision.
The current extension does not send prompts, gameplay text, save files, or player behavior to a remote generative-AI service. It does not use an external large language model, remote image generator, or AI profiling provider as part of gameplay.
Random or procedural outcomes should not be interpreted as factual claims about the user. They are generated solely for entertainment inside the fictional game system.
21. Payments, purchases, and virtual items
The current extension does not process credit cards, bank information, cryptocurrency wallets, subscriptions, or in-app purchases. Any fictional credits, shards, scrap, tools, resources, or similar game values are gameplay variables only and have no cash value, redemption right, ownership claim, or financial-account function.
The extension does not currently operate a marketplace where users buy, sell, trade, or transfer virtual items to other users. Local progression is not designed as a financial asset.
23. Chrome Web Store disclosures and policy consistency
The developer intends the privacy statements shown on the Chrome Web Store, the permissions requested by the manifest, and this Privacy Policy to describe the same underlying behavior. The extension's current single purpose is entertainment through its local game mechanics; broad access to unrelated browsing data is not required for that purpose.
If a future release changes the manifest or introduces data collection, the related store disclosures and this policy should be reviewed together so that users are not presented with contradictory information.
24. Contact
For privacy questions, policy questions, or requests concerning information you may have sent directly to the developer, contact:
22. Social features and public disclosure
The current version does not contain multiplayer chat, public profiles, friend lists, user-generated public posts, cloud leaderboards, or automatic sharing of gameplay. Other users do not receive your local save through the extension.
If you voluntarily take a screenshot, record the popup, describe your run online, or share information through another application, that disclosure is controlled by you and by the separate service you use. This Privacy Policy does not control information that you independently publish outside the extension.