Privacy policy

What a meeting shares

The app processes these data to connect participants, assign seats, display names, and animate avatars:

• Your chosen display name and temporary participant and seat identifiers.
• Your Meta avatar user ID, when available, and fallback preset number.
• Head position and rotation, the tracking origin, and compressed live avatar animation derived from headset, controller and optional hand-tracking input.
• Network addresses and connection information needed for room connections and optional live screen sharing.
• Shared putting-game ownership, putter and ball positions, and stroke counts.

Internet rooms use a StandupVR relay hosted by Render. The relay processes room codes, temporary membership, names, Meta avatar IDs and presets, head poses, compressed avatar motion, putting state, and screen-sharing connection messages to deliver them to the same room. Connections to this service use encrypted WebSockets. Relevant endpoints can see network addresses. There is no custom analytics upload or server recording of meetings.

Optional Quest hand tracking provides wrist and finger poses and pinch input for pointing at controls and animating your Meta avatar. The app does not receive raw camera images. Compressed avatar animation, including hand motion, is shared with participants in the same room; the optional self-preview stays local to your device.

The companion page lets you explicitly choose a browser tab, window or screen to show to the room. It sends live video using encrypted WebRTC connections, directly where possible and through a TURN relay when configured and needed. TURN relays forward encrypted video and process network/connection metadata; they do not receive the video decryption keys. Stop sharing in the page or browser to stop that capture. StandupVR does not record this video. The selected surface may contain personal information, so choose it carefully.

This version does not enable eye, face or full-body tracking. Avatar body motion is generated from headset, controller and optional hand input. Browser screen sharing remains video-only; optional meeting voice is a separate service described below.

Optional meeting voice

When configured, choosing to join voice connects to LiveKit Cloud using your chosen display name, a pseudonymous session identifier and a room-specific voice channel. Microphone audio is sent through LiveKit to people in that channel only after deliberate opt-in and the required device permission. Mute stops transmission; leaving the room or closing the app ends the voice session. Voice is separate from the screen-video TURN relay. Received voices are positioned at participants’ virtual heads using the room’s existing position updates.

StandupVR does not intentionally record voice or start recording exports, AI agents, transcription, inference or voice cloning. The SDK’s ability to support those features does not enable them. Other participants could make their own recordings. WebRTC encryption protects transport to LiveKit; this build does not claim end-to-end encryption. LiveKit processes media/session data under its data processing addendum; its privacy policy describes its own account and telemetry processing.

Meta services

The Meta SDK contacts Meta for account authentication, app entitlement and avatar assets. Access tokens stay with the local SDK flow; StandupVR does not put them in room packets or app settings. Meta may process information and retain SDK or account data under its own policies, including the Meta Platforms Technologies privacy policy. A preset can be used when account-avatar access is unavailable.

Optional testing tools

Enabling Test details writes a local CSV containing UTC time, platform, room role/count, frame/performance measurements, tracking/avatar readiness, preview state, and aggregate animation payload rates. It does not write names, user IDs, tokens or a history of poses to that CSV.

The desktop lab can log display names and LAN addresses. Manually collected Quest logs can include device serial numbers, process/user identifiers and diagnostic messages. Tools do not automatically upload these files. Review them before sharing; any recipient receives the copy you send.

Optional conduct and content reports

StandupVR uses Meta’s User Reporting Service. You can choose to submit a report about conduct or content through the Report option in the Quest universal menu. Meta processes the report you submit and delivers it to the developer’s support address, support@standupvr.quest. Delivery uses the support forwarding and mailbox services described below.

The developer uses reports and the information included in them to investigate the reported issue and respond as appropriate. The reporting configuration does not request the reporter’s email address; information you choose to include still forms part of your report. Enabling this reporting service does not enable automatic voice or screen recording by StandupVR. Meta’s own reporting flow and policies govern information submitted through that flow.

Website and support

The product and legal pages are static. The screen-sharing page runs local JavaScript, accepts a room code, connects to the room service and requests capture only after you choose to share. The code is kept in the URL fragment when opened from the app; fragments are not sent in ordinary website requests. The website has no custom analytics or third-party fonts, and its code sets no cookies. Vercel hosts it and may process IP addresses and request/device metadata for delivery, reliability and security. See Vercel’s privacy notice.

If you contact the developer, your address, message and attachments are processed to answer you and investigate the issue. The StandupVR support address uses ImprovMX to forward messages, including Meta user-report deliveries, to the developer’s inbox; the forwarding service and mailbox provider process those deliveries. See ImprovMX’s privacy policy. Send only what is necessary. Do not send passwords or access tokens.

Render hosts the room service in Frankfurt. Render and, when used for video relay, Metered process service and network information under their own policies: Render privacy policy and Metered privacy policy.

LiveKit Incorporated provides optional meeting voice separately from Render’s room service and Metered’s video relay. Meta, Vercel, LiveKit and relay providers may process data outside Germany and the EEA. Their notices and processing agreements describe their practices and transfer safeguards; see LiveKit’s data processing addendum and Vercel’s data processing addendum.

What remains afterwards

Leaving disconnects you and clears active membership and pending pose/stream buffers. The internet relay holds active room state in memory, replacing live motion with the latest updates. A departed member’s current state is removed; empty rooms retain their code for up to two minutes for reconnection. Rooms expire after at most six hours or a server restart. Screen-sharing connection messages are forwarded rather than stored as a meeting history. Hosting providers may retain operational request and network logs under their own policies. Leaving does not erase exported files, other participants’ copies, or Meta SDK process state and caches.

Local reports and lab/log copies have no automatic expiry and remain until manually deleted. Support messages, user reports and files held by the developer are retained only as needed to resolve the request, investigate the reported issue, meet legal obligations or handle related claims, then deleted. Meta, Vercel, LiveKit, Render and any TURN provider apply their own retention rules. Leaving a room, leaving voice or removing the app does not itself erase submitted user reports or provider operational records; use the contact below for requests concerning information held by the developer.

LiveKit’s retention schedule distinguishes delivered media from telemetry: user content is deleted after delivery except where law requires otherwise or a customer enables recording/logging. Telemetry defaults to up to 60 days, with longer exceptions for billing, security and legal purposes. StandupVR does not enable recording or AI-agent observability.

Your choices and rights

Joining shares the data needed for the room; without it, that function cannot operate. Test reporting and sharing support files are optional. StandupVR is intended for ages 13 and above and does not ask for a date of birth.

Meeting voice is optional. You can keep using the room without transmitting microphone audio, mute in the app, or deny/revoke microphone permission in your device settings. Permission and connection status are shown separately from room membership.

Your voice opt-in and mute choice are saved locally. After a deliberate first opt-in, a later authorized room connection or resume can restore that choice without another permission prompt. Mute before leaving if you want the microphone to stay muted on rejoin.

Where the GDPR applies, the legal basis is legitimate interests in providing the requested prototype, answering support and operating a secure website (Article 6(1)(f)); consent is used where legally required. There is no advertising profiling or automated decision-making with legal or similarly significant effects.

Where applicable, you can request access, correction, deletion, restriction or portability, object to legitimate-interest processing, and withdraw consent without affecting earlier lawful processing. You can complain to your data protection authority. Contact the developer below; see data deletion instructions for practical steps.