Privacy Policy
Caption This: Word Party
Effective date: July 21, 2026
Caption This: Word Party is a private-room multiplayer word party game. The publisher identity displayed on Google Play operates the service. This policy explains the v1 service; the production providers and Play Data safety declaration must remain consistent with it.
Data We Collect
We process nicknames, room codes and settings, answers, votes, reports, moderation records, game results, random room/player/reconnect identifiers, connection events, latency, errors, IP address and request metadata used for security and rate limiting, invite/share events, and minimized operator-enforcement events linked to random answer/player targets. Enforcement analytics do not copy answer text or moderator notes. If you contact support, we process the contact details and information you choose to send.
Data We Do Not Require
No account, email address, phone number, contact-list access, precise location, camera, microphone, or payment data is required for v1 gameplay.
How We Use Data
We use data to run and reconnect rooms, show prompts and results, apply security limits, process reports, respond to requests, improve reliability, measure aggregate game flows, enforce rules, and meet legal obligations.
Sharing
We do not sell personal data. Hosting, database, security, monitoring, and support providers may process data on the operator's instructions. Information may also be disclosed when required by law, to address an urgent safety risk, or to enforce rights. Invite links are sent to another app or person only when a player uses the share flow; room participants receive the nickname and game content needed to play.
YouTube Video Prompts
Scene Spin loads video from youtube-nocookie.com only after the player chooses to load it. Google/YouTube may then receive network and device information such as IP address, user agent, referrer, and player interactions under the Google Privacy Policy and YouTube Terms of Service.
Retention
Active room data becomes inaccessible and expires after 6 hours of inactivity by default. Redis uses a local append-only recovery log, so obsolete room commands can remain in that log until verified compaction. In a healthy production deployment, compaction is due every 6 hours, checked within 15 minutes, and has a 10-minute maintenance deadline, bounding this residual log history to 6 hours 25 minutes after logical expiry; a missed or failed compaction makes the service unready and requires operator response. Reports and moderation evidence are deleted after 548 days by default unless an authorized responder places a durable, audited safety or legal hold; held reports are exempt from automatic deletion until the hold is released after review. Raw analytics events are deleted after 730 days by default; data that can no longer reasonably be linked to a player may be retained longer. Unencrypted backup staging files are access-restricted, transferred promptly to encrypted off-host storage, removed after verified transfer, and aged out under a limited lifecycle. See the Data Deletion page for requests.
Security
Production traffic uses HTTPS/WSS. Access and secrets are restricted to people and providers needed to operate, secure, and support the game. Local backup staging files require restricted host access until verified encrypted off-host transfer and removal. No system is completely secure, and data may be processed outside your country subject to safeguards required by applicable law.
Children
The service is for players aged 13 and older and is not directed to children under 13. Do not submit a child's personal information.
Contact
For privacy questions, rights requests, safety reports, support, or deletion requests, contact dhanur2@gmail.com. Depending on local law, you may have rights to access, correct, delete, restrict, or object to processing and to complain to a data-protection authority.