Privacy Policy
Learn how RetroPlayer handles comments, contact messages, cookies, browser storage, usage statistics and privacy requests.
Updated
Updated: 2026-11-12.
Scope and contact
This policy describes information handling on RetroPlayer (https://retroplayergame.com). For privacy questions or requests, use the contact form. Do not include passwords or unnecessary identity documents.
Information and purposes
Page and game requests involve network addresses, paths and browser request information for delivery, troubleshooting and security. Comments include nicknames, text, language and time; approved comments are public. Contact messages include a name, optional email, category, subject and text and are available to authorized administrators, not public comments. Administrator authentication and moderation records support site management. Abuse prevention uses source-derived identifiers, content digests and counters; these identifiers are not fully anonymous.
Cookies and local storage
The language cookie remembers manual selection for up to 365 days. Administrator authentication and antiforgery cookies protect the backend; administrator authentication lasts two hours. Browser localStorage stores favorites and a submitted comment nickname. EmulatorJS may use localStorage and IndexedDB for settings, caches and game progress. Favorites and saves do not automatically synchronize between devices. Back up saves before clearing site data.
Usage statistics and third parties
The site records aggregate page views and game-start callbacks for usage statistics. The statistics module adds no visitor tracking cookie and does not retain IP addresses or complete request URLs. This does not mean hosting or security logs never process IP addresses. External images, links or emulator-related requests may disclose network and request information to their providers. Hosting providers, storage locations, backup arrangements and production advertising configuration are not fully documented here; no specific country of storage is promised.
Retention and requests
Comments, messages, handling records and source counters have no implemented automatic expiry deletion. Hiding or archiving and rate-limit resets do not delete records. A fixed retention period and backup deletion schedule have not been specified. Use the contact form to request access, correction, deletion or removal from public display of your information. Clearing browser data does not delete server submissions. There is no visitor self-service deletion interface.
Security, children and updates
Access controls, password hashing, antiforgery protection and rate limits reduce risk but cannot guarantee absolute security. Age-verification and parental-consent workflows are not implemented. Contact the administrator about inappropriate personal information submitted by a child. This policy will be updated when information handling changes; check the date above.