Privacy Policy for Build and Breach

Sentari VR Systems ("we," "us," or "our") respects your privacy. This Privacy Policy explains how we collect, use, and handle information when you use our application, Build and Breach ("the App"), on Meta Quest devices, and our desktop companion application, Build and Breach Builder ("the Builder"), on your computer.

1. Data We Collect

We collect minimal data necessary to provide the core gameplay and training experience.

A. Meta Platform Data

The App requests the following Meta Platform permissions:

• User ID: Used locally for spatial anchor persistence. Spatial anchors allow your custom room layouts to remain anchored in your physical space across sessions. Your User ID is processed on-device and is not transmitted to our servers.
• User Profile: Used to identify the local user for spatial anchor ownership. Profile data is not stored, shared, or transmitted externally.

We do not use Meta Avatars, Invites, or any social features that transmit data to third parties.

B. Gameplay and Performance Data

The App generates performance metrics to facilitate After Action Reviews (AAR). This data is stored locally on your headset and includes:

• Timeline of events (e.g., start time, completion time).
• Score metrics (e.g., targets engaged, accuracy, time to clear).
• In-game decisions and interactions.

Training Record: The App keeps a history of your graded rounds (date, scenario, difficulty, room complexity, score, and the results above) so you can track your progress in the headset's RECORD screen. It is stored only on your headset.

Diagnostics Log: To help us find crashes and performance problems, the App keeps a rolling log of its last 12 sessions on your headset. It contains technical events only: the App version, headset model and operating system, frame rate, battery level and temperature, error messages, and gameplay events (for example, a round starting or ending, or a door being opened). It contains no audio, no camera images, no room maps, and no name, email, or account details, and it uses a random session identifier rather than any hardware identifier. The App never uploads it. It leaves your headset only if you connect the Builder (see Section 2) or copy it off yourself, for example when sending it to us for support.

This data does not leave your headset unless you connect to the Builder (see Section 2) or manually export or share it.

C. Spatial and Camera Data (Mixed Reality)

Build and Breach utilizes the Meta Quest Passthrough API and Scene API to provide a Mixed Reality experience. Regarding this data:

• Camera Images: The App accesses the camera feed solely to render the Mixed Reality environment in real-time. We do not capture, record, store, or transmit raw camera images.
• Spatial Anchors & Scene Data: The App uses spatial data (walls, furniture positions) to interact with your physical environment. This processing happens entirely on-device using the Meta XR Runtime. Spatial anchors are stored locally by the Meta Quest system to persist room layouts between sessions. We do not store a map of your physical space on any server.

D. Microphone Data

The App asks for microphone access for Voice Commands, which let you give verbal commands (such as "Hands up!" or "Get down!") to the people in a scenario. Speech recognition runs entirely on your headset, using an offline speech model built into the App: your voice is matched against a fixed list of commands, and only the recognized command is used. Audio is never recorded, saved, or transmitted, and no speech service, ours or anyone else's, is involved.

Voice Commands can be turned off at any time in the App's SETTINGS, and you can deny or revoke microphone access in the Quest settings; the rest of the App works without it. The intro tutorial turns Voice Commands on while you play it so it can teach them.

E. Purchases

Purchases of the App and of any add-on content are made through the Meta Quest Store. The App asks Meta's platform whether your account owns that content; Meta handles the purchase and payment details, and we never see them.

F. Connection Data

To find and stay connected to the Builder, the App stores a small amount of connection information locally on your headset: the address of the computer that last ran the Builder, and a name for it, stored locally. This is an address on your own network (like 192.168.1.50), it stays on your headset, and is never sent to us.

2. The Builder Desktop App

The Builder is a companion application that runs on your computer. It lets you author training rooms, run instructor-led sessions, and review replays.

The Builder contains no analytics, no telemetry, and no automatic update mechanism. It makes no connections to the internet; its only network activity is talking to headsets on your local network.

