← Home

Privacy policy

Updated:

This policy explains data handling on the Rookie Lab website and apps. Features vary by platform, version and region. Describing a planned feature does not enable it.

Games and device storage

We use the chess username you enter to fetch public games from Chess.com or Lichess. Pasted PGNs may also contain player names. Results, recent accounts, settings and practice progress are stored in your browser or app. Do not submit chess passwords or unnecessary private information.

Remote analysis: current status

Public versions primarily use local analysis. Remote analysis is in private testing and is not connected to the public app. Before offering a remote mode, we will explain uploads such as games or positions, job identifiers and authentication data used to analyze games, return results and prevent abuse. Retention and providers will be updated when the feature launches.

Usage and crash reports

The website uses Google Analytics or Google Tag Manager when configured. The app uses a random installation ID to record screen views, time on screens, foreground usage, analysis actions, ad impressions/clicks/dismissals, device model, operating system and app version. Events go to Cloudflare; Firebase Crashlytics handles crash reports. Versions that enable Firebase Analytics send only behavior events and a random ID. You can stop future analytics and diagnostics in Usage & Privacy. We do not read activity in other apps, messages or phone contents.

Chess-account linking is off by default. If you enable Share the chess accounts I entered, connected Chess.com/Lichess handles are associated with this installation’s events in Rookie Lab’s private Cloudflare database for product analysis and support. Raw handles are not sent to Firebase Analytics or ad services, and do not verify account ownership. Turning the option off or removing an account requests deletion of the association. Offline changes retry when connected; settings show sync status. Account associations not updated for over 90 days are cleaned during later account-data writes, not by a fixed schedule. Disabling analytics does not erase earlier events. Use feedback for other access or deletion requests.

Feedback and security

Feedback records include your message, optional email, page, language, version and device information. An IP hash limits abuse. Optional diagnostics attach masked recent actions and errors that you can review before sending. Cloudflare provides storage and delivery; necessary feedback details may be sent to the maintainer through notification services.

Purchases and subscriptions

Apple processes iOS in-app payments. The app reads products, verified transactions, subscription expiry and revocation status to provide access, and may record purchase events such as product identifiers. We do not receive full card details. Any future payment methods will identify their processors and data uses at checkout and in this policy.

Advertising and choices

Production app ads are not enabled yet. Before enabling them, we will update providers, data types and applicable privacy choices. Consent or tracking permission will be requested where required before processing; this page is not a consent dialog. Rewarded ads, if enabled, will process reward events and transaction identifiers to verify one-time access.

Retention, deletion and international processing

You can remove local data by clearing website data or using app controls. Removing the app does not cancel a subscription. Server feedback and diagnostics are retained for support, security and applicable legal needs; no unimplemented automatic deletion deadline is promised. Providers may process data outside your country. Use Feedback to request access, correction or deletion; we will verify identifiable records and handle requests under applicable rules.

Contact and changes

Contact the Rookie Lab maintainer through Feedback. Include a way to reply to data requests, but no passwords or full payment card details. Material data-handling changes will update this date and include necessary notices before use of the relevant feature.