Bloopers VR — Privacy Policy

Privacy at a glance

Bloopers VR is a virtual reality obstacle-racing game with Solo Practice and optional multiplayer. We use Meta Platform services to verify access to the game at startup. No separate game login is required.

The current version does not request your Meta account User ID, username, or profile photo. Names, character colors, and rewards are saved locally using an app-generated identifier. Multiplayer uses Normcore and room-scoped player identifiers to synchronize gameplay.

All users worldwide may request access to, correction of, or deletion of their Bloopers VR personal data free of charge. Email hello@spawnbridge.com. See Section 8 for instructions.

1. Who we are and what this policy covers

Rangesh U S, operating as Spawn Bridge (“we,” “us,” or “our”), develops and operates Bloopers VR. This policy describes information processed through the game and our support communications, its purposes and recipients, retention, and your privacy choices.

Processing includes accessing information through software development kits, using it in gameplay, saving it locally, and transmitting it over a network.

2. Information we process

2.1 Meta platform services

We initialize Meta Platform services and check whether your account has access to Bloopers VR. We use the entitlement result to permit or deny access. We do not request your Meta account User ID, username, or profile photo.

Meta processes purchases through the Meta Horizon Store. We do not receive your full payment-card or banking details.

2.2 Local game information

The game stores the following in local application storage on your headset:

• Your chosen in-game name, or a default name.
• Your selected character color.
• Your Solo best time.
• Your coin balance and reward receipts.
• An app-generated random identifier for the local profile.

The local identifier associates saved names, colors, and rewards with the local profile. It is not derived from your Meta account and is not included in synchronized multiplayer player data. Solo best times are stored for the app rather than separately for each profile.

We do not operate a developer-controlled cloud-save database. Clearing app data may remove the local identifier and saves. Platform backup features may retain or restore copies.

Updates from older versions: Older versions used locally cached account identifiers to organize saves. On update, the game may read the last-used cached identifier solely to migrate that profile’s name, color, and reward receipts to the local identifier, without requesting an account identifier from Meta.

Following successful migration, that profile’s legacy identifier cache, preference keys, and wallet files are removed. Other historical profiles are not merged and may remain in local storage; unsuccessful migrations retain data for recovery. These remaining files can be removed by clearing local application data. Legacy identifiers are not included in multiplayer player data by the current version.

2.3 Multiplayer and Normcore

Quick Match and private Host/Join rooms use Normcore. During online play, the following information is processed by the networking service and synchronized with participating game clients as applicable:

• Room-scoped client identifiers, chosen names, character colors, and player or spawn assignments.
• Character positions, rotations, movement states, and jump events.
• Room names or codes, match and round identifiers, timers, and game-generated bot or ghost identifiers.
• Checkpoint progress, finish or elimination status, and finish times.

The networking provider also processes technical connection information, including IP addresses, to operate its service. Other players see chosen names, character appearances and movements, and match outcomes.

The current version does not include Meta account IDs or persistent local save identifiers in multiplayer player data.

Solo Practice does not require joining a Normcore room. Meta entitlement checks are separate from multiplayer connections.

2.4 Movement and voice

Headset and controller movement is processed for gameplay and may be represented in synchronized character movement during multiplayer. Gameplay uses controllers rather than hand-tracking or eye-tracking features.

The current release does not provide voice chat or collect, record, transmit, or transcribe microphone audio for voice chat.

2.5 Connectivity checks

After a multiplayer connection failure, the game may contact Google and Cloudflare connectivity-check endpoints to determine whether internet access is available. These services receive your IP address and ordinary network request information.

The game does not add account identifiers, local save identifiers, chosen names, or reward records to these requests.

2.6 Support and privacy communications

If you contact us, we process your email address, message, and information you voluntarily provide to respond or verify a privacy request. Do not send passwords, payment-card details, or other sensitive credentials.

3. Why we use information

We process information to:

