PastPlay Chrome Game Extensions
Privacy Policy
This page is the dedicated privacy policy for the publisher’s offline Chrome game extensions. It is not a homepage, game page, installation page, or promotional landing page.
This shared policy covers current and future extensions that link directly to this page and follow the practices described below. It intentionally does not list individual extension names or Chrome Web Store IDs.
Plain-language summary
- The extensions do not require an account and do not collect names, email addresses, payment information, precise location, browsing history, website content, or personal communications.
- Game saves, scores, emulator data, control settings, favorites, and audio preferences may be stored locally on the user’s device.
- Local gameplay data is not sent to the publisher, sold, used for advertising, or used to build a user profile.
- The extensions contain no advertising, analytics, telemetry, tracking SDKs, or remote executable code.
- Opening an external webpage creates a normal HTTPS request to that website. Standard server and security logs are explained separately below.
Data practices
| Data category | Practice |
|---|---|
| Identity and account data | Not collected. No account or login is required. |
| Financial, health, location, and communications data | Not collected. |
| Browsing history and website content | Not read, monitored, collected, or changed by the extensions. |
| Gameplay and preference data | May be stored locally in browser-managed extension storage solely to provide game functionality. |
| Analytics, advertising, and profiling | Not used inside the extensions. |
| External webpage request data | When a webpage is opened, its host and security providers may process ordinary request information such as IP address, browser type, requested URL, and request time. |
Local gameplay data
Some games need local storage for save states, emulator save data, scores, control mappings, favorite status, or audio preferences. This data is used only to run the game or remember settings selected by the user.
Local gameplay data remains on the user’s device. It is not transmitted to the publisher or third parties and is not used for analytics, advertising, tracking, or profiling. It remains until the user clears the extension’s stored data or removes the extension. Because the publisher does not receive this data, the publisher cannot view, export, correct, or delete it remotely.
Permissions and browser access
The covered extensions do not request broad access to websites, browsing history, cookies, downloads, bookmarks, or user accounts. They do not inspect the content of open tabs.
An extension may open a clearly identified PastPlay page after the user selects a link. It may also open a getting-started page after a fresh installation and register a goodbye page that Chrome opens after removal. These actions only open a URL; they do not give the extension access to the content of the opened page or other tabs.
Packaged code and network activity
Game and emulator code is included inside each extension package. The extensions do not download or execute remote JavaScript or WebAssembly code. Requests used to load packaged files remain within the extension package.
If a user opens PastPlay, a welcome page, a goodbye page, or another clearly labeled external link, the browser connects directly to that site over HTTPS. The extension does not attach local saves, scores, preferences, advertising identifiers, or persistent extension-specific user identifiers to the URL.
Website and security logs
External websites are separate from the offline game extension. Like other public websites, their hosting, content-delivery, and security providers may automatically process standard request information such as an IP address, browser type, requested URL, response status, and request time. This information is used to deliver the requested page, prevent abuse, and maintain security.
The publisher does not combine these standard web logs with local gameplay data and does not use them for behavioral advertising or user profiling. The publisher does not maintain a separate extension analytics database. Infrastructure providers may temporarily retain security logs according to their operational and legal requirements.
Use, sharing, and sale of data
The publisher does not sell, rent, or trade personal data. Local gameplay data is not disclosed because it is not received by the publisher. Standard web request data may be processed only by the hosting, content-delivery, and security providers needed to deliver and protect a webpage, or when disclosure is required by law.
User choices and deletion
Users can remove locally stored game data by clearing the extension’s storage in Chrome or uninstalling the extension. Users can avoid external website requests by not selecting external links; the installation and removal pages may still be opened automatically by Chrome as described above.
For questions about this policy or standard website data, email [email protected]. Include enough information to identify the request, but do not send passwords, payment information, or game save files.
Children’s privacy
The covered extensions do not knowingly collect personal information from children or from any other users.
Security
External pages use HTTPS. The extensions use packaged code and local browser-managed storage to reduce unnecessary data transmission. No method of storage or transmission is guaranteed to be completely secure, but the publisher limits data handling to what is necessary for the described functionality.
Changes to this policy
This policy will be updated before a covered extension introduces materially different data practices. The Last updated date at the top of this page will identify the current version. An extension with different practices must use an updated or separate policy.