Legal

Privacy Policy

Last updated October 9, 2026. This policy covers the apps listed here, including FloatPlayer, CloseCircle, and vrdesk web.

The short version

Deskcrew, Meme Vault, Kawaii Coffee Timer, and Relay have app-specific policies. Read each policy for that app's data practices, purchase handling, and optional measurement features.

Most apps on this site work entirely on your Mac and do not collect, store, or transmit your personal content. FloatPlayer, CloseCircle, and DevForge send limited, content-free product analytics described below. vrdesk is the connected exception described in full below: its native media stays on your local network, its web media is peer-to-peer, and the web edition sends only connection-setup messages through Supabase. These apps do not use advertising or behavioral tracking.

What the apps access — and where it stays

Each local utility only touches what it needs to do its job, and its working content stays on your device:

Purchases

Some apps offer an optional one-time “Pro” purchase. Purchases are handled by Apple through the App Store. Clip Contract validates its Pro entitlement directly with Apple's StoreKit. Some other apps use RevenueCat, a purchase-management service that receives an anonymous identifier and basic device information — never the content you use the app with. We do not receive your payment details; Apple handles all payment information. See also Apple's Privacy Policy.

Data we collect

None for the Mac utilities above except DevForge. We do not operate servers that receive your content. DevForge sends a random installation identifier and content-free product interaction, foreground-active time, bounded error, and purchase outcome events to Supabase for analytics; its full disclosure is available in the DevForge Privacy Policy. CloseCircle sends a random installation identifier plus content-free screen, active-time, and completed-workflow events to Supabase; its full disclosure is available in the CloseCircle Privacy Policy. No app uses this data for advertising or cross-app tracking. Apps that are still in evaluation run their purchase flow locally with no network activity at all. FloatPlayer sends a random installation identifier plus content-free screen, foreground-active time, video-source category, playback, Picture in Picture, import, and bookmark outcome events to Supabase; its full disclosure is available in the FloatPlayer Privacy Policy. vrdesk is the other connected app in this collection — its current iOS release offers an optional subscription without requiring an account, and its web edition uses cloud signaling; exactly what those services handle, and what they never touch, is described in vrdesk — Quest headset, web, iPhone, and Mac below.

Permissions you may be asked for

These permissions are granted by you in System Settings and can be revoked at any time.

vrdesk — Quest headset, web, iPhone, and Mac

vrdesk streams your Mac's desktop to a Meta Quest headset so you can work in VR, with an optional iPhone acting as an extra display. It has more moving parts than the single-purpose Mac utilities above, so its data practices are spelled out here in full. The controller of any personal data described in this section is Dupree Ops LLC. You can reach us at isaiahdupree33@gmail.com.

How native vrdesk is built — screen content stays on your local network

vrdesk connects your Mac and your headset directly, peer-to-peer, over your own Wi-Fi or LAN. The Mac host announces itself on the network with a discovery beacon; the headset finds it and completes a 6-digit pairing; the desktop is then encoded as H.264 video and sent to the headset over WebRTC. There is no cloud server, no relay, and no analytics in this path. Your screen, keystrokes, mouse movements, and audio travel device-to-device on your network and reach only the headset you paired with — they never reach us.

Web edition

The web edition uses your browser's screen picker to capture only the display, window, or tab you choose. Screen video and optional shared audio travel directly between the host browser and viewer through encrypted WebRTC; vrdesk and Supabase do not receive or store those media frames. The web edition uses Supabase Realtime to exchange the temporary technical messages needed to establish that peer-to-peer connection: a random room capability, WebRTC session descriptions, ICE network candidates, connection role, and timestamps. A room exists only while its participants are connected; vrdesk does not write it to an application database. Supabase may process ordinary service metadata such as IP address and connection logs under its privacy policy. No vrdesk account, name, email, analytics profile, or recording is created.

What vrdesk collects — and what it never touches

vrdesk never collects, stores, or transmits to us any of the following: the contents of your screen, the windows or documents you have open, your keystrokes, your mouse input, audio, your files, or your browsing. There are no advertising or behavioral-tracking SDKs in vrdesk; RevenueCat provides the purchase-service analytics described below.

