Polydance privacy
Polydance is an app for testing apps in a headset, on Meta Quest and on Android XR. While you record, it captures what you see and say, and it sends each recording to the Polydance receiver at capture.polydance.net. There, it goes into the thread you recorded it in and becomes a review bundle: a transcript, still frames and a short summary.
What is recorded
- The view in the headset while a recording runs: apps, panels and passthrough, which can show the room you are in.
- Your microphone, unless you switch Mic off, and the sound of apps, unless you switch App sound off.
- Details of the recording: when it was made and how long it is, the headset model and its software version, the app's version, the thread it answers, and which links or apps you opened from the inbox while recording.
- Your Meta account: your Meta user ID and display name, given by Horizon OS when you sign in. They show the team who sent a recording, and let the receiver check your account proof and app entitlement with Meta. Entitlement does not prove current release-channel membership.
- Your Google account, on Android XR: your Google account ID, your name and the email address Google has verified, given by Google when you sign in with Google. They show the team who sent a recording. The address decides whether you are invited to the test, and puts you in the threads people have added that address to.
- Email addresses, if you give them: your own, and those of people you add to a thread. They are stored on the receiver and shown to the people in that thread and to the team. When you enter your own, Polydance emails you a link to confirm it; once confirmed, threads that invited that address are yours. When someone on the team adds an address to a thread, Polydance emails it once for that thread: who added it, the thread's title and how to join, never the thread's messages or recordings. Addresses added by anyone else are not emailed.
Nothing is recorded until you press record and accept the headset's own screen-capture prompt. The app does not collect your location, contacts, advertising identifiers or analytics, and shows no ads.
Where it goes
- The Polydance receiver, capture.polydance.net, a server Polydance runs. Recordings are sent over HTTPS and stored there in private folders.
- Gladia transcribes the microphone track. The receiver deletes the transcription job at Gladia once it has the text.
- Anthropic (Claude) writes each recording's title and summary from the transcript text. When the team has turned it on, Claude also looks at up to 24 still frames to name what you pointed at.
- AhaSend sends Polydance's emails: for an invitation, the address, the name of who added it and the thread's title; for a confirmation, the link. Open and click tracking are off, and every email has a link that stops all email from Polydance to that address.
- The Polydance team runs capture.polydance.net, so it has access to every thread's recordings, including the threads a newcomer starts in Getting started. When the team works in a thread, its coding agents read that thread's bundles on the team's own computers.
- People in a thread, those the team has added to it and whoever opened it by recording, and the team can play its recordings and read their transcripts in the app. Other testers do not see a thread they are not in.
- Reports, recorded with the bug key on the deck, are about Polydance itself: a bug or a feature you would like. Each goes only to the Polydance team, is processed the same way, and is not shown in your inbox or your recordings.
Nothing is sold or used for advertising.
How long it is kept, and deleting it
- A recording waits a few seconds after you stop before it uploads. Press Delete in that time and it never leaves the headset. Cancel while recording throws a recording away.
- Delete removes the headset copy and queues deletion from the receiver. The app reports pending or unconfirmed server deletion; it can wait for connectivity, sign-in or processing to finish. If access has been revoked or deletion stays unconfirmed, contact us to remove the server copy.
- A report is deleted from the headset as soon as the receiver has all of it, and one that cannot be sent is removed after a week. It has no Delete once sent; to have one deleted from the receiver, email privacy@polydance.net.
- To have an email address removed from the receiver, email privacy@polydance.net.
- Copies the team already downloaded to their own computers stay there until they remove them. Ask them, or us, if you want those gone.
- A tester's video is kept for 30 days after it is sent, then deleted on its own. The recording's transcript, still frames, summary and microphone track stay, so it can still be read, until it is deleted. This applies to everyone except the team that runs this receiver.
- Otherwise recordings are kept until deleted. Each tester has a storage allowance. When the receiver's disk fills, it deletes the oldest finished recordings first.
- The receiver operator can block your Meta user ID locally and restart the receiver to stop access. Removing you from a Meta release channel alone does not guarantee this. Access also stops when Meta denies app entitlement, or when entitlement has not been verified for 24 hours. To have everything you recorded deleted, email privacy@polydance.net.
- On Android XR, the receiver operator can remove your address from the invited list or block it, and restart the receiver, to stop access.
Asking to join, from the website
The form on polydance.net sends your email address, the headset you have and your note, if you write one, to this receiver. It keeps them for 180 days so the team can reply, and emails them to the team through AhaSend. The form never emails your address, and does not add it to any list. To limit misuse, your browser solves a small puzzle before the form is sent, and the receiver keeps a code made from your IP address (never the address itself) for the same 180 days. To have a request deleted, email privacy@polydance.net.
Counting visits to the website
polydance.net counts visits with Google Analytics only if you allow it in the bar at the foot of the page. Until you do, nothing is loaded from Google. If you allow it, Google Analytics sets cookies in your browser (_ga and one starting _ga_) and sends Google the pages you view there, the site that sent you, your browser and device, and roughly where you are, worked out from your IP address. Google keeps the visit data for 2 months and what it holds about your browser for 14 months, and may handle it outside the UK. Google signals is off, so none of it is joined to a Google account. The Cookies button at the foot of the page changes your answer; saying no removes the cookies. Your answer is kept in your browser, not in a cookie.
Who may use it
Polydance uses a private-beta-only admission model for adults invited to test: a valid Meta account proof and app entitlement, subject to a receiver-local blocklist and tester limit. There is no separate receiver allowlist; this model must not be used for public distribution. Meta requires testers in private release channels to be 18 or older.
On Android XR, signing in with Google admits only the addresses the team has invited, subject to a receiver-local blocklist and tester limit. Google confirms who you are, not that you may test.
Contact
For questions about this notice or your recordings, email privacy@polydance.net.