Privacy Policy
Effective and last updated October 23, 2026
This policy explains how VR Build Kit LLC (“we,” “us”) handles personal information when you use the vrbuildkit.com website, the VR Build Kit app for Meta Quest, and related services (together, the “Service”).
The short version: we collect what we need to run your projects, we do not sell your personal information or use it for targeted advertising, we do not run advertising trackers, we use website analytics only if you opt in, and you can ask us to delete your data at any time.
1. Who we are and what this covers
VR Build Kit LLC operates the Service and is responsible for the personal information described here. This policy applies to information collected through the website, the Quest app, meeting and guest features, email, and support conversations. It does not cover third-party websites or services we link to, or Meta's own handling of data on Quest devices, which is governed by Meta's privacy policy.
If you use the Service on behalf of a company, that company may have its own policies about the projects and files you upload.
2. Information we collect
Information you give us
- Account information: email address and password (stored as a secure hash by our authentication provider).
- Project content: floor plans, drawings, photos, 3D models, textures, documents, and other files you upload; photos and videos you capture in the Quest app; project names, spaces, variations, layouts, saved scene states, and exports.
- AI conversations: prompts, messages, attachments, and references you send to the generation assistant, plus the briefs, plans, and assets it creates.
- Payment information: plan, subscription status, generation-funds balance, automatic-reload settings, invoices and receipts, billing name, receipt email and address, a tax ID if you add one, and your reason for cancelling if you choose to give one. Card details are entered into secure Stripe card fields on our checkout and Billing pages and are collected and stored by Stripe, not by us. We never receive your full card number or security code; we receive the card brand, last four digits, and expiration date so we can show which card is on file.
- Feedback and support: bug reports, feature requests, contact-form messages (name, email, optional company, and message), and emails you send us.
- Reports: if you report someone or something from the Quest app, what you chose and wrote, and where it happened (the meeting, project, or library model). If someone reports you, we see that report and may look at the meeting or content it names.
Information collected automatically
- Device and log data: IP address, browser and operating system, pages and API endpoints requested, timestamps, and error details, recorded by our hosting and file-delivery providers and our servers.
- Headset session data: identifiers for paired headsets, QR pairing and session tokens, app version, and headset preferences.
- 3D performance diagnostics: file structure measurements such as triangle, primitive, material, texture, and node counts; model file names and hashes; headset model and app version; load timing, memory samples, and whether a model loaded, remained editable, or failed. We do not upload passthrough images or tracking coordinates with these diagnostics.
- Usage and cost records: generation jobs, AI provider usage and cost, storage used, and feature activity needed for billing, spending limits, abuse prevention, and troubleshooting, and to measure how features are used (for example, which example projects an account opens, on which device, and whether it later upgrades).
- Browser storage: sign-in tokens and settings stored in cookies or local storage. See Cookies.
Information from others
- Stripe tells us whether a payment succeeded and provides invoice, subscription, and saved-card details (brand, last four digits, and expiration date).
- People you work with may share a project or meeting invitation with you, or add content to a shared session.
We do not intentionally collect sensitive personal information such as government identification numbers, precise GPS location, health information, or biometric identifiers. Please do not upload files containing that kind of information.
3. Headset, voice, and spatial data
Mixed-reality features need information about your surroundings and movements. Here is how we handle it:
- Room and scene understanding. The Quest app uses Meta's scene and spatial anchor features to place projects in your space at real-world scale. Room scans and passthrough camera images are processed by Meta's system on the device; our app does not receive or upload them, except in photos and videos you choose to capture (below).
- Hand and head tracking. Tracking is used on the device to let you interact with projects. During a shared meeting, your head and hand positions may be sent in real time to other participants so they can see where you are pointing. We do not store this movement data after the session.
- Shared anchors and colocated meetings. When you host or join a meeting in the same physical room, the app shares spatial anchor information through Meta's platform so headsets can align. Meeting snapshots of the project scene are stored so guests can load them, and the host's edits, drawings, and comments are sent live to everyone in the meeting.
- Finding a meeting. A hosting headset announces the meeting's invitation to devices on the same Wi-Fi network. Headsets on the same internet connection can also find a meeting through our website when the host requires approval; to match them we keep a keyed fingerprint of the host network's public IP address, not the address itself. Guest approval is on by default: a guest joins only after the host allows them. If the host turns approval off, any headset on the same Wi-Fi can join.
- Voice features. While voice listening is on, audio from your microphone is streamed from the headset to OpenAI for real-time transcription. On Pro and Enterprise accounts listening starts when a project opens, unless you turn that off in Headset Settings; it stops after 15 minutes without a voice command, and you can stop it any time from the Voice menu. We do not store the audio from voice controls. Transcript text may be saved with the project and summarized. Raw transcript text is automatically deleted after 30 days, and the summary and action items stay with the project until you delete them.
- Photos and videos you capture. When you take a photo or record a video in the Quest app, by voice or from the menu, Meta's system asks for your permission once each time the app is opened. The capture shows your headset view, including the passthrough view of your surroundings and anyone in them, and a video also records audio from your microphone. Captures upload to the project they were taken in, where anyone with access to that project can view and download them from the dashboard, and they are kept until you delete them or the project. The app also keeps its own copy on the headset until the app is uninstalled or its storage is cleared.
- Sun at a named place. If you ask for the sun at a place (for example, “sun in Denver”), the headset looks the place up with Komoot's Photon service and its time zone with TimeAPI. They receive the place name or its coordinates and your headset's IP address. The place you choose is saved with the project's lighting.
- Model performance. When an authenticated headset opens a 3D model, the app sends technical load and memory diagnostics tied to that model's file name, file hash, and project. We use these records to warn you about models that may load slowly, lose editing features, drop frames, or exceed headset memory, and to improve those estimates over time.
4. How we use information
- Provide the Service: store projects, convert files, generate rooms, models, and materials, sync projects to your headset, and run meetings.
- Process payments, manage subscriptions and generation funds, apply spending limits, and send the receipts and billing emails described in the Billing Terms. Billing emails go through our email provider, Resend, and may include your plan, amounts, invoice or receipt numbers, and your card's brand and last four digits.
- Send service messages such as account confirmations, password resets, security alerts, and project notifications.
- Respond to support requests and feedback, and let you know when an issue you reported is fixed.
- Troubleshoot, secure, and improve the Service, including reviewing failed or low-quality generation jobs to fix our workflows.
- Estimate whether an uploaded 3D model is suitable for the headset and refine those estimates using de-identified, aggregated device outcomes.
- Prevent fraud and abuse, enforce our Terms, and comply with legal obligations.
We do not sell personal information, share it for cross-context behavioral advertising, or use your project files to train general-purpose AI models. If we want to use personal information for a new purpose that is not compatible with these purposes, we will ask for your consent first.
Where laws such as the EU or UK GDPR apply, we rely on these legal bases: performing our contract with you; our legitimate interests in securing and improving the Service; compliance with legal obligations; and your consent, for example for optional voice features and analytics cookies, which you can withdraw at any time.
5. AI processing
Many features use AI models provided by OpenAI through its API, including the generation assistant, floor-plan interpretation, room and object generation planning, material generation, voice transcription, and transcript and feedback summaries. To provide those features, we send the relevant prompts, files, images, and audio to OpenAI.
- We configure these requests so OpenAI does not store them for later retrieval, where OpenAI supports that option.
- Under OpenAI's API terms, API data is not used to train OpenAI's models by default. OpenAI may keep request data for a limited period, generally up to 30 days, to detect abuse.
- AI output is generated automatically and can be inaccurate. It is not a decision about you that has legal or similarly significant effects.
Some generation and conversion jobs also run on computers we operate, such as 3D processing workers. Those systems only use your files to complete your jobs.
Artist Network. If you choose to request help from a human artist, we share an AI-assisted summary of your project and the files needed for the work with an artist bound by confidentiality obligations. We only do this when you ask for it.
7. Service providers
These providers process personal information for us. We may update this list as the Service changes.
| Provider | Purpose | Information involved |
|---|---|---|
| Supabase | Accounts and sign-in, database, server functions, and file storage | Account details, project data, uploaded and generated files |
| Vercel | Website hosting and server functions | IP address, request logs, data passing through our API |
| Cloudflare | File storage and delivery | Uploaded and generated files, headset photos and videos, Model Library files, IP address and request logs |
| Stripe | Payments, subscriptions, invoices, and fraud prevention | Billing name, email, address, tax ID if added, payment method (held by Stripe), purchase history |
| OpenAI | AI generation, conversation assistant, voice transcription, and summaries | Prompts, attachments, floor plans, voice audio while voice features are active, transcripts |
| LiveKit | Real-time meeting presence | Session identifiers, live head and hand positions, and the host's live edits, drawings, and comments during a meeting |
| Resend | Transactional and billing email (receipts and billing notices) and contact-form notifications | Email address, name, message content, and in billing emails your plan, amounts, invoice or receipt numbers, and card brand and last four digits |
| Komoot (Photon) | Finding a place you name for the geographic sun in the Quest app | The place name you say or type, and your headset's IP address |
| TimeAPI | Finding that place's time zone for the geographic sun | The place's latitude and longitude, and your headset's IP address |
| Website analytics through Google Analytics, only if you accept analytics cookies | Pages visited (with identifiers removed from addresses), referring site, device and browser type, approximate location, and a random cookie ID | |
| Meta | Quest platform services such as app distribution, spatial anchors, and colocation | Headset and platform identifiers and shared anchor data, under Meta's own terms and privacy policy |
9. How long we keep information
| Information | How long |
|---|---|
| Account, projects, uploads, generated assets, and exports | Until you delete them or your account, then removed from active systems within 30 days and from backups on their normal cycle |
| Raw voice transcript text | Automatically deleted after 30 days; summaries stay with the project |
| Headset photos and videos | Until you delete them or their project, then removed as above; the copy on the headset stays until the app is uninstalled or its storage is cleared |
| Meeting snapshots | Deleted automatically one to two days after the meeting ends |
| Meeting records (start and end times, meeting time used, and fingerprints of the headsets and network involved) | As long as needed for billing, meeting limits, and security |
| Audio from voice controls | Not stored by us |
| Headset sessions and QR pairing tokens | Until they expire or are revoked, plus a short security log period |
| 3D performance profiles and headset diagnostics | While the related project or model remains in your account; de-identified aggregate benchmarks may be kept to improve capacity estimates |
| Billing, invoices, and payment records | As long as required for tax, accounting, and legal purposes, generally up to 7 years |
| AI usage and cost records | As long as needed for billing reconciliation, disputes, and spending controls |
| Support messages and feedback | As long as needed to resolve the request and improve the Service, then deleted or de-identified |
| Reports about people or content | As long as needed to review and act on them and keep the Service safe; if the reporter's account is deleted, the report is kept without who sent it |
| Server logs | According to our hosting and file-delivery providers' standard log retention |
| Google Analytics data (only if you opt in) | Cookies up to 2 years; event data kept 14 months |
10. Your privacy rights
Depending on where you live, you may have the right to:
- Know what personal information we have about you and get a copy in a portable format.
- Correct inaccurate information.
- Delete your personal information.
- Opt out of the sale or sharing of personal information, targeted advertising, and certain profiling. We do not do these things.
- Limit the use of sensitive personal information. We do not use it beyond what the Service requires.
- Withdraw consent you previously gave, such as for voice features.
- Appeal our decision on your request, and complain to your state attorney general or local data protection authority.
We apply these rights to all users, not only residents of states or countries that require them. To make a request, email support@vrbuildkit.com or use the contact form and choose “Privacy / data request.” We will confirm receipt, verify your identity by confirming control of your account email, and respond within 45 days (or sooner where required). An authorized agent may submit a request with proof of authorization. We will not discriminate against you for exercising your rights.
Nevada residents. We do not sell covered information as defined in Nevada Revised Statutes 603A. You may still submit a verified request directing us not to sell your covered information by emailing support@vrbuildkit.com with the subject “Nevada opt-out request.” We will respond within 60 days. You may also review and request changes to the personal information in your account by contacting us.
California residents. The rights above include those under the California Consumer Privacy Act where it applies to us. California's “Shine the Light” law lets you ask whether we disclosed personal information to third parties for their direct marketing. We do not.
To appeal a decision, reply to our response with the subject “Privacy appeal.” We will respond within the time required by applicable law.
11. Deleting your account and data
You can delete individual projects, assets, and exports from your dashboard at any time. To delete your entire account:
- Email support@vrbuildkit.com from your account email with the subject “Delete my account,” or submit the contact form. You don't need to sign in, and there is no fee.
- We will confirm the request, cancel any subscription and automatic reload, then delete your account, projects, uploaded and generated files, headset photos and videos, transcripts, headset sessions, and meeting snapshots within 30 days.
We keep only what we must: billing and tax records, records of the request itself, and information needed to prevent fraud, resolve disputes, or comply with the law. Content already shared with others, such as an export a collaborator downloaded, cannot be recalled. Signing out of the Quest app or uninstalling it does not delete your account.
12. Security
We use encryption in transit (HTTPS), database access controls that restrict project data to authorized accounts, short-lived signed links for file access, scoped and revocable headset sessions, and limited administrative access. No system is perfectly secure. If we learn of a security incident affecting your personal information, we will notify you and regulators as required by law.
To report a security vulnerability, email support@vrbuildkit.com or use the contact form and choose “Security vulnerability.” Our security.txt lists the same contacts. We review every report and fix confirmed issues promptly.
13. Children
The Service is intended for adults and is not directed to children. You must be at least 18 to create an account. We do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, contact us and we will delete it.
14. International users
We are based in Nevada, United States, and our service providers may process information in the United States and other countries. Those countries may have different data protection laws than where you live. Where required, we rely on appropriate safeguards such as standard contractual clauses offered by our providers.
15. Changes to this policy
We will update this policy when our practices change. The date at the top shows when it last changed. If we make a material change, we will notify you by email or in the Service before it takes effect.
16. Contact us
Email support@vrbuildkit.com or use our contact form.
