zonChess ยท ChessZCam Android

ChessZCam Android Privacy Policy

Last updated: 2 November 2026 · version 2026-11-02.1

ChessZCam helps record, review and share physical chess games. Core board detection and game processing run on your device. Online activation, Google Play purchase verification, automatic Google Play Billing diagnostics, optional feedback, content reports and sharing workflows can send data outside the device. Billing diagnostics can be sent to Google even when you do not make a purchase.

Viewer Mode is free. Using Viewer does not require starting the licensed-feature trial. You choose whether to start a trial, purchase a licence, submit feedback or publish a game.

1. Scope and contact

This policy describes ChessZCam for Android and its trial, licensing, purchase-verification, automatic Google Play Billing diagnostics, optional app-feedback and content-reporting services. Google Play publisher: Produksi Zonkita. Developed and operated by Motivace Studio under the zonChess product brand. For questions or a data request, email admin@zonchess.com.

The app's licensing flow does not create a zonChess user account. Google Play purchases use your Google account. A publishing service you choose may have its own account and privacy terms.

2. Data at a glance

WorkflowData involvedWhere it is used
Record, detect, analyse and exportCamera frames, recordings, optional microphone audio, board positions, moves, project files and exportsOn your device for the selected workflow. Sharing or exporting to another app is a separate action.
Trial and licensingDevice activation identifier, platform, nonce, activation times, licence rights, coarse country context when available, and hashed network-address information for abuse controlsSent to the zonChess licensing service for rights and trial/device limits.
Google Play purchasesProduct identifier, purchase token, device activation identifier and verification request contextSent to zonChess and verified with Google Play. The entitlement table stores a token hash, licence/product association, timestamps and revocation status.
Google Play Billing diagnostics (automatic)App/package and version; Android OS, device model/manufacturer and non-unique OS build information; language/region, network type and available carrier context; Billing API, error/result and checkout launch/result events; transient client or checkout correlation identifiersThe Billing library can send technical events over HTTPS to Google's logging service when it connects or is used, including at startup/resume without a purchase. Events may be queued locally before transmission. Used for technical reliability and diagnostic analytics.
Local Viewer and broadcastPositions, moves, optional player names/board labels, connection information and a requested board photo where supportedThe source, companion or viewers on the network you configure.
Optional Live PGN publishingPGN, move timeline and game metadata that may include player names, event, site, round and resultThe zonChess, Lichess or HTTPS endpoint you select.
Feedback and supportRating/topics, optional text, app/build, device summary, language, licence status, screen/workflow context and server-side hashed IP for rate limitingSubmitted feedback; support routes also receive contact details or attachments you choose to provide.
Safety reports and local blocksReport ID, source fingerprint and kind, selected reason, explanation, app and terms version, optional contact email, and salted network-address hashes for request limits. Local consent, blocks and pending reports are stored on your device.Only reports you submit, or previously queued reports being retried, are sent by HTTPS to zonChess. No automatic board-photo, recording, licence-ID or purchase-token attachment is made.

3. Camera, audio and local work

The camera supports game recording, board detection and board-photo comparison. Microphone access is used when you choose to record audio with video. Permissions are handled through Android. You can change them in Android settings; denying a permission may prevent the relevant feature from working.

Game videos, detected positions, saved projects, analysis and exports are handled locally for the core recording and review workflow. A licence-verification request does not contain camera footage. When you share an export, send an attachment for support or use a sharing feature, the selected recipient or app receives the material you choose.

You control local recordings and exports through the available file/project controls and Android's file or media tools. Files exported to shared storage, another app or a backup location may remain there after ChessZCam is removed.

4. Activation identifiers and country context

To associate a trial or paid licence with a phone, ChessZCam derives an activation identifier from Android's app-scoped identifier. The value sent is a hash-derived identifier, rather than the original Android identifier. If it is unavailable, the app can use an app-generated identifier. Hashing does not make this information unrelated to the device.

The licensing service receives the activation identifier, platform and a random request nonce, and records the licence/device binding and activation/request timestamps. These support entitlement checks, device limits, restoration and trial-abuse prevention. The identifier may remain consistent across reinstalling the same signed app on the same Android user/device; changes to signing, user or device configuration can affect it.

You may choose a country during activation. If none is selected, the service may estimate a country from trusted server-side network metadata or a local GeoIP source, when available. This is country-level context, not GPS or precise location. Connection IP addresses are processed by the service; its application database uses salted hashes for trial and request-rate abuse controls. Hosting infrastructure may also process connection information in operational logs.

