Sentari VR Systems ("we," "us," or "our") respects your privacy. This Privacy Policy explains how we collect, use, and handle information when you use Sentari Build ("the App") on Meta Quest headsets and the Sentari Build desktop app on your computer and the Sentari Build iPad app (together "the Desktop App"; what this policy says about the Desktop App and "your computer" applies to the iPad app and your iPad too). Sentari Build is used by home builders and their clients to design accessory dwelling units (ADUs) and view them at full size.
Summary: Your designs stay on your own devices unless you choose to use one of the Desktop App's optional cloud features: reading a plan image with AI, or sharing a proposal with your client by link (Section 2A). Your Sentari account also holds your company's license, its price book, and monthly counts of how much your company uses the Desktop App (numbers only, nothing about a plan or a homeowner). The App and the Desktop App otherwise talk to each other directly over your local network. The App does not access camera images, record audio, or send room maps to us. (When two headsets walk a house together, Meta's shared spatial anchor service handles the room data needed to line them up; see Section 1B.) The only other thing that can leave your devices is an optional crash report.
1. Data the App Handles on the Headset
A. Your Designs
Projects you create or open (walls, rooms, doors, windows, finishes, furniture, roof, measurements, and the project name) are stored on the headset's internal storage: the project you have open, the projects you save, and, if a builder sets one, a "demo start" project used to reset the App between client visits. They are never sent to us. Project names are whatever you type; we recommend not using a client's full name or address.
B. Mixed Reality, Spatial Anchors, and Camera
- Camera images: the Quest system shows your surroundings (passthrough) behind the App. The App does not access, capture, store, or transmit camera images or video.
- Spatial anchors: to keep a house pinned in the same place in your yard or room across sessions, the App uses Meta's spatial anchor feature. The anchor is created and stored on the headset by the Meta Quest system; the App stores only the anchor's random identifier next to the project. No map of your space is sent to us.
- Boundary: the App asks the system to hide the Meta boundary while you are in mixed reality, so the house isn't drawn behind it. In client view it does so only when a safe area has been outlined and outdoor safety is on; otherwise the headset's own boundary stays. The outline is kept on the headset. Use the App in a clear area; a builder's representative should outline and supervise the area during client visits.
- Walking a house together (v1.0.1 and later): only when one headset chooses Invite a headset and another chooses Join a headset:
- The inviting headset creates a spatial anchor where its wearer stands and shares it through Meta's shared spatial anchor service, so the joining headset can find the same spot. Sharing an anchor sends data describing the shape of the space around it (a point cloud, not camera images) to Meta, where it is handled under Meta's Privacy Policy; the headset's "Enhanced spatial services" setting must be on. None of it is sent to us. The App erases the anchor when the inviting headset stops.
- To be found, the inviting headset announces the session to headsets nearby using Meta's colocation discovery (Bluetooth and Wi-Fi). The announcement contains the headset's model name (for example, "Quest 3"), the open project's name, and the headset's address on your local network, and can be seen by nearby headsets running apps that look for such sessions. It stops when the inviting headset stops.
- The design, which doors are open, where the house stands, and each wearer's head and hand positions then go directly between the headsets over your local network, so each can show the others. None of it passes through the internet or any Sentari server, and none of it is stored beyond the project itself.
- Scene data (garage scan): when you choose to scan a garage into walls, the App reads the room model from your headset's Space Setup (its walls, doors and windows as shapes and sizes, not camera images) and turns it into editable walls in your project. The room model is read on the headset only; it is not sent to us or to anyone else.
C. Settings and Identifiers
The App stores its settings on the headset (for example, which hand holds the menu, wall opacity, whether the walkthrough has been seen, and whether crash reports are on). It creates a random installation ID used only to group crash reports (Section 3). It does not use your Meta account, profile, avatar, or friends, and asks for no microphone, hand-tracking, or location permission.
D. Text You Type
When you name a project in the headset, the Quest system keyboard is used. What you type becomes the project name described in Section 1A.
2. The Desktop App and the Local Link
The Desktop App lets you design on a computer, send a design to a headset, receive one from it, and export blueprint PDFs.
- What is exchanged: project data you choose to send (by Send, Get, or Live sync), the headset's position on the plan while connected (so the computer can show where the wearer is standing), basic status (mixed reality or VR, the active tool, frame rate, App version), the headset's model name (for example, "Quest 3"), and a device identifier used to remember a paired headset.
- Where it goes: directly between your headset and your computer over your own network. None of it passes through the internet or any Sentari server.
- Pairing: a headset connects only after someone approves its 4-digit code on the computer. The computer keeps a list of paired headsets (identifier, model name, the date paired, and a hashed security token) in the Desktop App's application data.
- Discovery: the headset finds the computer with a standard local-network discovery query and, if needed, by checking addresses on your local network. Devices on your network can see this discovery traffic; it never leaves your network.
- Files: projects you save and blueprint PDFs are stored where you choose on your computer (blueprints requested from the headset go to the Documents/Sentari Build folder).
2A. Cloud Features in the Desktop App
The Desktop App uses the internet to check your company's license (v1.2.0 and later), to keep your company's price book on its account (v1.4.0 and later), to add to your company's monthly usage counts (v1.4.0 and later), and for two optional features, AI plan import and client share links. Your designs are not uploaded unless you use one of the optional features.
- Sentari account: editing plans, AI plan import and share links need you to sign in with your email address and a password. We store your email address, a user ID and a protected (hashed) form of your password with Google Firebase, the service we use for accounts; we never see the password itself.
- License: Sentari Build is licensed to a company. We store the company's name, the email addresses of the people its owner adds, and its license (trial, subscription or pilot, the number of kits, and the date it is paid through). The Desktop App keeps a signed copy of the license on your computer so it works offline for up to 14 days. Subscriptions are paid through Stripe, which handles your payment details; we never see your card. Checking the license sends no design data. When a pilot is about to end, we email the account owner 14, 7 and 1 days before.
- Company price book (v1.4.0 and later): the price book your company sets up (your rates, option prices, and rent and loan defaults) is stored on your company's account with Google Firebase, so every computer and iPad signed in to your company prices with the same book. Your company's signed-in people can read and change it; we record who saved it last and when. We can access it to support you. It holds your prices, not your plans or your clients.
- Usage counts (v1.4.0 and later): the Desktop App adds to six monthly numbers on your company's account: plans started, proposals exported, share links made, days a headset connected, client views, and sales demos run. They are numbers only: nothing about a plan, a price or a homeowner, and nothing per person. We use them to support customers and to measure how a pilot is going, and review them with you in pilot check-ins. Counts made offline wait on the device and are added when it is next online.
- AI plan import: when you choose to read a plan image, the image is sent to our server and on to Anthropic's Claude model, which reads its walls, doors, windows and room names; the result comes back to your computer. We keep a record of your import credits and each read (date, credits used), not the image. Credit packs are paid through Stripe, which handles your payment details; we never see your card.
- Client share links: when you make a share link, a copy of the project is stored with Google Firebase so the person you send the link to can open it in a web browser at sentarivr.com/r/…. The copy includes the design, your price book and the client's selections, your company details as entered, and the client's name and address; it does not include the client's email, phone or notes, or the plan image under the drawing. Anyone who has the link can open it, so send it only to your client. When your client sends their picks from that page, we store the name and note they type, their picks and the total, and email them to you. You can also make a 6-character headset code for a share link; a Quest with the App that types the code downloads that same copy of the project and keeps it on the headset. A code stops working after 7 days, when you make a new one, or when you stop sharing. The link and its replies stay until you choose stop sharing, which deletes the link, its replies and its codes.
3. Crash Reports
To find and fix problems, the App and the Desktop App can send a crash report to Sentry, an error-monitoring service operated by Functional Software, Inc. A report is sent when the app hits an unexpected error, or when the App starts and the previous session ended unexpectedly. A report contains:
- the error message and the program locations involved (stack trace);
- the app version, the device model and operating system version;
- the App's mode (mixed reality or VR) and active tool, and the App's last 30 log lines (technical messages such as a project being rebuilt or a connection opening);
- the random installation ID from Section 1C.
Reports do not contain your designs, project names, file names, camera images, room maps, or any name, email, or account details. Like any internet service, Sentry receives the sending device's IP address. Reports are kept for up to 90 days and are used only to fix bugs.
Turning it off: in the App, Settings ▸ Crash reports ▸ Don't send. In the Desktop App, Help ▸ Send Crash Reports. Crash reporting is only active in builds we have configured for it; a build without it sends nothing.
4. How We Use Data
- Core functionality: designing, displaying, and saving your projects, and keeping a house anchored in place.
- The local link: moving projects between your headset and computer and showing the wearer's position on the computer.
- Walking together: lining up two or more headsets on the same spot and showing each wearer the same house, doors, and the other wearers.
- Cloud features you choose: signing you in, reading plan images you send for AI import, and hosting share links and passing your client's picks to you (Section 2A).
- Your company's account: checking the license, keeping the price book the same on every device, reminding the owner before a pilot ends, and the monthly usage counts we use for support and pilot check-ins (Section 2A).
- Client visits: resetting the App to a builder's demo project and showing a short walkthrough to first-time wearers.
- Reliability: crash reports, as described in Section 3.
5. Data We Do NOT Collect
- We do not capture, store, or transmit camera images, video, or audio.
- We do not send room scans, maps of your space, or spatial anchors to our servers.
- We do not use advertising, tracking, or third-party analytics services. The only usage information is the six monthly counts per company in Section 2A.
- The App (headset) has no accounts and uploads no designs; it downloads one only when you type a headset code. The Desktop App uploads a design only when you use AI plan import or make a share link (Section 2A).
- We do not sell your data. We share it only with the service providers named in Section 6, for the purposes described there.
6. Third-Party Services
Sentry (Functional Software, Inc.) processes crash reports under the Sentry Privacy Policy, as described in Section 3.
Google Firebase (Google LLC) hosts Sentari accounts, company licenses, price books and usage counts, share links and client replies, and sends the emails, under the Firebase privacy terms.
Anthropic reads plan images sent for AI import, under its commercial terms, which do not allow it to train on them. Stripe processes payments for subscriptions and import credits under the Stripe Privacy Policy.
The App runs on the Meta Quest platform, which collects its own telemetry and usage data and stores and shares spatial anchors under the Meta Privacy Policy.
Business customers: if your company licenses Sentari Build from us, the contact and billing details you give us are used to provide the service and support under your agreement and the Sentari Build terms, and are not collected through the App.
7. Children's Privacy
Sentari Build is a professional design and sales tool and is not directed to children under 13. We do not knowingly collect personal information from children under 13. Meta's age requirements for Quest headsets also apply.
8. Your Rights and Data Deletion
- On the headset: delete a saved project from the App (Open… ▸ Delete), or remove all App data by uninstalling Sentari Build or clearing its storage in the Quest settings. This removes your projects, the demo start, settings, the installation ID, and the App's anchor identifiers.
- On your computer: delete project and PDF files you saved; uninstall the Desktop App and delete its application data folder ("Sentari RoomCraft", its name before the rename, inside ~/Library/Application Support on macOS, or %APPDATA% on Windows) to remove the paired-headset list and settings.
- Share links: in the Desktop App, Client ▸ stop sharing deletes the shared copy and your client's replies at once. To delete your Sentari account and its import history, or your company's price book and usage counts, email us.
- Crash reports: to ask us to delete crash reports from your devices, email us with the date and the device; reports are deleted automatically after 90 days.
- Requests: you can contact us about any data we hold at support@sentarivr.com. California residents may have additional rights under California law, including the right to know about and delete personal information.
9. Changes to This Policy
We will update this policy before Sentari Build starts using data in a new way (for example, a new cloud feature), and post the new version on this page with a new "Last Updated" date.
10. Contact Us
If you have any questions about this Privacy Policy, please contact us at:
Sentari VR Systems
Email: support@sentarivr.com