Operator and requests
BlackJacker is operated by Մադոյան ՍՊԸ / Madoyan LLC, Armenia. Contact support or request access to, correction of or deletion of data at nersesmec@gmail.com. Ordinary users do not need to create an app account. Service reviewer sign-in is described separately below.
Training data
History, answers, mistakes, statistics, manual sessions and settings, including language, theme and audio, are stored on the device. The purchase verification service does not accept these training files. Free exercises work offline; when online, the app also checks Pro availability, including in Free. Resetting statistics does not mean that all local backup copies or exports are erased. Built-in music and effects are not recordings of your voice.
Android backups and training file transfer
The Android build configuration disables automatic cloud backup and device transfer. It does not erase older copies; OS and manufacturer behaviour can vary. For a voluntary export or import through Android's system file picker (SAF), you choose the storage provider, which may be a cloud service. The training JSON excludes purchase tokens and service reviewer sessions and does not transfer Pro entitlement. Its checksum checks integrity; it does not encrypt the file. Retention and deletion of exports depend on you and the selected provider.
Purchases and identifiers
For purchase verification, restoration and rechecking cached access, the app sends our server a purchaseToken, random installationId and single-use nonce. They support Pro access, restoration and protection against replay and revoked purchases. The server stores an AES-256-GCM encrypted token, its hash, purchase state, acknowledgement and update time; an ID/nonce pair hash prevents replay. These data are pseudonymous, not anonymous. The token and signed entitlement are also cached on the device. An offline entitlement of up to 72 hours is not a purchase retention period.
Recipients and network
Google Play processes payment; our verification server does not receive card numbers. It sends the token to Google Play API for verification, acknowledgement and revocation checks, and receives purchase state and transaction region. If RTDN notifications are enabled, purchase messages arrive through Google Cloud Pub/Sub. Hosting and network providers participate in operating the service. Connections expose IP addresses, which the server uses in memory between requests for rate limiting. Our application logs contain time, route, method, status and duration for diagnostics and security, without IP, request bodies, passwords or tokens. Infrastructure providers may keep separate logs.
Reviewer access
If you are given service reviewer access, sign-in sends the service identifier, password, installation ID and nonce. This is a separate access method, not a Pro purchase or ordinary player registration. The password is sent over HTTPS at sign-in and is not persisted by the client; the server stores a salted password hash. Later requests use a random refresh token; the server stores its hash, installation ID, credential version and expiry. Sessions are limited to 24 hours without extension on refresh; signed entitlements and nonces are limited to 1 hour. Signing out or revoking a session does not instantly end an already issued offline entitlement.
Retention rules
Active purchases are retained while needed to restore Pro. After the first revocation, our retention rules allow an encrypted token for up to 30 days and a minimal antifraud hash/record for up to 180 days. The limits are up to 7 days for our service logs, 30 days for managed backups, 12 months for closed support cases, and acceptance plus 30 days for local QA copies. These periods do not set retention for Google's independent records or your exports with an external provider. The ID/nonce replay-control hash has a validity period of 72 hours; this does not mean the record is erased instantly.
Deletion and backups
Send a request to nersesmec@gmail.com. The response period is up to 30 days, not a universal deadline for deleting every copy. Support will arrange an appropriate verification of your authority and the data scope, including managed backups. Do not send passwords, raw purchase tokens, installation IDs or payment details. For an active purchase, deleting access evidence can affect restoration of Pro; any retained antifraud minimum is explained separately. Uninstalling does not delete server records, Google data or exports you saved independently. You and the relevant provider also control local data and external copies.
SDKs and data protection
Purchases use Unity IAP and Google Play components. Optional Unity Analytics, crash diagnostics and performance reporting are disabled in the build configuration; store and access verification connections are separate from local training. Our Pro verification and service sign-in requests are configured to use HTTPS. The server can decrypt the purchase token; this is not end-to-end encryption. The app does not add separate encryption to local JSON files.
Website and voluntary support
The website stores the selected theme in browser localStorage; its code has no submission forms, external fonts or analytics scripts. Page visits expose IP addresses to website infrastructure. When you voluntarily email us, we and the email provider receive your sender address, message and submitted attachments to respond to your request. The email link opens an external application. Google Play, email services and file services you select also process data under the terms of the relevant service.
Text revised: 26 October 2026.