01Purchases and account wallet in TikTok version 0.5.7
Version 0.5.7 enables optional purchases using TikTok Beans. Versions 0.5.3 through 0.5.6 retained the earlier login, ads and measurement features without enabling purchases. In 0.5.7, the game obtains a fresh TikTok login code to establish a short-lived payment session. Our server temporarily stores encrypted platform authorization tokens, a hashed session token, expiry information and the game-specific player identity. The game holds the payment session token in memory.
Our Cloudflare D1 database records product identifiers, Beans amounts, order and trade identifiers, payment and refund states, verification events, and the account wallet containing bamboo leaves, paid hints and the remove-ads entitlement. These records support verified delivery, purchase restoration, duplicate prevention, disputes and support. They are retained for those purposes and are not automatically deleted when you clear local game storage. Contact july@lineargame.ai for data requests; we review requests against records needed for outstanding transactions and disputes. We do not receive payment-card details from TikTok.
Limited IAP measurement events sent to TikTok and Tencent CLS include shop/product views, purchase attempts, controlled outcomes, product identifiers, displayed Beans amounts, environment, language, duration and random correlation identifiers. Analytics are not proof of payment. They do not contain platform access tokens, login codes, OpenID or payment-session tokens. Paid account balances can be restored with the same verified TikTok account; puzzle progress remains local. An already downloaded, consumed hint may be lost if local storage is cleared before use.
02Who is responsible and which version applies
LinearGame Pte. Ltd. (the “PandaDoku team”, “we”, or “us”) provides PandaDoku. Contact us about privacy or support at july@lineargame.ai.
This notice covers PandaDoku on TikTok, this policy website, and our game login service. Version 0.1.1, the previously submitted build, has local gameplay and settings, with no game-integrated ads or remote gameplay event reporting. Version 0.2.0 introduces optional rewarded videos for hints and gameplay event reporting through TikTok’s official SDK. Version 0.3.0 adds TikTok silent login, a server-side identity record, and optional home-screen and sidebar tasks that unlock local leaf decorations. Versions 0.4.0 and 0.5.0 retain the earlier login, rewarded-hint and gameplay-measurement features. Version 0.5.0 updates gameplay presentation and adds a local challenge leaderboard based on personal-best scores and local challenge rivals; it does not add a global player leaderboard. Version 0.5.1 retains these features and introduces interstitial ads at selected level transitions and a separate gameplay-measurement channel using Tencent Cloud Log Service (CLS). Version 0.5.2 adds Brazilian Portuguese and improves Arabic right-to-left (RTL) layout. It retains the features and data-handling behavior described for version 0.5.1. Versions 0.4.0 and 0.5.0 do not include these interstitial ads or CLS measurement. Features apply only when you use a build that includes them; this notice does not announce that a particular version is publicly available.
03Game progress, activity dates, and event identifiers
The game stores unlocked and completed levels, best completion times and scores, the last selected level, tutorial status, and preferences such as music, sound, and reduced motion. Versions 0.2.0 through 0.5.2 also store earned hint credits, recent reward-request identifiers to prevent duplicate credits, and the first and most recent active dates used to recognize return visits. Versions 0.3.0 through 0.5.2 store whether the Golden Leaf and Jade Leaf decorations have been collected; these local ownership flags prevent repeated grants in the same local save. Storage uses the TikTok mini-game container so your progress and choices can be remembered.
For event reporting, the game creates random session and level-attempt identifiers in memory, with identifiers for individual events. These relate actions during play and distinguish repeated events. Versions 0.2.0 through 0.5.0 do not create a persistent installation identifier. Activity dates and times use UTC. These values are not your TikTok username or email, although TikTok may relate reported events to information it holds under its own policies. Versions 0.3.0 through 0.5.2 also use the separate player identity described below.
Versions 0.5.1 and 0.5.2 additionally create a random local identifier for CLS measurement, scoped to this game and the configured log topic. It is stored in the mini-game container and can relate this game’s activity from the same local storage across sessions until that storage is cleared or lost. It is not derived from OpenID, your login identity, a hardware identifier, username or email, and is not used to restore game progress. Although it is not a direct account identifier, its ability to link events means the resulting records should not be treated as completely anonymous.
We do not operate a cloud save or cross-device progress backup for these versions. The game does not upload a copy of your save to our server. Versions 0.2.0 through 0.5.2 send event details to TikTok, and versions 0.5.1 and 0.5.2 also send the limited event details described below to CLS. Progress, settings, hint credits, reward records, activity dates, and leaf decorations remain device-local. Clearing app or mini-game data, changing devices, or losing container storage can remove them. The server identity record and measurement events are not backups of these items.
04TikTok silent login and your game identity in versions 0.3.0 through 0.5.2
PandaDoku uses TikTok silent login to verify your TikTok game identity. The game sends a temporary login code over HTTPS to our login service on this website’s domain. Our server exchanges that code with TikTok and temporarily processes the returned OpenID and platform tokens. OpenID is TikTok’s identifier for you within this game. We store an encrypted copy of OpenID together with a stable, game-specific pseudonymous player identifier so we can recognize the same verified identity on later logins. This information is not anonymous, even though we do not request your TikTok display name or avatar.
The identity record is stored in Cloudflare D1 through our Sites hosting service. OpenID is encrypted before it is written to the database; encryption and identity-generation secrets stay on the server. Our login application does not write raw login codes or TikTok access or refresh tokens to its database or application logs. It returns only the game-specific player identifier and login result to the game. The game keeps this identifier in memory for the current run and does not add it, OpenID, login codes, or platform tokens to gameplay analytics or local game saves.
To prevent repeated or abusive login requests, the database also holds login-code hashes and expiry times, keyed hashes of source IP addresses with request counters and time windows, and service-configuration verification records. The login application uses the IP address to derive the rate-limit hash; it does not store the raw address in these database records. Hashes and pseudonymous identifiers may still be personal information. Verifying your identity does not upload or restore game progress, hint credits, or decorations.
05Rewarded videos and gameplay measurement in versions 0.2.0 through 0.5.2
You can choose to watch a TikTok rewarded video to receive the hint reward shown in the game. TikTok supplies and operates the ad. We receive SDK callbacks about loading where supported, errors, and whether viewing finished, so we can handle the request and grant a reward after completion.
The game reports events to TikTok through its official event-reporting API. Event details include the runtime event identifiers and activity dates described above; game and event-schema versions; session and UTC activity times; tutorial and settings actions; level number, difficulty, attempt, actions, duration, mistakes, completion or failure; hint use and credit changes; and ad placement, request, loading where supported, cancellation, error and reward outcomes. Where available, a limited launch-scene code and the fixed game-entry path help distinguish entry contexts. Our game event reporter does not read or send raw launch queries or referrer details. In versions 0.5.0 through 0.5.2, events also describe tutorial steps, local challenge ranking views and continuation actions. These rankings compare personal-best scores with local challenge rivals, not players on a global leaderboard.
Versions 0.3.0 through 0.5.2 additionally report login attempts and results, home-screen and sidebar task requests and results, and decoration grants or storage failures. These events use random request identifiers, controlled status or error categories, and timing information. They do not contain the player identifier, OpenID, login codes, or platform tokens.
We use this information to understand tutorials and level progression, diagnose failed requests, measure return visits, and evaluate player acquisition and advertising performance. TikTok receives and processes the reported events for platform analytics and advertising optimization. Actual ad impressions, ad revenue, campaign cost, and return on advertising spend come from TikTok’s platform reports; requesting an ad in the game does not itself confirm an impression or revenue. Platform reporting is available only after TikTok enables the relevant features for a live game.
06Interstitial ads and Tencent Cloud CLS measurement in versions 0.5.1 and 0.5.2
Versions 0.5.1 and 0.5.2 may request a TikTok interstitial ad when you select the next level after certain completed levels. These ads are separate from optional rewarded videos and do not grant hint credits. We record controlled request, loading, closing, error and timing states to diagnose this flow. An ad request or a client show request is not proof of an actual impression, completed viewing, or advertising revenue.
The game also sends a limited copy of gameplay events over HTTPS to Tencent Cloud Log Service (CLS) for product analysis and diagnostics. The configured collection endpoint is in Tencent Cloud’s Guangzhou region in China. Configured test and production log topics separate the corresponding measurement streams; each record includes the game identifier to distinguish PandaDoku records. Event fields are restricted to an allowlist: game identifier and version, runtime environment, event name and identifier, session and attempt identifiers, event time, the separate random local CLS identifier described above, and supported gameplay, level, score, ad-status and duration fields. We use these records to understand progression and scoring, identify failed interactions, and improve the game. They are not purchase receipts or a replacement for TikTok’s actual impression or revenue reports.
The CLS game payload does not include the login player identifier, OpenID, login codes, platform access tokens, account names, email addresses, raw launch queries or referrer data. This restriction on payload fields does not mean the network request is anonymous: Tencent Cloud and network or hosting providers may receive and process IP addresses, request timing, headers and other technical metadata to deliver and secure the service. We do not describe these records as completely anonymous or as unrelatable to a device’s activity.
For temporary delivery failures, versions 0.5.1 and 0.5.2 can save a retry queue in local mini-game storage. The queue holds at most 500 pending events, including their event details and identifiers. Queued records older than 72 hours are discarded when the game next processes the queue; capacity limits can remove older pending records sooner. These are client-side retry limits, not a cloud retention period. Uploaded records are subject to the separately configured CLS log-topic retention and service controls; the 72-hour local limit does not promise deletion from Tencent Cloud after 72 hours. Clearing local storage removes the local identifier and pending queue but does not delete previously uploaded CLS records. Contact july@lineargame.ai for questions or requests concerning CLS records we control.
07TikTok platform information
PandaDoku initializes the official TikTok SDK and responds to the game entering the foreground or background. TikTok may process account, device, network, usage, advertising, and diagnostic information to operate and secure its platform and provide its login, advertising, and measurement services.
These versions do not request your TikTok profile, username, avatar, email address, contacts, precise location, camera, or microphone through game code. Versions 0.1.1 and 0.2.0 have no game login integration; versions 0.3.0 through 0.5.2 use silent login as described above, without creating a separate PandaDoku password. These versions have no in-app purchase integration. This does not mean TikTok itself processes no personal information.
Read TikTok’s Privacy Policy, or open the policy and privacy controls provided in your TikTok app for your region. TikTok’s platform processing and retention are governed by its applicable notices.
08When you contact us
If you email july@lineargame.ai, we receive your email address and the information you choose to send, such as a description of a problem or a screenshot. We use it to answer you, investigate issues, handle privacy requests, and maintain support records. Please do not send passwords, payment card details, identity documents, or unrelated sensitive information.
09This website, recipients, and international processing
The policy pages contain policy text and support links. We have not added advertising trackers, analytics scripts, contact forms, or non-essential cookies to these pages. The same domain also provides the login service introduced in version 0.3.0. Our Sites and Cloudflare service providers process that service and its encrypted identity storage on our behalf. Hosting and infrastructure providers may process IP addresses, request details, security signals, and other technical metadata to deliver, protect, and operate the website and service.
TikTok receives events from versions 0.2.0 through 0.5.2 and handles rewarded and interstitial advertising, login exchanges, and platform tasks as described above. Tencent Cloud provides the separate CLS measurement service described above for versions 0.5.1 and 0.5.2, using its configured Guangzhou-region endpoint. This may involve processing in China even when you play elsewhere. Our hosting and email service providers may process service, website, and support information on our behalf, and their infrastructure and processing may be in countries other than yours. We may disclose information to providers who help operate or secure the service, or where required by law or necessary to protect legal rights. We do not sell information received through support emails. For questions about recipients or safeguards applicable to information we handle, contact us at the address on this page.
10Why we use information and how long we keep it
We use local game storage and reward state to provide the gameplay and choices you request, and the identity record introduced in version 0.3.0 to verify and recognize your game identity. Login security records help prevent duplicate and abusive requests. We use support information to respond to requests and resolve issues. Gameplay measurement helps us improve the game, maintain reliable reward flows, and assess player acquisition. Where applicable data protection law requires a legal basis, providing the requested service, our legitimate interests in supporting, improving and securing the game and measuring its performance, or a legal obligation may apply, subject to your rights and local requirements. TikTok describes its own processing and applicable choices in its regional policies.
We retain the server identity record for as long as needed to recognize your game identity and support the service. You may request deletion by emailing july@lineargame.ai. After verifying a request, we delete information when it is no longer needed or when deletion is required, subject to applicable legal obligations and any lawful need to retain information. Login-code hashes have expiry times and rate-limit records use short time windows. Expired security records are removed during request-triggered cleanup; they may remain until cleanup runs. Service-configuration verification records remain while needed to operate the identity store.
Local progress, hint credits, recent reward records, activity dates, and decorations remain subject to TikTok container and device storage settings. Runtime session, attempt, event, and player identifiers are created or held in memory; versions 0.5.1 and 0.5.2 also persist the separate CLS identifier and temporary event retry queue as described above. Reported event copies are handled by TikTok and, in versions 0.5.1 and 0.5.2, Tencent Cloud CLS. We do not maintain a separate cloud copy of your save. Clearing local storage does not itself delete the server identity record or information already transmitted to TikTok or CLS. TikTok events are subject to its platform retention and request processes. Support information is retained only as long as needed to resolve the request and related issues, meet legal obligations, or establish, exercise or defend legal claims. We assess retention using the issue, whether follow-up is needed, and applicable legal requirements.
11Your choices and privacy rights
You can change music, sound, and reduced-motion settings, and you can decline rewarded-video offers and optional return-visit tasks. Declining these offers does not disable event reporting in versions 0.2.0 through 0.5.2 or silent login in versions 0.3.0 through 0.5.2. These versions do not include a dedicated “delete all progress” button, an in-game identity-deletion control, or a control for deleting events already reported to TikTok or CLS. For local-storage help or requests about our server identity record or CLS measurement records, email july@lineargame.ai; for information held by TikTok, use its privacy settings and request channels.
Depending on your location, you may have rights to access, correct, delete, restrict processing of, or receive a copy of personal information we hold. You may also have the right to object to processing based on legitimate interests. Where processing relies on consent, you may withdraw that consent. You may complain to the relevant data protection authority.
To make a request, email us with “PandaDoku privacy request” in the subject. We will take reasonable steps to verify it and respond within applicable legal time limits. You do not need to create a separate PandaDoku account to make a privacy request.
12Children and young players
PandaDoku on TikTok is available only to users who meet TikTok’s applicable age and regional eligibility requirements. We do not knowingly request personal information from children below the applicable minimum age. If you believe such information was sent to us, contact july@lineargame.ai so we can investigate and take appropriate action.
13Security and policy changes
We use reasonable measures appropriate to the information we handle, but no storage or transmission method is completely secure. We will update this page when our practices change and identify material new features and data uses. The date and version scope on this page identify which notice applies.
Privacy and support contact: july@lineargame.ai.