Privacy policy
VibeAR is a workspace that shows the terminals, browsers, files and screen of your own computer as windows in your room. Most of what you do never leaves your network. This page says exactly what does, who receives it, how long it is kept and how to delete it.
The short version
- Your terminals, files, screen and browsing stay on your local network, between the headset and your computer. We never see them.
- You sign in once, in the desktop app or on vibear.dev. The headset never asks for a password: it is linked to your account through the computer it is paired with.
- Voice is off by default. You choose Local voice (processed entirely on your computer) or Cloud voice, which uses Google Gemini for both speech-to-text and the voice assistant.
- AI-generated room backgrounds (skyboxes) use OpenAI, and receive only the description you type.
- Neither provider trains its models on your data. They keep it for at most 55 days (Google) or 30 days (OpenAI) for abuse monitoring, then delete it.
- We meter paid AI features (how many tokens a request used and what it cost), never what you said. There is no advertising, tracking or behavioural analytics in any of our software.
- You can delete your account and data from the headset, the desktop app, vibear.dev or by email. How to delete your data.
- We never sell data.
Who we are
VibeAR is published by Xavier Jara, an individual based in Paris, France, who is the data controller for the processing described here. Contact: support@vibear.dev. Full publisher details are in the legal notice.
What stays on your network
The headset app and the desktop app talk to each other directly over your Wi-Fi. Everything you do in a window (commands and their output, files, web pages, the mirrored screen, notes, the contents of SSH sessions) travels only between those two devices and is stored, if at all, on your own computer. Our servers are not part of that traffic and cannot read it. The one exception is Cloud voice, described below, and only for the request you speak.
Coding assistants you run in a terminal (for example Claude Code or Codex) run on your computer under your own account with their providers. VibeAR does not send them anything and does not receive what you send them; their own privacy terms apply.
AI and voice
Local voice
Speech-to-text and the voice assistant run on your own computer, using open-source models downloaded once onto it. Your audio and your requests do not leave your network, and no third party receives them.
Cloud voice (Google Gemini)
If you choose Cloud voice, your requests are processed by Google Gemini, provided by Google LLC through the paid Gemini API. Gemini does two jobs: it turns your speech into text, and it works out what you asked for and answers. When you hold the microphone and speak, the following is sent to Google through our server:
- the audio of that request only (the microphone is off the rest of the time, and nothing is sent until you speak to the assistant);
- the text of the request;
- the names and layout of your open windows, so it can act on them;
- when you ask about what is on screen (for example "explain this error"), the visible text of the window you are asking about;
- for spoken replies and read-aloud terminal questions, the text to be spoken.
Nothing that identifies you (your name, email or account) is sent to Google; the requests are made under our API account, not yours.
Training. Under Google's terms for paid Gemini API services, Google does not use these prompts or responses to train or improve its models.
Retention. Google keeps prompts and responses for up to 55 days, solely to detect abuse and meet legal obligations, and then deletes them. We do not store your audio, transcripts, prompts or replies at all. What we do keep is a usage record of each request: the model used, the number of tokens, the cost and the time. That record holds no content and is how we enforce the monthly quota that comes with your plan.
AI skyboxes (OpenAI)
If you generate an AI background for a workspace, the description you type is sent to OpenAI (OpenAI, L.L.C.), whose image model paints the picture. Nothing else is sent and nothing identifies you. Under OpenAI's API terms this data is not used to train its models, and OpenAI keeps it for up to 30 days for abuse monitoring before deleting it. We keep a weekly count of the images you generated, to apply your plan's allowance.
What else we collect
| Data | When | Why | Kept for |
|---|---|---|---|
| Email address | When you create an account | To run your account, send receipts and answer support | Until you delete the account |
| Sign-in methods: password (stored only as a salted hash), passkeys, and the Google or Apple account identifier if you sign in with them | When you add one | To let you sign in | Until you remove it or delete the account |
| Purchases, plan and subscription status | If you buy | To unlock what you paid for | Until you delete the account; invoices as the law requires (below) |
| Headset licence: a one-way hash of the headset's identifier and its model name | When a plan is activated on a headset | To tie the licence to your headset (two per account) and prevent copying | Until you free the seat or delete the account |
| AI usage records: tokens, cost, model, time. Never content | When you use Cloud voice or AI skyboxes | To apply your plan's quotas and reconcile our provider bills | With the account; on deletion they are stripped of anything that links them to you |
| Coding-assistant usage: token counts reported by your computer | When the plan meters the coding assistant | To apply your plan's quota | Until you delete the account |
| Local network addresses of your computer | Only if your headset and computer are on different networks | So the headset can find your computer when local discovery fails | In memory only, about 90 seconds after the computer stops reporting |
| Waitlist email | If you join a waitlist | To tell you once when the product or platform is available | Until it is sent or you unsubscribe |
| Server logs: IP address, time, request path, error codes | Any request to vibear.dev | Security, abuse prevention and debugging | Up to 30 days |
Neither app collects advertising identifiers, crash reports, device diagnostics or behavioural analytics. The desktop app keeps its own log file on your computer; it is never uploaded.
Microphone, camera and room data
The microphone is muted by default and shows an indicator while it is on. With Local voice your audio stays on your computer; with Cloud voice it goes to Google as described above. We never store recordings.
The optional "keep keyboard visible" setting finds your physical keyboard so it stays visible through the dimmed view. It uses Meta's keyboard tracking on the headset, or, as a fallback, low-rate passthrough camera frames sent to your own computer on your network. Frames are not stored and never reach our servers or any third party. The headset's room understanding (spatial anchors), used to keep windows where you left them, never leaves the headset.
Collaboration rooms
When you share a window with another person, the content is end-to-end encrypted between the two computers. Our relay passes the encrypted bytes along and cannot decrypt them. It keeps only metadata about the room (when it opened and closed, how many people joined, how many bytes passed).
Every service that processes your data
| Service | What for | What it receives | Where |
|---|---|---|---|
| Google LLC (Gemini API) | Cloud voice: speech-to-text, the voice assistant, spoken replies | The request's audio, text, window names and on-screen text you ask about | United States |
| OpenAI, L.L.C. | AI skyboxes | The description you type | United States |
| Cloudflare, Inc. | Hosting of vibear.dev, our server, its database, the collaboration relay and the discovery service | Everything our server stores (above), plus request logs | Global network; data may be stored in the EU or the United States |
| Stripe (Stripe Payments Europe, Ltd., Ireland, and Stripe, Inc.) | Payments, invoices, subscription management | Email, payment details (we never see your card number), billing address, purchase | EU and United States |
| Apple (Sign in with Apple) | Sign-in, if you choose it | The sign-in request; Apple returns your account identifier and email, which may be a private relay address | Ireland / United States |
| Google (Sign in with Google) | Sign-in, if you choose it | The sign-in request; Google returns your account identifier and email | United States |
| Resend (Plus Five Five, Inc.) | Sending account, receipt and waitlist emails | Your email address and the message | United States |
| Google Fonts | Typefaces on vibear.dev | Your IP address and browser details, when the page loads | United States |
Each acts on our instructions as a processor, except Apple and Google for sign-in and Stripe for its own legal obligations, which act as independent controllers under their own privacy policies. Meta processes data about your use of the Quest under Meta's own policies; VibeAR does not send Meta anything.
Transfers outside the European Union
Several of these services are in the United States. Those transfers rely on the EU–US Data Privacy Framework where the provider is certified under it, and otherwise on the European Commission's Standard Contractual Clauses, as provided in each provider's data processing terms.
Legal bases (GDPR)
- Contract: running your account, purchases, licences, plan quotas, and Cloud voice or AI skyboxes when you use them.
- Consent: turning on the microphone and choosing Cloud voice, the keyboard-camera feature, and waitlist emails. You can withdraw consent at any time by turning the feature off or unsubscribing.
- Legitimate interest: security, fraud and abuse prevention, server logs, and keeping AI costs accountable.
- Legal obligation: keeping invoices and accounting records.
How long we keep data
Account data is kept for as long as the account exists. When you delete it, everything listed above is erased immediately, except invoices and the accounting records tied to them, which French law requires us to keep for 10 years (held by Stripe and by us). The usage records we keep for our provider bills lose every link to you. Server logs expire on their own within 30 days.
Deleting your data
You can delete your account, and with it your data, from any of these:
- On the headset: Settings ▸ Mac ▸ Delete my VibeAR account.
- In the desktop app: Account ▸ Delete account.
- On vibear.dev: vibear.dev/delete-account.
- By email: write to support@vibear.dev from the address on the account. We reply within 30 days, usually much sooner.
Deleting the account cancels any subscription, frees your headsets, and erases your email, sign-in methods, licences, plan and usage. It reaches our providers too: the AI and speech providers' copies are deleted as well. Google and OpenAI hold no copy of your requests beyond their abuse-monitoring windows (55 and 30 days), which they delete automatically and which carry no identifier linking them to your account. If you ask us to, we will also send a deletion request to them on your behalf. Stripe deletes or anonymises your customer data except what it must keep by law. Data on your own computer and headset (notes, settings, files) is yours: uninstalling the apps removes it.
Your rights
Under the GDPR and the French Data Protection Act you have the right to:
- access your data and get a copy;
- rectify it if it is wrong (you can change your email in the desktop app);
- erase it (see above);
- restrict its processing;
- data portability: receive it in a machine-readable format;
- object to processing based on legitimate interest;
- withdraw consent at any time, without affecting what was done before;
- not be subject to a decision based solely on automated processing (we make none);
- set instructions for what happens to your data after your death.
To exercise any of them, write to support@vibear.dev. We answer within one month. If you are unhappy with our answer you can complain to the CNIL (Commission nationale de l'informatique et des libertés), 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France, cnil.fr, or to the data protection authority where you live.
Security
Traffic to vibear.dev is encrypted with TLS, passwords are stored only as salted hashes, headset licences are cryptographically signed, and collaboration content is end-to-end encrypted. The link between your headset and your computer is protected by a pairing code you confirm on both devices.
Reporting a vulnerability. If you find a security issue, email support@vibear.dev with "Security report" in the subject. Please give us a reasonable time to fix it before disclosing it. We will not take action against good-faith research.
Children
VibeAR is not directed at children under 15 and we do not knowingly collect their data. Meta Quest accounts carry their own age requirements.
Changes
If this policy changes in a way that matters, the date at the top changes and account holders are told by email before the change takes effect.
Contact
Xavier Jara · Paris, France · support@vibear.dev