5. Google Play payments and entitlement verification

Google Play handles checkout and payment details for the Play version. ChessZCam does not receive your payment-card number or card security code. The app receives purchase information from Google Play and sends the product identifier, purchase token and activation request to the zonChess entitlement service over HTTPS.

The service checks the purchase with the Google Play Developer API before issuing a signed licence. The purchase token is processed for verification; the entitlement table stores its SHA-256 hash, associated licence, product identifier, purchase/verification timestamps and revocation status. Licence-device bindings and security/audit records are kept separately. Google processes purchase and account information under its own privacy policy.

Restoring or re-verifying contacts these services again. Refund or revocation handling may change the entitlement. See the ChessZCam Google Play terms for the commercial offer.

Automatic Google Play Billing diagnostics

The Google Play version includes Google Play Billing Library 9.1.0. In addition to checkout and purchase verification, the library automatically records technical events when the Billing client connects or runs API operations. This can happen when ChessZCam starts or resumes, even if you do not buy a licence. Choosing not to purchase, or declining optional feedback, does not by itself stop this automatic SDK activity.

These events can include the app/package identifier and version, Android OS version, device model and manufacturer, non-unique OS build information, language and region settings, network type and available mobile-network/carrier context. They can also include Billing API calls, response/error results, checkout launch and result activity, and transient identifiers that correlate a Billing client or checkout session.

The library can queue technical events locally and transmit them over HTTPS to Google's logging service. Google receives these diagnostics separately from the purchase-verification requests handled by the zonChess licence server. The purpose is technical analytics: monitoring Billing reliability and performance and diagnosing API or checkout failures.

Google's handling and retention of the information it receives are governed by its applicable terms and Google Privacy Policy. We do not set a fixed retention period for Google's diagnostic logs. The library's local queue and Google's records are separate from the zonChess licence, feedback and safety-report databases described below.

6. Local Viewer and broadcast sharing

Viewer follows a source board on the same Wi-Fi, hotspot or configured local network. Shared information can include confirmed positions/moves, a diagram of the board currently observed by the camera, optional player names and a board label. A viewer can request a board photo for comparison where the source supports it. Camera video stays on the source device in this Viewer workflow.

A local-network link or QR code can let its recipient access the shared board. Use the sharing controls to manage the session or replace the QR/link. Recipients may keep copies of received information; stopping sharing does not remove those copies.

Some local connections use HTTP or WebSocket without transport encryption supplied by ChessZCam. Use a network you trust and consider who can join it. Local Viewer does not by itself provide remote internet viewing. A PC broadcast companion or internet publishing service is a separate workflow with its own recipients.

7. Optional Live PGN publishing

When you configure and start Live PGN publishing, the app sends the PGN and timeline to the selected zonChess receiver, Lichess Broadcast or custom HTTPS endpoint. The destination may receive player names, event details and result. A configured access token authorises the publishing request.

Visibility and retention depend on the destination and operator. A published game may be public. Choose the destination and metadata carefully and obtain the permissions needed to publish them. To remove a published copy, use the destination's controls or contact its operator; deleting the local project does not delete a remote copy.

8. Feedback, support and clipboard controls

Quick feedback is optional. Tapping a rating sends it with app/device context; optional topics and short text may follow as another record linked by a random prompt identifier. Context includes app/build, platform, device/OS summary, language, licence status, screen size and where the question appeared. The server uses hashed IP information for rate limiting. Feedback may be forwarded to the developer through configured email or Telegram notifications for support and product improvement.

Offline, unsent quick feedback can be queued locally and retried when online. The queue is capped at 20 records; records older than 14 days are discarded when it is processed. This queue limit is separate from retention of feedback already received by the server or support channels.

Support email and website-form actions open the selected service with app/device details you can inspect or edit. Information is sent through that route when you submit it. Messages, contact details, diagnostic material or attachments you include are handled for that request.

When you choose a Paste control, the app can read clipboard text to fill the relevant field, such as a Viewer link. It does not need payment-card details. Pasted information is used by the action you subsequently choose; avoid including unrelated private information in a field or support message.

9. Content reports and source controls

Play app version 1.28.2 and later includes Safety controls for remote board content. Accepting shared-content rules stores their version locally. The Block this source control stores source fingerprints on this device so a blocked source can stay hidden after a restart. You can unblock entries through Blocked sources. These records do not create a social account or a verified friends list.

