Bit Universe for Meta Quest: privacy policy
Effective October 30, 2026. This page covers the standalone Quest edition and its private beta. Other editions use the main Bit Universe policy.
Who is responsible
Bit Universe is made by Kevin Savill, an independent developer. For privacy questions, access, correction or deletion requests, email support@bit-universe.net.
Local gameplay and settings
The app stores up to three gameplay saves, save backups, achievements earned in the game, the last selected slot, audio/display settings, workspace positions and optional room-anchor identifiers on your headset. Gameplay does not use a separate Bit Universe account or a developer-operated server. Standalone Quest saves are separate from PC and phone saves.
Diagnostic logs and any performance observations gathered for testing remain local unless you choose to send a report or use Meta's own reporting tools. We do not run a separate gameplay analytics, advertising or crash-upload service in the Quest app.
Personal data we collect and process through Meta
Bit Universe collects and processes personal data. Its integrated Meta Horizon Platform SDK uses account-linked data to verify ownership and unlock achievements for the signed-in player. Collection includes receiving and handling information through the integrated platform services; it does not require us to save a permanent copy or operate our own server. Account-linked collection is not anonymous. We also collect personal data that you choose to send to support.
The following disclosures cover User ID (USER_ID), User Profile (USER_PROFILE) and Deep Linking (DEEP_LINKING), the three Platform permissions requested by Bit Universe. Meta lists all three for achievements in its Data Use Checkup requirements, Table 1. The information below identifies the data, where collection occurs, how it is used, and what is retained. Fields depend on what Meta supplies and what you choose to send; requesting access does not mean that every available field is retrieved on every launch.
User ID (USER_ID): account-linked data collection
What is collected and where it comes from: the Meta Platform achievement integration handles the signed-in player's app-scoped Meta account identifier together with earned achievement identifiers and unlock results. The account identity comes from Meta's signed-in platform service; earned achievement identifiers come from milestones reached in the game. The game calls Achievements.Unlock and receives its operation result. These account-linked achievement operations involve personal-data collection and processing even though the game does not separately fetch the raw Meta ID through a user API or copy it into a gameplay save.
How it is used: to associate earned platform achievements with the correct Meta account and handle achievement-operation errors. If you supply an account identifier in a support request, we collect and use that copy to identify and resolve your issue or locate information for a privacy request.
Storage and retention: achievement-request state is held in memory during the session. Local saves retain in-game achievement progress, and local diagnostic logs can retain operation results and error messages until replaced or cleared. Meta retains its account, purchase and platform-achievement records under its own controls. Support copies follow the support retention and deletion rules below.
Separate SDK ownership check: the app also initializes the SDK and checks whether the player owns the game. That entitlement check is resolved at the SDK layer and does not require the USER_ID permission or a Data Use Checkup request. It is not the purpose for requesting User ID; that permission is requested for platform achievements.
User Profile (USER_PROFILE): profile information collection
What this permission covers: the player's Horizon username and profile photo made available by Meta's profile services. It is requested to support the Meta platform-achievement integration. What we collect: we collect a Horizon username, profile image or other profile information when you include it in a support message, screenshot or beta-access request. The current game does not separately call profile APIs to download a username or photo or display a player profile. This distinguishes actual collection from the additional fields the requested permission makes accessible.
How it is used and retained: Meta provides the account-associated achievement service. We use profile information you send to identify the affected player, provide requested support or manage beta access. User-provided copies are stored in support correspondence or beta administration until no longer needed for those purposes and any required obligations. They are covered by the deletion mechanism below.
Deep Linking (DEEP_LINKING): launch information collection
What this permission covers: launch type and source, intended in-app destination, opaque launch message/parameters, and any supplied tracking, lobby or match-session identifiers from Meta's launch services. It is requested to support Meta's achievement integration. What we collect: we collect launch information when you send it to support in a description, screenshot or diagnostic file, to investigate problems starting the app or reaching the expected experience. The current game opens its normal title/save flow and does not separately call the launch-details API to read deep-link payloads, implement destination-specific travel, or record those payloads in gameplay saves.
How it is used and retained: the platform permission supports achievements as required by Meta; any launch details you send us are used to troubleshoot the reported issue. Those copies are stored with support correspondence until no longer needed for the request and any required obligations, and can be deleted through the mechanism below. Meta controls information retained in its own launch services.
Who receives collected information
The integrated Meta Platform services communicate with Meta for signed-in ownership verification and achievement unlocks. Meta operates its account, purchase, entitlement, achievement and platform/device-diagnostic services under Meta's privacy policy. Kevin Savill receives the support and beta-administration information you provide. Google Workspace (Gmail) is our service provider for collecting, delivering, storing and managing support email and its attachments. It does not receive an automatic feed of gameplay or platform data from the game.
The Quest app has no developer-operated account server, automatic gameplay analytics or crash-upload service, advertising SDK, in-app purchases, social or multiplayer features, microphone recording or voice chat. We do not sell personal data or use it for advertising. Beta access is managed through Meta release-channel invitations, for which we collect the email address or account information you provide.
Retention, deletion and your choices
Collection and use still occur when information is handled temporarily and discarded. Closing the game ends its in-memory achievement-request state; local gameplay progress, settings and diagnostic files remain until replaced or deleted. Support correspondence is retained only while needed for the request, related support, safety or legal obligations, then deleted. Meta-controlled account and platform records follow Meta's controls.
Players in every country can request deletion of collected personal data under our control, including any User ID, User Profile or Deep Linking information received in support or beta administration. Email support@bit-universe.net with the subject Bit Universe Quest data deletion. The full deletion instructions below explain verification, local deletion, backups and Meta-controlled records. A request does not require a separate Bit Universe account.
Headset, controller and hand input
The app collects and processes headset and controller poses, button input and, when enabled, hand-joint poses and gesture state on the headset to render the view and support pointing, pinching, grabbing and moving the workspace. It does not use this input to identify you or send it automatically to the developer.
Optional Hand input trace is off by default. If you enable it in Controls, hand-tracking and gesture diagnostics are recorded to local CSV files, with a 24 MB limit per session and the current and previous trace retained. Turning tracing off stops new recording; existing files remain until replaced or cleared with app data. Review a trace before choosing to send it to support.
Passthrough and room anchors
Optional passthrough is displayed by the headset's system compositor. The game does not access or record raw camera images, transmit room images to us or share spatial anchors with other players. If you choose room anchoring, the headset's anchor service saves/restores an anchor and the app stores its identifier locally. A virtual environment remains available.
Cloud Backup
Meta Cloud Backup may include app data when enabled. Meta operates this service; it is not live cross-save between devices or platforms. Backup availability and successful restoration depend on Meta and device settings and should be verified before removing important local data.
Support and beta feedback
If you email us, we and Google Workspace (Gmail), our email service provider, collect your email address, message and any screenshots, save files or logs you choose to attach. Google Workspace stores and processes this correspondence for us to deliver, secure and manage support email. Attachments may include headset/device diagnostics, hand-input traces or Meta account information if you choose to send them. Support email is managed in our Savill Interactive Workspace; support@bit-universe.net is an alias into that mailbox. We use them to respond, troubleshoot and improve the game. Include only what is needed: headset model, game version, steps and symptoms. Do not send passwords, payment-card information or unrelated personal/room images. Reports are not sent automatically.
We retain correspondence while needed to handle the request and related support, safety or legal obligations, then delete it when no longer needed. You can request deletion at support@bit-universe.net. We do not sell personal information or use support messages for advertising.
Request deletion and manage your data
Players in any country can request access, correction or deletion of personal data associated with Bit Universe, including any Meta user ID, profile or launch information under our control, beta contact details, support messages and logs or files sent to us. Email support@bit-universe.net with the subject Bit Universe Quest data deletion.
Tell us which data you want deleted and provide the email address used for support or beta contact, or your Horizon username if relevant to locating the record. Do not send your password, payment details or identity documents. We may ask for the minimum additional information necessary to verify that the request concerns your data. We will review the request, delete data under our control that we are not required to retain, and confirm the outcome. If we hold no matching data or a legal obligation prevents deletion, we will explain that. We respond within applicable legal deadlines.
- On your headset: delete a save slot from the title menu to remove that slot's gameplay progress. To clear all local saves, save backups, settings, layouts and diagnostic/hand-trace files, clear the app's storage using available headset controls or uninstall it. We cannot remotely erase files on your headset.
- Meta Cloud Backup: manage or delete retained app backups through Meta's backup/account controls separately. A retained backup can restore local data after a reinstall.
- Meta-controlled platform records: deleting local data does not erase Meta store purchases, account profile information or platform achievements. Use Meta Support and Meta's privacy/account controls for those records. You may also contact us for help identifying the appropriate route; we cannot directly erase records that Meta independently controls.
- Developer-held records: the email request above covers information in our support records and beta administration, including any user ID, profile information, launch information or diagnostics you provided. The current game does not create a separate developer-hosted database of Meta IDs, profiles or deep-link payloads.
There is no separate Bit Universe account to delete. Depending on your location, you may have additional rights, including objection or restriction, withdrawal of consent and complaints to your privacy authority. Contact us to exercise your rights.
Audience
The Quest edition and current private beta are intended for teens and adults aged 13 and over, or the applicable minimum age in the user's region. We do not knowingly request support information from children outside that audience. Contact us if a child has provided information so we can review and delete it as appropriate.
This website
These pages use self-hosted fonts/images, with no analytics, advertising scripts or cookies set by our site code. Cloudflare processes IP addresses, request information and security diagnostics to host and protect the site under Cloudflare's policy. Email links open your chosen mail application and do not automatically send a message.
Changes and contact
We update the effective date when this policy changes and explain material changes in release notes or another appropriate notice. Contact: support@bit-universe.net.