Play Lounge Data Retention Policy
1. Purpose and Owner
This policy covers the personal information Play Lounge holds, including persistent identifiers from users of any age, and it is our written data-retention policy for children’s personal information under the U.S. Children’s Online Privacy Protection Act (COPPA). NeuEra Apps LLC owns it and reviews it every year, and whenever a new kind of data is added. The retention table in Section 5 of our Privacy Policy summarises it.
2. Rule
We keep each item only as long as the purpose below needs. Deletion is automatic wherever the software can do it. Nothing is kept “just in case”, and nothing about a child is kept indefinitely.
3. Retention Schedule
| Item | Purpose | Retention | How it is deleted |
|---|---|---|---|
| Random player ID | Run the game; reconnect you | Until you disconnect, plus a 3-minute grace period in a game; it can be restored for 24 hours through the session token | Automatic |
| Session token | Reconnect you | 24 hours | Automatic: it expires; signing out revokes it |
| Room code | Private games | 5 minutes without activity, 2 hours at most | Automatic |
| Game checkpoint (two random player IDs and the board) | Resume a game across a server restart | Deleted when the game ends; at most 1 hour, swept every 15 minutes | Automatic |
| Missed result | Tell a player the result of a game they missed | 15 minutes | Automatic (server memory) |
| Running score between players without accounts | Show the running score | 30 minutes without a game; lost on a server restart | Automatic (server memory) |
| IP address | Daily visitor counts, de-duplicating visits, protecting the service from abuse | Server memory only: a scrambled form for the day’s visitor count, the address itself for the day to de-duplicate visits, and 30 minutes for the promotion banner’s click filter. Never logged or written to disk | Automatic |
| Daily totals | Run and improve the service | Kept; they hold no identifier, IP address or free text | — |
| Return counter (scrambled random device identifier, platform, first and last day seen, days visited, return flags) | Count new and returning visitors | 90 days after the device’s last visit | Automatic, daily. Never joined to a player ID or an account |
| Server logs (random player IDs and technical events; no IP address, user agent or token) | Find and fix faults | 7 days | Automatic (our host’s log retention) |
| Disk snapshots of our server’s database | Disaster recovery | 5 days | Automatic (our host) |
| Support messages (email, optional first name, message) | Answer the request | Until resolved, at most 90 days. A child’s email address is used to reply once, then deleted | By hand |
| Account (Firebase user ID, provider, created / last used / last sign-out times, generated game name) | Sign-in; saved scores; signing out everywhere; the game name shown to opponents | Until the account is deleted, or 730 days (two years) without use | Automatic: the account-deletion path, and a daily sweep for accounts not used for 730 days |
| Saved scores between signed-in players | Keep the score across devices | Deleted with either player’s account, including when it expires | Automatic, with the account |
| The player’s record (per game and level: won, lost, drawn and left-early totals, last updated) | Show the player their own record on every device | Deleted with the account, including when it expires. No game history is kept | Automatic, with the account |
| Record-merge fingerprints (one-way fingerprint of a one-off random code, time) | Add a device’s record to the account only once | Deleted with the account | Automatic, with the account |
| The device’s own record (totals per game, days played in a row, results waiting for an account) | Show the player their record, with or without an account | On the device only; never sent while signed out | The player: clearing the site’s data or uninstalling the app |
| Firebase deletion queue (Firebase user ID, attempts, next attempt) | Finish deleting the Firebase user if Google can’t be reached | Until Google confirms the deletion: about 9 hours of automatic retries, then completed by hand within 30 days | Automatic, then by hand |
| Deleted-account fingerprint (one-way fingerprint of the user ID, deletion time) | Stop a still-signed-in device from re-creating a deleted account | 30 days | Automatic, daily |
| Email, name, photo and user ID at Google Firebase | Sign-in | Until the account is deleted; our server asks Google to delete them | Automatic |
| Age-check answer | Decide whether sign-in is offered | Never leaves the browser; only a “not eligible until” date is kept, for one year | Automatic (the browser) |
| An account found to belong to a child under 13 | None | Deleted as soon as we learn of it | By hand, through the same deletion path |
Database rows deleted from the live database also leave the disk snapshots within 5 days.
4. Deletion Requests
We answer a deletion request sent to hello@neuera.app within 30 days, and delete through the same path as in-app account deletion. We record only the date and that it was done, never the email address.
5. Contact
NeuEra Apps LLC, 1968 S. Coast Hwy #2044, Laguna Beach, CA 92651(818) 641-0005 · hello@neuera.app