Policy / Privacy
Your files stay
on your device.
This page explains the information used by the VL.MR collection site. Individual playable releases may publish additional details for their saves and community features.
Local preferences
VL.MR stores interface sound and intro preferences in your browser. Playable releases may use browser storage for settings, save data, unlocked stages, and personal bests. Those features are documented on each release’s privacy page.
Optional accounts
If you choose to sign in with Discord, VL.MR stores an internal account ID, the name, email address, and avatar supplied by Discord, session records, your chosen profile name, handle, short bio, and synced interface preferences. Discord processes the sign-in under its own privacy terms. VL.MR does not receive or store your Discord password.
Community messages
Anyone may read the Community channel. Posting requires a VL.MR account. A message stores its text, the posting account, the public profile display name, and its timestamp. Messages and profile names are public. The channel uses manual refresh rather than automatic polling.
Signed-in members may privately report a message or hide another member. A report stores the reporting account, message, reason, and review state. A block is visible only to the blocking account. Moderators may mark a message as removed and retain a limited audit event for safety and abuse prevention. Deleting your account removes its Community messages, reports, and blocks. Account exports include messages posted by that account.
Beta access and VLMR Signal
A lab-access request stores the requesting account, the note and device description you provide, confirmation that you are authorized to use the software you select, review status, and review timestamps. Approved access is represented by an account entitlement and a public Beta Tester badge. Administrators can approve, decline, revoke, and audit access.
Joining the VLMR Signal interest list stores only the account and time of registration. It is not a subscription or payment record, and no payment information is currently collected.
Account security and retention
Session and OAuth records are used to keep you signed in and protect account actions. OAuth token values are encrypted before database storage. Account security and moderation events may be retained in a limited audit log without message content. Signing out deletes the current session. Deleting the account removes the profile, sessions, preferences, beta records, badges, entitlements, reports, blocks, and Signal interest.
Game files
When a compatibility experiment asks for software from your device, selection and preparation happen locally in the browser. VL.MR does not upload, retain, provide, or link to commercial game files, console firmware, encryption keys, or extracted proprietary assets. Private access controls only VLMR-authored presentation code and appropriately licensed runtime components.
Advertising and consent
VL.MR is being prepared for Google AdSense. Once advertising is activated, Google and its partners may use cookies, local storage, device information, and network information to provide, measure, and protect advertising. Visitors in the EEA, the United Kingdom, and Switzerland will be shown a Google-certified consent message before consent-dependent advertising storage is used.
Advertising is not currently loaded on this collection page. This notice will be updated when serving begins.
Infrastructure logs
Hosting and security providers may process standard request data such as IP address, browser information, requested URL, timestamps, and security signals to deliver the site, prevent abuse, and diagnose failures.
Your choices
You can clear local site data through your browser, download an account export, or permanently delete the optional account from the Profile channel. When the consent message is active, you can decline consent or revisit your choices through the privacy controls provided on the site.
Contact
Privacy questions can be sent through the contact page.