1. About this policy
Blimp Battle is a mixed reality game provided by Asilomar Design Inc. This policy describes Bot Battle and Target Practice, the private Friends Lobby beta introduced in version 1.01, and this website.
Solo modes remain available without joining an online room. The private Friends Lobby beta supports up to four players using a room code, with optional microphone access for voice chat. The game does not have player accounts, advertising, or a gameplay analytics SDK.
2. Information used during gameplay
The game uses headset position and orientation, controller input, tracking status, and a room-floor reference to support movement, aiming, menus, and arena placement. Solo modes process these inputs on your device. After you enter a room code and select Join in Friends Lobby, the game sends arena-relative movement and gameplay input to our server to coordinate the match and share game state with the other players in that room.
Mixed reality passthrough is supplied by the Meta Quest runtime. The game does not request access to raw room-camera images, and it does not automatically upload gameplay recordings.
Voice in private rooms. When you join a coded room and allow microphone access, your voice is relayed through our game server to the other players in your room, including in lobby and course menus. Voice uses encrypted connections to the server; it is not end-to-end encrypted. The game relays audio in memory and does not record or persist it. Other participants can hear what you share, and we cannot prevent them from making their own recordings.
You can join and play without allowing microphone access. Muting disables outgoing voice audio. Leaving the room or ending the mixed reality session stops microphone capture and closes the voice connection.
3. Saves stored on your device
The game stores settings, tutorial completion, course progress, awards, and personal best times locally in browser storage associated with the game website. It also caches game files to support loading and offline use.
These saves are not uploaded by the game to a player account or cloud-save service. They remain on your device until the relevant website data is removed or replaced. Different website addresses may have separate saves.
4. Hosting and service providers
Game delivery. Railway hosts the game content and private room server. When your device requests game files or connects to a private room, the hosting service processes technical request information, which can include your IP address, browser information, requested address, timestamps, and diagnostic information, to deliver, secure, and operate the service.
This website. This policy website is hosted through OpenAI Sites on Cloudflare infrastructure. These services process technical connection and request information to deliver and protect the page. We have not added advertising, analytics scripts, contact forms, or account registration to this website.
Email. Our support address uses Squarespace email forwarding, with Mailgun delivery and Google Gmail for receiving and responding to messages. These providers process correspondence to deliver and operate the email service.
Meta services. Meta operates the headset, browser runtime, account, and store under its own privacy policy. This policy describes our game and website; it does not replace Meta’s policy.
5. Support messages and retention
If you email us, we receive your email address, the contents of your message, and any attachments you choose to send. We use this information to respond to your request and address the issue you report. Please do not send passwords or unrelated sensitive information.
We retain support correspondence for as long as reasonably needed to respond to your request, handle related follow-up, and meet applicable legal obligations. Retention depends on the request; we do not use a fixed automatic deletion schedule. You may request deletion by emailing contact@blimpbattle.com. Personal information relating to a child is kept only as long as needed for the purpose for which it was collected.
Technical hosting logs are maintained by our hosting providers under their service retention settings and policies. Retention can vary by provider and service plan. We use this information for delivery, security, and troubleshooting, not to create player profiles. The game does not upload local progress or raw gameplay tracking inputs to those logs. Private rooms use temporary player and seat identifiers and voice membership tokens in server memory. Server diagnostics can include room join and leave events, seat, course, match phase, and connection close codes and reasons. The game also stores the most recent connection failure on your device to help with troubleshooting. Voice audio is not written to these logs.
We do not sell personal information or use support messages or game data for targeted advertising. Information may be handled by the service providers described above to operate the game, website, and support service, or disclosed when legally required.
6. Children and families
Blimp Battle is intended for a mixed-age audience. The game does not ask players for their name, date of birth, email address, or a player profile. Solo modes do not include communication with other players. The private Friends Lobby beta allows voice communication with others who join using the same room code. Parents and guardians should consider who has the code and help children decide whether to join or allow microphone access. Avoid sharing names, contact details, or other personal information in voice chat.
Parents and guardians may contact us about information relating to their child, including requests to review or delete information we hold. Please contact support on your child’s behalf and include only the information needed to explain the request. Technical information processed to deliver the game is described above.
7. Your choices and deletion requests
Information held by us. Email contact@blimpbattle.com to ask about, correct, or request deletion of personal information held by us, including support correspondence. We may request the limited information needed to verify and locate your request. Depending on where you live, you may have additional privacy rights.
Local game data. Saves and cached files are held on your device, so we cannot erase them remotely. Use the applicable browser or device website-data controls for the game address quest-release-production.up.railway.app, or contact us for help finding those controls. Clearing that website’s data removes the associated local progress and settings. Uninstalling the game alone may leave browser-based website data behind.
Microphone and room sharing. Use the in-game mute control to stop outgoing voice audio, leave the room to stop sharing room gameplay and voice, or manage microphone permission in the headset or browser permission controls.
Meta account data. Requests about information held by Meta should be directed to Meta through its account and privacy controls.
8. Contact and policy updates
We will update this page when our practices change and revise the effective date. If an update requires additional notice or consent, we will provide it as required.