This policy explains the account, security, research, contest, game, device, support, and consent-gated analytics data used to operate the beta.
This is an expanded beta draft. It is not binding until the operator identity, contact details, retention schedule, processor inventory, jurisdiction, effective date, and legal review are finalized and published.
This draft explains how RetroStock Arcade is intended to collect and use personal data across the website, account features, research, community, contests, games, and support.
The operator identity, registered address, privacy contact, data-protection authority, retention schedule, processor inventory, transfer safeguards, and effective date are still pending. This page is informational and is not a final jurisdiction-specific Privacy Policy until those details and counsel approval are published.
| Category | Examples | Source |
|---|---|---|
| Account | Email, username, avatar, provider, verification status | You or an identity provider |
| Security and sessions | Password hash, session records, login history, IP address, user agent, failed-login and lockout data, two-factor settings | You, your device, and the Service |
| Preferences and local state | Theme, sound, refresh, compact mode, logo and price display, analytics consent, recent symbols, game scores, and chart drawings | Your browser or account |
| Research and community | DD, notes, titles, citations, tags, visibility, revisions, comments, reactions, follows, bookmarks, reports, and share links | You and other users |
| Contests and games | Predictions, picks, confidence, scores, run tickets, input logs, replay checksums, and anti-cheat signals | You and the Service |
| Usage, diagnostics, and support | Requested symbols, charts, refresh activity, consent-gated product events, scrubbed client errors, support messages, reports, appeals, and attachments | Your device, the Service, and approved providers |
| Purpose | Typical legal basis |
|---|---|
| Provide accounts, preferences, research, contests, and games | Performance of a contract or steps requested before a contract |
| Authenticate users, prevent abuse, moderate content, and secure systems | Legitimate interests, balanced against user rights |
| Provide requested support and communications | Contract, legitimate interests, or consent depending on the communication |
| Comply with legal obligations and protect legal claims | Legal obligation or legitimate interests |
| Optional product analytics | Consent, requested before analytics loads |
We share only what is reasonably necessary with:
The beta does not sell personal data for money and does not enable advertising or creator payments. Any future monetization or advertising requires a new privacy review and notice. The final policy will identify the operator's actual processors, independent third parties, locations, and contractual safeguards.
Public DD, posts, comments, reactions, profile details, contest standings, and leaderboard entries can be viewed, copied, indexed, or reshared by others. Deleting content from the Service cannot remove copies made by third parties. Private and unlisted research is access controlled, but no online storage can be guaranteed absolutely confidential. Do not submit confidential, sensitive, or material non-public information.
The operator is still approving the retention schedule. Until that schedule is published, data is intended to be kept only for as long as reasonably necessary for the purposes above, including security, fraud prevention, disputes, backups, and legal obligations.
The schedule must address at least:
The current public UI does not provide a complete self-service export and deletion workflow. A final policy will publish the approved privacy-request channel and actual deletion behavior. Public copies made by third parties and data retained under a legal or security exception may remain after removal from the Service.
The Service uses administrative, technical, and organizational safeguards appropriate to the data and risk, including secure session cookies, CSRF protection, password hashing, authentication controls, rate limits, redacted logging, and abuse monitoring. No system is completely secure. The operator will provide a security and privacy contact before binding publication and will handle reportable incidents as required by applicable law.
Data may be processed in countries where the operator and its configured providers operate. The final policy will identify relevant locations and, where required, the approved transfer mechanism and safeguards, such as an adequacy decision or appropriate contractual terms.
Depending on your location and the applicable law, you may have the right to be informed, access your data, correct it, request deletion, restrict processing, receive a portable copy, object to processing, withdraw consent, and challenge certain automated decisions.
Requests should use the dedicated privacy channel published by the operator. We may verify identity before responding and may retain or restrict data where law, security, or another person's rights requires it. Requests are generally answered without undue delay and within the period required by applicable law.
You may complain to the data-protection authority in your country or place of residence. The final policy will name the relevant supervisory authority and any appointed data protection officer, if applicable.
The beta uses automated checks for authentication, rate limiting, contest validation, game replay verification, and moderation support. It is not intended to make decisions based solely on automated processing that produce legal or similarly significant effects. The final policy will explain any material change to this position and the available safeguards.
The Service is intended for adults aged 18 or older. We do not knowingly collect personal data from children. If you believe a child has provided data, use the privacy contact once it is published.
We will post updates with a revised review or effective date. Material changes will receive additional notice where required. The operator identity, postal address, privacy email, support channel, and effective date remain pending and must be completed before this document becomes binding.
General product questions can be sent through the contact page. Do not use the current simulated contact form as the sole channel for a statutory privacy request.
Optional product analytics is currently disabled or awaiting your choice.