New Android hosts expose a random, app-generated publisher identifier in Viewer data to support source blocking across sessions. It is separate from the licence activation identifier. For older sources without that identifier, the app derives a fingerprint from the source address. A fingerprint can link reports about the same source; hashing does not make it unrelated to that source.

When you submit Report content or source, the app sends a random report ID, a source fingerprint and source kind, your selected reason and explanation, the app and accepted-terms version, and an email address only if you enter one. Report text may contain personal information you choose to type. Include only what is needed. The report workflow does not automatically attach a board photo, camera recording, raw Viewer URL, publishing credential, licence activation ID or purchase token. Recognisable credentials and network addresses in free text are redacted before storage in the reporting database; do not rely on redaction to remove every piece of sensitive information.

The zonChess reporting endpoint receives the connection information needed to handle the request. Its rate-limit records use a salted network-address hash rather than the raw address and are cleared after their short abuse-control window. Hosting infrastructure may separately maintain operational logs. Reports and case notes are stored in the operator's private database on its hosting service and are available to authorised moderation staff through a password-protected inbox. They are not published as a public report feed or automatically sent to other app users.

A successful server receipt means the report was stored for review, not that the allegation was proven or all copies removed. Unsent reports can be held in a local queue of up to 20 entries and retried when the app is open and online. Entries older than 14 days are not retried. A Queued message is distinct from a received report. You can clear pending reports using Clear queued reports.

Open reports are kept while they are investigated. Closed report records and their associated case notes are scheduled for deletion 90 days after closure using the reporting service's cleanup job. Reopening a case resumes investigation and clears its closure date. This schedule applies to the report database; other licensing records, independent hosting logs, third-party copies and backup retention are covered by their own purposes and processes. You may also request access, correction or deletion using the contact below, providing the report ID where available.

10. Purposes and recipients

Data received by zonChess services is used to provide/restore licensed features, enforce trial/device limits, verify purchases, prevent abuse, answer support and improve the product from submitted feedback. Hosting, database, email and configured support-notification providers process information needed for these services. Google Play and a publishing destination you select also process information for their services.

Google also receives the automatic Billing SDK technical diagnostics described in section 5 for Billing reliability, performance monitoring and troubleshooting. This collection is not limited to information sent to zonChess.

We do not sell or rent personal information. Game data is shared through the recording, export, local sharing or publishing workflow you choose. Service providers and recipients may process data in locations different from yours.

11. Retention and data requests

Local projects and media remain under your control unless you send or share them. Removing the app does not request deletion of server-side activation, purchase, feedback or support records, or remove exported/published copies.

Activation and purchase records support continuing licence use, restoration, device limits and trial-abuse prevention. Support and feedback records support responding to issues and maintaining the product. Records may also need to be retained for security, dispute resolution or applicable record-keeping obligations. Retention is assessed against those purposes rather than the app's installation period.

Google manages information it receives through its own services, including Billing SDK diagnostic logs, under its applicable terms and privacy controls. A request to zonChess does not automatically delete Google's independent records. Use the Google Privacy Policy to find Google's data controls and request options.

Request access, correction or deletion

Email admin@zonchess.com with the subject ChessZCam data request. Describe the data and action requested and enough context to locate the activation, purchase, game publication or support message. We may request reasonable information to verify the request.

Requests are handled through support. Some records may need to be kept to maintain an entitlement, prevent repeated trial abuse, resolve a dispute or meet an applicable obligation; any applicable limit to a request will be explained. Do not send card details, passwords or a raw purchase token. For an independent publishing service's copy, also contact that service.

12. Your choices and people in recordings

You can use free Viewer without starting the trial, decline feedback, choose whether to publish/share and manage Android camera/microphone permissions. Disabling a permission or network connection can limit the feature that needs it.

Respect players' and spectators' privacy, including children's, and follow venue rules. Obtain the permissions needed to record/publish identifiable people and player metadata. A parent or guardian can contact us about a child's information received through a ChessZCam service.

13. Security and changes

Licensing, Play purchase verification, feedback submission and supported internet publishing endpoints use HTTPS. Local sharing has the separate limitations above. Keep your device, sharing links and publishing credentials under appropriate control.

This page may be updated when data practices change. The date above identifies this version. Contact admin@zonchess.com for clarification.