Privacy policy
Publisher: AIRMEET INC. (Google Play developer name: Airmeet). Privacy and support contact: vinay@airmeet.com, confirmed by the owner as the public contact. The current website footer says “GreyFlakes Studio, a division of Airmeet Inc.”
What MoveToPlayGames does
MoveToPlayGames is a set of movement-controlled games for a television or web browser. A camera can be used on the TV, or a phone can act as the camera and send movement landmarks to the paired TV. This release is intended for players ages 6 and older, including children and adults. Children should have a parent or guardian help with setup and camera use and supervise safe play.
AIRMEET INC. uses data handled by the game to provide gameplay, pair devices, and operate and improve the service. It does not sell personal data or use camera or movement data for advertising or unsolicited marketing. The product records limited page and setup events through PostHog, as described below, and has no in-game feedback form.
Camera and movement data
- TV-camera mode: with the user's permission, the TV browser reads camera frames and runs pose tracking locally to control the game. The game code does not upload those frames, and does not record them except as described for Freeze Statue below.
- Phone-input mode: after the user taps “Open camera,” the phone browser reads camera frames and runs pose tracking on the phone. It sends normalized body-landmark samples (33 points with x/y/z/visibility values) over a WebRTC data channel to the paired TV. The game code does not send the phone's camera frames to the TV or signaling endpoint.
- Freeze Statue mirror and Statue Gallery: during Freeze Statue the game draws the camera image, mirrored, on screen and turns it into stone, ice or gold during each freeze. This happens on the device only. If the player chooses to save a freeze photo (by raising both hands, tapping it or pressing Space), a small still image (240×180 pixels) is stored in browser storage on the game origin, up to 12 per player. Statue Gallery photos are never uploaded. Pressing X twice on the gallery screen deletes them, and so does clearing site storage or the Android app's “Clear profiles and scores.” In phone-input mode the TV has no camera frames, so the mirror and saved photos show a drawn figure made from the pose landmarks.
- Pose landmarks describe body position and movement. The TV uses them as live game input; the application code does not save a motion history. This transfer is necessary for phone-controlled play and should be disclosed before camera access.
- WebRTC data-channel traffic is protected by DTLS between the paired browsers. The signaling server supplies ICE settings and exchanges SDP. The production pairing endpoint currently returns Google's public STUN service (
stun:stun.l.google.com:19302) and no TURN relay. STUN can receive connectivity requests and ordinary network metadata; it does not relay the pose data channel. The signaling service participates in connection setup, so DTLS is not a guarantee against compromised app code or a malicious signaling service. If a TURN relay is added in a future release, this notice will be updated to describe its role.
Profiles and scores
Player display names, local player IDs, selected player, scores, leaderboards, and unlocked levels are saved in browser storage on the TV/game origin. They are not uploaded by the game's profile and score code. Children should use a nickname rather than a full name, with a parent or guardian's help. This data stays until it is cleared in the app, removed from browser/site storage, or the Android app data is cleared or the app is uninstalled. The Android TV setup offers “Clear profiles and scores.”
Pairing and technical service data
Phone pairing sends temporary random pairing credentials and a WebRTC session description (SDP) between the TV, phone, and the website's signaling endpoint. SDP can contain ICE network-address candidates. The server keeps pairing-room state in memory for up to five minutes and the TV deletes it after connecting or cancelling. The signaling server does not carry camera frames or the WebRTC pose-data-channel payload.
The Python site server logs ordinary static-file requests with a timestamp, connection peer address, request line (including method and path), status, and response size. Behind Railway, that peer address may be a proxy address rather than the user's address. Pairing API requests are excluded from this application access log. Railway's public privacy policy describes device/IP retention as long as needed to operate its systems and states no fixed maximum period; Railway also describes platform event logging. The application does not set or control Railway's log-retention period or access controls. Other infrastructure providers may process connection metadata under their own practices.
The linked Railway production service reports a deployment region of us-west2 (United States). Pairing room state and service processing may therefore occur in the United States. Network and relay providers may process connection data in other locations according to their service configuration.
Service providers and external resources
The app requests page code, assets, and locally hosted Fredoka and Baloo 2 font files from its website host; pose-tracking and QR-code code from jsDelivr; and a pose model from Google Cloud Storage. The TV game does not request fonts from Google Fonts or assets from ImageKit. The game and phone capture pages also load PostHog analytics code and send the limited events described below to PostHog’s US service. The public homepage separately loads web fonts from Google Fonts, and public marketing pages load guide illustrations and a promotional video from ImageKit. The production pairing endpoint currently returns Google's public STUN service (stun:stun.l.google.com:19302) and no TURN relay. These hosting, delivery, and connectivity services may receive an IP address and ordinary connection metadata needed to deliver resources or establish a connection. Camera frames are not sent to the website host or signaling endpoint. In phone mode, pose landmarks are sent to the paired TV through an encrypted WebRTC data channel; the app server does not receive these data-channel packets. Providers' own retention and privacy practices apply to the metadata they process. If connectivity configuration changes to include a TURN relay, that relay may forward encrypted packets and observe connection metadata; this notice should be updated before that change is released.
The game web view (including Android TV) and phone capture-assist page use PostHog for page views and basic setup events, such as pairing success or failure and camera start or stop. Events exclude camera frames, pose landmarks, player nicknames, scores, pairing credentials, URL queries and fragments, referrers, and raw error messages. Automatic click/text capture, session replay, surveys, and person profiles are disabled. Analytics uses temporary in-memory identifiers rather than persistent analytics cookies or localStorage, and respects browser Do Not Track and Global Privacy Control signals. PostHog’s US hosting receives ordinary network metadata, including an IP address to deliver requests; client configuration disables IP-based event enrichment. Provider retention is governed by the project’s PostHog settings and the provider’s practices. No feedback form, account registration, advertising SDK or in-app purchase has been added.
Children, adults and supervision
Children ages 6 and older and adults are the intended audience for this release. A parent or guardian should help a child connect devices, position the camera, check the play area, and supervise movement. Children should not enter a full name as a player name. The app has no account or messaging feature. A parent or guardian may contact vinay@airmeet.com about a child's information. The app does not provide a form to submit contact details.
Security and deletion
The Android app requires secure HTTPS content, rejects TLS errors, disables Android backup, and does not expose a JavaScript-to-native bridge. Phone invites are single-use, expire after five minutes, and are placed in the URL fragment; the phone page removes the fragment from browser history after reading it. Stop the phone camera or close/background its page to stop capture. Local profiles and scores can be cleared as described above. The app does not set a fixed retention period for hosting or connectivity-provider logs; those providers' published practices govern their own logs.
Contact and changes
Publisher: AIRMEET INC. (developer name: Airmeet). Privacy/support contact: vinay@airmeet.com. Last reviewed: 30 September 2026. The app's Play disclosures should be kept consistent with this notice.