1. Verify your access to Bloopers VR.
2. Save local preferences, best times, and rewards.
3. Migrate existing saves when updating the game.
4. Provide online rooms and synchronized gameplay.
5. Determine and display match results.
6. Diagnose connection failures and validate chosen names.
7. Respond to support and privacy requests.
8. Comply with applicable legal obligations.

We do not sell personal data or use gameplay information or legacy account identifiers for targeted advertising or cross-app tracking.

4. Who receives information

Meta: Provides platform entitlement and store services. Information Meta processes independently is governed by Meta’s privacy policy.

Normcore: Provides multiplayer networking and processes the information described in Section 2.3. Participating game clients receive synchronized game state. Normcore’s published privacy policy describes its published practices, but states that it does not apply to end users of customers’ applications. This Bloopers VR policy describes our processing of player information.

Google and Cloudflare: Receive connectivity-check requests as described in Section 2.5. See Google’s privacy policy and Cloudflare’s privacy policy.

Email providers: Process correspondence so we can respond.

We may also disclose information when required by applicable law.

5. Storage and international processing

Local names, preferences, best times, identifiers, and rewards are stored on your headset. Multiplayer information passes through Normcore and participating game clients. Connectivity requests are processed by Google and Cloudflare; correspondence is processed in our email systems.

Local saves do not mean that all gameplay information remains exclusively on your headset.

We operate from India. These services may process information in other countries with different data protection rules. Users worldwide may contact us about their privacy rights.

6. Retention

Local game information: Local information can remain until the relevant application data is cleared or removed. Uninstalling alone may not remove copies retained or restored by platform backup features. See Section 2.2 for legacy save migration and removal.

Multiplayer and connectivity information: Networking and connectivity providers may retain connection records, service logs, or room information according to their service arrangements and applicable policies. We do not represent all such information as immediately erased on disconnect.

Support and privacy correspondence: We retain correspondence as needed to handle requests, maintain appropriate resolution records, or satisfy legal obligations.

We delete or de-identify information when it is no longer needed. We address applicable deletion requests without undue delay and coordinate deletion of personal data processed on our behalf with relevant providers.

7. Security

The game uses Meta entitlement checks, multiplayer room separation, and validation of chosen names. Persistent local save identifiers are excluded from multiplayer player data. No storage or transmission method is completely secure.

Report privacy or security concerns to hello@spawnbridge.com.

8. Your privacy choices and deletion

Access, correction, and deletion requests are available to all users worldwide, free of charge.

How to request deletion

1. Email hello@spawnbridge.com.
2. Use the subject Bloopers VR Data Deletion Request, or simply explain your request.
3. You may include your in-game name and a description of the information concerned. You do not need a Meta User ID to request deletion.
4. We may ask for limited information to verify the request. We will never ask for your Meta password.

What happens next

We will review and respond to your request, delete applicable personal data under our control without undue delay, and coordinate applicable deletion with providers processing it on our behalf. We will explain any legally required retention and confirm completed steps.

For headset-only information, we will explain how to remove the relevant local application data. We cannot remotely erase headset-only files.

What deletion affects

Removing local data can delete names, character settings, best times, coins, rewards, and legacy saves. It does not delete your Meta account, store purchases, or information independently controlled by providers. Using the game again may create new local and multiplayer information.

Other privacy choices

You may change your chosen name through game settings and use Solo Practice without joining a multiplayer room.

9. Children and age-appropriate use

Bloopers VR is intended for a teen and adult audience and is not directed to children under 13. Contact hello@spawnbridge.com if you believe a child has provided information contrary to the intended audience or applicable age requirements. We will review and address the request in accordance with applicable law and platform requirements.

10. Changes to this policy

We may update this policy when practices or features change. We will update the date when publishing a revision and provide additional notice where required by law.

11. Contact

Developer and data controller: Rangesh U S, operating as Spawn Bridge
Country: India
Privacy, correction, deletion, and security: hello@spawnbridge.com

Data deletion requests are available worldwide, free of charge. See Section 8.