Who is responsible
Brian Chen in Norway operates the Chen Chess Coach staging beta and is the data controller for the personal data described here. Email support@chenchess.space with a privacy question or request.
Information the beta handles
- Beta access: an access-request email, invitation and delivery status, Beta Access state, and administrative audit facts needed to operate the invitation lifecycle.
- Identity: a Firebase Player ID, verified email, supported sign-in method, authentication timestamps, and the minimum authorization state needed to protect the product.
- Coaching: a normalized completed game, Review Side, rating input, generated chess facts, and short-lived Review Session state. Original pasted PGN text is not retained after normalization.
- Security and operation: minimized request, failure, timing, and rate-limit records. Logs exclude form bodies, emails, invitation codes, Firebase tokens, and OAuth secrets.
Why it is used
The information is used to consider and deliver beta access, authenticate Players, provide and restore requested coaching, prevent abuse, diagnose failures, and protect the service. Access requests are not marketing subscriptions. Chen Chess Coach does not sell beta data or use it for advertising.
Service providers
These providers process limited data only for the product or its infrastructure. They are not marketing recipients.
- Firebase and Google
- Firebase supplies identity and Firestore storage. Google is also involved when a Player chooses Google sign-in. Firebase privacy information
- Railway
- Railway hosts the staging application and its private services. Railway privacy policy
- Resend
- Resend delivers transactional beta invitations. Open and link tracking are disabled. Resend retains sent-email data for its standard 30-day period. Resend privacy policy
- ImprovMX
- ImprovMX forwards messages sent to Chen Chess Coach support and invitation addresses to the operator. It does not grant access. ImprovMX privacy policy
- Vercel
- Vercel supplies authoritative DNS. It does not host this beta or receive invitation email. Vercel privacy notice
A Coach App conversation also remains subject to the privacy terms of the Player's chosen host, ChatGPT or Claude. Chen Chess Coach receives only the product requests that host sends to the Coach MCP connection.
Retention
- Access requests, invitations, delivery status, and Beta Access remain only until revocation where applicable, a verified deletion request, or beta closure.
- Keyed rate-limit identifiers expire within 24 hours.
- Application security and operational logs expire within 30 days.
- Player-owned Game Import Records and Review Sessions have a 14-day absolute limit; an inactive Review Session becomes unavailable after 72 hours.
- Identity-free Game Analysis cache entries expire after 30 days without reuse and never persist beyond 90 days.
Storage cleanup may complete after the logical deadline, but expired records are not treated as available product data.
On beta closure, the operator stops beta write traffic and erases staging access requests, invitations and delivery metadata, Beta Access grants, keyed rate-limit records, and beta OAuth state. A provider's independent retention period still applies; in particular, Resend may retain its sent-email copy for 30 days.
Your choices and requests
Email support@chenchess.space to ask what beta data is associated with you, correct it, object to or restrict its use where applicable, receive a portable copy where applicable, or request deletion. After verification, a beta-data deletion removes your access request, invitation and delivery metadata, Beta Access grant, and beta OAuth grants. It leaves your Firebase sign-in identity in place. Ask separately for whole-account deletion if you also want that identity and Player-owned coaching data removed. Chen Chess Coach may need to verify that the request comes from the relevant person before acting. You may also complain to the Norwegian Data Protection Authority or your local supervisory authority.
Changes
This notice may change as the beta changes. A material update will receive a new effective date and, where appropriate, a notice in the product. Production requires a fresh review of this notice and the operator identity.