Your microphone is for the game—not a background listener.

When microphone permission is used

Permission is requested after you press a microphone or play control that needs audio input. A mic check reads the current input level so you can confirm that your voice is audible; it does not create or upload a take. During a round, recording begins only for the announced recording window. Live voice chat is muted while everyone records so other players' voices are not mixed into the take.

You can remove microphone permission through your browser's site settings. The game cannot record after the browser stops or denies the microphone track.

Where recordings go

Live voice chat and network addresses

Live chat uses direct peer-to-peer WebRTC connections when the network permits them. As with other peer-to-peer calls, participants' IP addresses can be visible to one another through the connection. Public STUN services help establish the direct link. A relay may be configured for restrictive networks, but a relay is not guaranteed to be available. Use headphones to reduce echo.

Information kept in your browser

The application may store:

• Your chosen party name.
• An opaque signed guest credential for reconnecting to Cloudflare.
• Recent sound history so fresh clips can be preferred.
• A small public-party result recap without recordings or room credentials.
• Local tab-test room state and recordings.
• A legacy Supabase guest session when an older room uses that backend.

Browser storage is specific to the browser profile. You can remove it using the game's available clear controls or your browser's site-data settings.

Analytics and reliability diagnostics

The public frontend includes Vercel Analytics and Speed Insights to measure visits and loading experience. Online Cloudflare rooms also send bounded reliability diagnostics such as capture or decode failures, reconnects, platform category, transfer size and latency buckets. These diagnostics help identify broken gameplay; they expire with the room and are not recordings or authoritative billing data.

Hosting providers necessarily process ordinary request information needed to serve the site and backend. Chiri Party's private operational pages are excluded from search and require separate administrative credentials to show detailed activity.

Names, room codes and public parties

A party name is visible to the people in the room. Treat room codes and invitation links as access information and share private-room invitations only with people you intend to invite. Random public parties match you with strangers, who can see your party name, hear your submitted takes and use live voice chat while you share a room. Do not use a party name that reveals personal information you want to keep private.

Questions or problems

This page describes the current implementation and should change when the product's data handling changes. To report a privacy or technical issue, open an issue in the project's public repository without including a room code, credential or recording.