When the App and the Builder are connected:

• What is exchanged: room layouts you author, a device name for your headset (e.g., "Quest-02"), live session state (positions and events needed to display the session in the Builder), replay/AAR data for review, and the diagnostics events described in Section 1B.
• Where it goes: directly between your headset and your computer over your own local network. None of it passes through the internet or any Sentari server.
• Where it's stored: rooms you author, replays you save, and the list of headsets that have connected (each headset's identifier and its assigned name) are stored inside the Builder's application data on your computer. They are removed by following the deletion steps in Section 8.

How the devices find each other: the App discovers the Builder by sending a standard discovery query across your local network, and if needed it checks addresses on your local network directly. During discovery, devices on your network can see that a headset is looking for the Builder, and the Builder shows headsets that register with it. Discovery traffic never leaves your local network.

3. How We Use Data

We use the data described above strictly for:

• Core Functionality: Enabling gameplay, physics interactions, spatial anchor persistence, and generating your local performance score.
• Training Feedback: Displaying your engagement statistics and scenario results in the post-action review, on the headset and — when connected — in the Builder.
• Room Authoring and Instruction: Sending rooms you author in the Builder to the headset, and showing live session progress to the instructor running the Builder.
• Spatial Persistence: Saving and loading your custom room layouts so they remain in place across sessions using on-device spatial anchors.
• Reconnection: Remembering the Builder's last known address so later sessions connect without searching.

4. Data We Do NOT Collect

• We do not collect or process Meta Avatar data.
• We do not use Meta Invite or social features.
• We do not capture, store, or transmit camera images or video.
• We do not record, store, or transmit audio from your microphone. Voice Commands are recognized on the headset and the audio is discarded immediately.
• We do not use third-party analytics, advertising, or crash-reporting services in the App.
• We do not operate backend servers for the App or the Builder, and neither sends us any data — their connection is device-to-device on your own network.
• We do not share any data from the App or the Builder with third parties.

5. Data Storage and Security

Local Storage: All user-generated data (performance logs, your training record, the diagnostics log, spatial anchors, save files, settings, and connection settings) is stored locally on your headset's internal storage. Rooms, replays, and the connected-headset list are stored in the Builder's application data on your computer.

No Cloud Transmission: We do not operate a backend server that collects your personal usage data. All communication between the App and the Builder happens on your local network, creating a secure "offline-first" environment.

6. Third-Party Services

We do not share personal data from the App or the Builder with third parties. The App runs on the Meta Quest platform, which collects its own telemetry and usage data governed by the Meta Privacy Policy.

Our website is separate from the App and the Builder: if you use the contact form, the details you submit (such as your name, email address, and message) are stored with our website hosting provider so we can respond. The App and the Builder never send anything there.

7. Children's Privacy

Build and Breach is a tactical training simulator not intended for children under the age of 13. We do not knowingly collect personal information from children under 13.

8. Your Rights and Data Deletion

Since data is stored locally on your devices, you have full control over your information:

• Access: You can view your performance logs directly within the App's AAR interface and your training history on its RECORD screen, and your authored rooms and replays within the Builder.
• Deletion (headset): You can delete all App data by uninstalling the App from your Meta Quest library or clearing the App's storage via the Quest Settings menu. This removes all locally stored performance data, your training record, the diagnostics log, spatial anchors, settings, and remembered connection addresses.
• Deletion (computer): Uninstall the Builder, then delete its application data folder to remove your rooms, replays, and the connected-headset list: on macOS, "Build & Breach Builder" inside ~/Library/Application Support; on Windows, "Build & Breach Builder" inside %APPDATA%.
• Data Deletion Requests: You may also request deletion of any data associated with your account by contacting us at info@sentarivr.com.

9. Changes to This Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.

10. Contact Us

If you have any questions about this Privacy Policy, please contact us at:

Sentari VR Systems
Email: info@sentarivr.com