Privacy Policy

01 / Privacy Policy

Who operates VoidRoom?

VoidRoom is operated by Mr Craig Tunstall, operating VRC.LOL, who is the controller of the personal information described here. This policy covers the VoidRoom game on Windows and Meta Quest, its website, multiplayer services and support.

For privacy questions or data requests, email privacy@vrc.lol. For game support, email support@vrc.lol. These public addresses forward to the operator’s Yahoo mailbox. Do not send passwords, recovery codes, access tokens or identity documents.

02 / Privacy Policy

Information we collect and process

• Account and sign-in: your VRC.LOL account identifier, Display Name, approved permissions and authentication/session records. Passwords and passkeys are handled by VRC.LOL Identity; VoidRoom receives an application session after you approve access. Account recovery email and sign-in information are managed in the central account system.
• Your player and creations: avatar choices, player profile, room ownership and permissions, saved drafts, room versions, uploaded creation files and publication/moderation status.
• Multiplayer: room/instance membership, network connection information, avatar position, head/controller poses, movement, expressions, gestures and gameplay actions needed to display and synchronise players.
• Communication: room text messages and optional microphone audio. Friend relationships, blocks and private messages are stored where you use those features. Reports contain the reporting account, reported account/room, the supplied reason/details and moderation history.
• Technical information: IP addresses, requests, service timestamps, connection errors, application/build versions and diagnostic records used to operate and secure the service. Local game logs may include account identifiers and connection details.
• Support: the contact address, message and attachments you choose to send, and correspondence needed to handle your request.

03 / Privacy Policy

How we use this information

We use account, player and room information to provide sign-in, restore your saved avatar and creations, enforce room permissions, connect you to instances and deliver multiplayer and communication features. These core operations support the service you request.

We use technical records and reports for service security, abuse prevention, moderation, troubleshooting and protecting players, relying on legitimate interests where applicable. Support correspondence is used to answer requests and meet applicable legal obligations. Optional microphone access is controlled by your device permission and in-game voice settings; you can play without granting it. We do not sell personal information or use it for targeted advertising.

04 / Privacy Policy

Microphone, tracking and room chat

When voice is enabled, microphone audio is captured and transmitted through the room’s game server to other players. Muting stops gameplay transmission. In push-to-talk mode, releasing the talk control stops transmission. The microphone test processes audio locally to show/test the input; it is not sent as room speech. VoidRoom’s voice implementation uses short-lived playback buffers and does not save voice recordings to its application database.

Head and controller tracking are used for gameplay and avatar synchronisation; remote players receive the poses needed to display your avatar. The game does not use those poses to establish your real-world identity. Room text chat uses bounded in-memory history in the active session. Private messages, saved room content, support correspondence and moderation reports have separate persistent storage.

Other players may record or copy what they see or hear using their own tools. Avoid sharing sensitive information in rooms or messages. Microphone permissions can also be removed in your device settings.

05 / Privacy Policy

Who can receive information?

Players in an instance can see your Display Name, avatar, actions and messages, and hear transmitted speech. Publicly published rooms and creations are visible to their audience. Authorised administrators/moderators can access information needed to operate the service, review reports and enforce rules; room roles grant only their applicable permissions.

VRC.LOL Identity provides central authentication. Our self-managed services use dedicated hosting supplied by Zare in the United Kingdom; game downloads also use OVH infrastructure. Published room/creation files may be delivered through mod.io. Meta operates the Quest platform/store and processes its own platform information under Meta’s privacy policy; the current VoidRoom sign-in uses VRC.LOL, not a Meta social login.

Contact email is delivered through our mail service to Yahoo. Providers and services may process information internationally; UK hosting does not mean all information stays in the UK. See Yahoo’s correspondence privacy notice. We may disclose information where required by law or necessary to protect users and the service.

06 / Privacy Policy

Cookies, device storage and retention

The website uses an essential encrypted session cookie for sign-in and request protection, with a configured lifetime of up to 14 days. Authentication steps may expire sooner. The game stores preferences and remembered account/session information on your device; signing out removes the usable game sign-in, while device files and unsaved drafts may remain until you remove them or uninstall/clear application data.

Transient audio, tracking and room-chat buffers are held for live operation and are replaced or cleared as sessions end. Saved account/player records, room drafts/versions, relationships, private messages and reports persist until removed through an available control or a verified request, subject to records needed for security, moderation or legal obligations. Removing an installation does not delete server-side records.

There is currently no single verified automatic expiry covering all persistent records, shared infrastructure logs or backups. Retention depends on the service purpose, whether the record is still needed, a deletion request, and any necessary legal/security hold. We do not promise a fixed deletion date for every backup or third-party copy. Deleted data must not be put back into active use through routine restoration. We will explain relevant retained categories and reasons when responding to your request.

07 / Privacy Policy

Request access, correction or deletion

We will verify ownership using your account or a suitable existing contact method before disclosing or deleting information. We will review the associated profile, saved creations, relationships/messages and other stored data, and explain any records that must be retained or information held by an independent provider. Public files distributed through mod.io may require removal there as well. Copies other players have made cannot necessarily be recalled.

You can request access, correction, erasure, restriction, portability or object to processing where the law provides these rights. Optional microphone permission can be withdrawn in device settings. Revoking VoidRoom access in VRC.LOL stops that permission; it is not itself a data-deletion request. Requests are handled within applicable legal time limits, normally one month for UK data-rights requests, with any lawful extension explained.

You may complain to the UK Information Commissioner’s Office or your relevant supervisory authority.

08 / Privacy Policy

Age requirements and changes

VoidRoom’s current preview is intended for users aged 13 or older, or the higher minimum age required by their region or platform. It is not intended for children under that minimum age. If you believe a child has supplied information contrary to this requirement, contact privacy@vrc.lol.

We will update this notice when practices change and show the effective date. Material changes will be explained through the website or appropriate service notice. This policy does not replace independent platform providers’ policies.