The only personal data vrdesk collects through Apple and RevenueCat is what's needed to identify the entitlement customer, validate purchases, and remember a Pro unlock across your own devices:

For App Store privacy disclosure purposes, vrdesk classifies User ID and Purchase History as linked to you. Both are used for App Functionality and Analytics because RevenueCat provides receipt validation, entitlements, Customer History, Charts, and Experiments. Neither category is used for advertising or cross-app tracking, and vrdesk does not collect the screen, input, audio, or file content you stream on your local network.

No account required

Version 1.0 build 4 removes Sign in with Apple and does not create a user account or request a name or email. The app generates an opaque identifier for purchase validation and shares that identifier with your Mac for Pro synchronization. Existing installations retain their previous identifier to preserve purchase history. Restore Purchases uses your App Store account to restore eligible purchases on another iPhone or iPad.

Purchases & subscriptions (RevenueCat)

vrdesk Pro is an optional auto-renewing subscription sold in the iPhone app and handled by Apple through the App Store. To validate the subscription and unlock Pro across your devices we use RevenueCat, which receives the persistent entitlement user identifier, basic device and locale context, Apple receipt and transaction information, purchase history, entitlement state, and last-seen time. vrdesk does not send your name or email, and RevenueCat never receives your payment card or the screen, input, audio, or file content you use vrdesk with. Apple handles all payment information; we never see it. RevenueCat documents the required Purchase History purposes in its Apple App Privacy guidance. See also Apple's Privacy Policy.

Mac App Store edition

The native Mac App Store edition is view-only. It contains no RevenueCat or analytics SDK and sends no purchase identifier to a server. Apple's content picker lets you select one display or window. JPEG frames and short-lived pairing tokens remain in memory and travel only to paired devices on the local network. The app does not retain recordings. Stopping sharing disconnects viewers and invalidates session tokens. This local stream is not encrypted; use a trusted network. The edition requires local network access and your selected screen/window capture, but no Accessibility permission.

Web permissions

The web edition requests Display Capture only after you press “Choose what to share.” Your browser presents its own picker, shows an active-sharing indicator, and lets you stop the capture at any time. Immersive mode requests WebXR only after you press “Enter VR” in a compatible Quest Browser.

Permissions by device

Every one of these is granted by you and can be revoked at any time in that device's system settings.

Third parties we rely on

vrdesk uses a small number of sub-processors, each for a single narrow purpose:

There are no advertising or behavioral-analytics SDKs. RevenueCat's purchase-service analytics are limited to its Customer History, Charts, and Experiments functions and are not used for advertising or cross-app tracking.

Retention & deletion

The native screen, input, and audio path remains on your local network and is not retained by vrdesk or RevenueCat. Web-edition screen and audio media are peer-to-peer; its Realtime setup messages are transient, while Supabase may retain operational logs under its service practices. RevenueCat retains the custom user identifier and purchase-service customer history under its service retention practices. Deleting the app removes its ordinary local container, but Apple Keychain data may persist according to platform behavior. Older installations can revoke their prior Sign in with Apple authorization in iOS Settings; this does not delete purchase history or cancel a subscription. To end billing, cancel the subscription in the App Store. To request deletion of the vrdesk customer link and data under our control, email isaiahdupree33@gmail.com and identify the request as vrdesk data deletion. Limited transaction records may remain where required for fraud prevention, accounting, disputes, or law.

Security

A native stream only starts after you enter your Mac's 6-digit pairing code in the headset, and it flows peer-to-peer on your own network. The web edition uses an unguessable 80-bit room capability and encrypted WebRTC media. Anyone who receives the complete live web room link can attempt to join that session, so share it only with the intended viewer and stop sharing when finished.

Children

These apps, including vrdesk, are not directed to children under 13 and do not knowingly collect any information from children.

Changes

If this policy changes, the updated version will be posted here with a new date.

Contact

Questions? Email isaiahdupree33@gmail.com.