Simulator data
& privacy.

If you sign in with Google, we receive your Google account identifier, email address, display name, and profile image. We use these details to authenticate you and create your simulator account. Your email is not shown on the public leaderboard.

Every completed cup-stacking run records simulator-only data: task and difficulty, timestamps, robot joint state and controls, headset and controller poses and inputs, mapped teleoperation targets, magnet state, cup poses and velocities, completion checks, client/version labels, and technical metadata. A bounded local browser queue may temporarily hold a failed episode upload for up to 24 hours so it can retry. We also store session and attempt records, scores you register, and limited error diagnostics such as an error message, stack trace, route, browser type, and simulator state.

Your chosen username, best time, recent registered scores, difficulty, run count, and leaderboard rank may be public. You choose the username once and cannot change it afterward; deleting the account removes it. Your Google email, Google identifier, raw session data, episode files, and diagnostic events are not public.

We use the data to operate the PC-to-Quest simulator, verify submitted times, detect abuse, maintain leaderboards, diagnose failures, improve the experience, build simulation datasets, and develop or evaluate future robotic-control and related machine-learning models.

Before opening the PC control room, you must accept the current simulator data notice. That consent covers recording completed simulator runs and their possible future use for model development, training, evaluation, and research. We version and timestamp this consent with each stored episode. If the purpose changes materially, we will update this notice and ask again.

Account details and public scores remain until you delete them. Raw completed episode archives and anonymous or de-identified session records are retained for up to 12 months. Minimal attempt records that support a score remain with that score. Error diagnostics are retained for up to 90 days. Backups may retain deleted identity or score data for up to 30 additional days before rotation. We may retain aggregated statistics that no longer identify an account.

After signing in, the PC control room provides separate controls to sign out, delete all public scores, or delete your simulator account. Score deletion removes leaderboard entries and statistics but keeps non-public session and episode records under the stated retention period. Account deletion removes the Google account identifier, email, display name, public username, avatar, public scores, leaderboard statistics, and account-linked diagnostics. Completed cup-stack sessions, attempts, and episode archives are retained without the account link until their normal retention expiry and may still be used for model development, training, evaluation, and research.

We use Google for authentication, Vercel to host the application, Neon Postgres for account and simulator records, Upstash Redis for short-lived signaling and rate limits, and Cloudflare TURN when a relayed WebRTC connection is needed. We limit public data, protect internal exports with an administrator allowlist, rate-limit sensitive endpoints, and hash completed episode contents. No internet service can be guaranteed perfectly secure.