Learn how Read19 handles account, game, cloud analysis, payment, security, and performance data, and the choices available to you.
Read19 processes data required to provide accounts, Go review, cloud KataGo analysis, subscriptions, security, and service performance. Registration and sign-in involve an email address, display name, password hash, account identifier, sessions, and hashes of analysis keys. Analysis records include rules, board size, search amount, model, GPU, queue and execution timing, errors, and limited client metadata. Complete analysis requests and results are not retained as task logs, while games and compact review data that a user saves to the cloud library follow the cloud-library rules.
The Web client stores preferences, a random installation identifier, and necessary browser credentials locally. Cloud games use unguessable share identifiers, and anyone who receives a public link can view its published game content. Community topics and replies are public by default. Cloudflare provides edge, Worker, D1, R2, email, and performance services; configured GPU providers execute KataGo searches; Apple and Creem process purchases in their respective channels. Each provider receives data only as needed for its function and applies its own logging and retention practices.
A user can delete individual cloud games or permanently delete the account. Account deletion removes the account, sessions, analysis keys, cloud games, analysis jobs, and most account records. Minimal irreversible identifiers or transaction-notification records may remain when necessary for a still-active subscription, refund, dispute, duplicate-credit prevention, legal obligation, or continuing security block. Send privacy requests to support@read19.com with only the information needed to locate the request; never send a password, complete API token, card number, or Apple purchase receipt.