SUPPORT AND CONTACT
Contact Read19
For help with an account, Go review, the KataGo API, a client, subscription, or payment delivery, email support@read19.com. Email is the official public support channel for Read19.
Describe what happened
Include the platform and version, approximate time, page or feature, reproducible steps, and the complete error text shown by the interface. For a game-specific issue, attach an SGF only after checking its private content, or provide a public Read19 share link. Do not send a game record containing another person's private information unless you are allowed to share it.
For an account issue, state the login email only. Never send a password, session, Passkey data, or complete API token. For an analysis connection issue, include the client name, network environment, request time, and a screenshot with the key fully redacted. Read19 support will not ask you to install remote-control software or pay a personal account by email.
Payments, subscriptions, and refunds
For an Apple subscription, first check the system subscription settings and try Restore Purchases. For a Creem Web subscription or permanent analysis units, include the order or transaction identifier, purchase channel, and approximate time. Never send a complete card number, security code, bank login, or complete Apple purchase receipt. Read19 can inspect signed server notifications and the delivery ledger and can assist the payment channel when an investigation is required.
Cancel automatic renewal in the channel where the subscription was purchased: App Store manages Apple purchases, while the Read19 account console links to Creem subscription management for Web purchases. Deleting a Read19 account does not cancel a subscription that remains active with its payment channel. Permanent analysis units are separate one-time digital content and do not renew.
Response boundaries
Read19 has no public telephone support, live chat, or walk-in office. Ordinary requests sent to support@read19.com are handled in received order; check the public status page first for an active service incident. The public community is appropriate for Go, game records, and product workflows, but not for login emails, order identifiers, credentials, or other sensitive account information.
If a credential may be exposed, first revoke the analysis key, sign out unfamiliar sessions, and change the password, then describe the actions already taken. If you cannot sign in, send only the login email, approximate time, and error information that is safe to disclose. Access recovery continues through the existing account-verification flow.