Your discoveries. Your choices.
How Z Puzzle Lab: Logic Games handles progress, optional account linking, advertising and purchases.
Who we are
Z Puzzle Lab: Logic Games is published by Zyntra Apps. Contact [email protected] for privacy questions or requests about this game. This notice covers Puzzle Lab and its associated online services.
Your progress and cloud account
The game creates a generated player ID and installation credentials. Our dedicated Puzzle Lab database stores authenticated sessions, allocated and completed puzzles, assistance use, mastery and task progress. Puzzle moves are processed to validate solutions and prevent duplicate rewards; this does not mean every submitted move sequence is retained in full. Preferences sent to the server include theme and whether you tapped the review control. Tapping that control does not tell us whether you submitted a Google Play or App Store review.
Our game service is hosted on OVH infrastructure in Canada and connects through HTTPS. Local storage holds puzzle state, undo history, preferences and pending requests. Cloud credentials use Android device-bound encrypted storage or the iOS Keychain, depending on the platform. Uninstalling the app does not delete the cloud account.
Optional Google linking
Google linking is optional. You can play as a guest and choose to link your progress for recovery. When you choose to link, Google authenticates your account and sends a signed identity proof. Our server verifies it and stores a hash derived from Google's stable account identifier to associate your progress. We do not store your Google password, identity token, profile photo, name or email in that identity table. The sign-in chooser can display Google account details on your device.
Being signed into the Play Store does not automatically link game progress. Linking and account restoration are separate actions; the app asks before replacing a guest session with linked progress. Google operates its own account services under Google's Privacy Policy.
Optional Play Games
Google Play Games can authenticate your game profile and receive achievement progress. It is separate from linking your Puzzle Lab cloud account. Google processes game activity, profile identifiers, device information and diagnostics under its own privacy policy. We do not request your friends list or other games' data. You can manage or delete Play Games data through your Google Play Games profile.
Sign in with Apple on iPhone and iPad
On Apple devices, linking with Apple is optional. Apple authenticates your account and supplies an identity proof and authorization code. Our service verifies these with Apple and stores a hash of the Apple account identifier for progress recovery. We do not request or store your Apple password, name or email for this link. Authorization codes and identity proofs are processed for verification and are not retained in the progress database or ordinary logs.
A refresh credential from Apple is encrypted with a dedicated server key so we can revoke the game link when you delete your account. If Apple is temporarily unavailable, a separate encrypted revocation request is retained and retried until revocation succeeds. Expiring link requests and encrypted recovery responses are removed by scheduled cleanup. Choosing to restore linked cloud progress replaces the current guest progress; restoring a purchase is a separate action and does not replace puzzle progress.
Game Center on Apple devices
Game Center can authenticate your Apple game profile and receive achievement progress. It is separate from linking the Puzzle Lab cloud account. Apple processes Game Center profile information, activity and diagnostics under Apple's Privacy Policy. We do not request your contacts or friends list.
Advertising and your choices
The game integrates Google AdMob and Google's User Messaging Platform. The Mobile Ads SDK can collect and share IP addresses, app and ad interactions, diagnostics, and device or account identifiers for advertising, analytics and fraud prevention. IP addresses can indicate approximate location even though the app does not request location permission. This includes processing by Google that Zyntra does not receive directly.
Apple version note: iOS version 1.0 requests non-personalized ads. The additional iOS 1.0.1 practices described below are prepared for a forthcoming update and apply only after you install that version. This notice does not mean the update is already available in your App Store.
Available consent choices depend on your region and settings. Where required, you can reopen Ad privacy in the game's Profile. On iPhone and iPad, Apple's App Tracking Transparency prompt may ask whether to allow tracking when you choose the tracking-permission control. If you allow it, Google Mobile Ads can use your device's advertising identifier for advertising measurement and related purposes across apps and websites. If you decline or tracking is unavailable, the game does not access that identifier for tracking. You can change Apple's tracking permission in iOS Settings.
Optional ad personalization in iOS 1.0.1: Profile > Ad preferences provides a personalization switch. Its initial On setting is a preference, not consent. The app requests non-personalized ads unless this preference is On and Apple's tracking permission is authorized. Even when both conditions are met, Google's consent choices and regional requirements still determine whether personalized ads may be served. Permission to request an ad is not treated as permission to personalize it. Google's publisher first-party identifier remains disabled in this iOS integration.
Turning personalization Off or withdrawing Apple's tracking permission returns the updated app to non-personalized ad requests. The app discards cached ads when it detects a change to these settings or opens Google's privacy-options form. Ad privacy, Apple tracking permission and usage analytics are separate choices. Declining Apple tracking does not remove your progress or purchases, or require you to buy No Ads Forever. Rewarded videos remain voluntary and subject to ad availability and applicable consent choices. Google may still process contextual advertising, measurement and fraud-prevention data as described above. The game does not request precise location permission.
Read Google's iOS Mobile Ads data disclosure, Google's Android Mobile Ads data disclosure, and Google's ad controls.
Rewarded videos are optional. When server-verified rewards are enabled, a generated player ID and reward-request reference associate the selected offer with its verified transaction and prevent duplicate grants. Those rewards are not purchases. Designated test devices and diagnostic builds use test advertising. In supported releases, assistance is granted only after our server verifies the selected reward offer; a completed video callback on the device alone does not grant a reward.
Optional usage analytics
The game uses Google Analytics for Firebase when usage analytics is enabled. On iOS, collection starts disabled and requires a saved choice allowing it. Released iOS 1.0 does not expose the new Usage analytics screen. In the prepared iOS 1.0.1 update, the first time you open the app without a saved choice, it offers Allow usage analytics or Keep analytics off. Enabling requires the choice to be saved successfully. If saving fails, analytics stays off for that session.
Analytics helps us understand puzzle difficulty, onboarding and which screens players use. Our events include screen visits, puzzle starts and validated completions, including a first-puzzle-completed event. Android also records tutorial steps; iOS 1.0.1 adds tutorial-begin, tutorial-complete and tutorial-skip events. Event details include game mode, board size, move count and completion success. When collection is enabled, Firebase may also collect automatic events such as first opening the app, engagement and purchases. Our custom event list is not a complete list of SDK processing.
Google processes an app-instance identifier, app and device information and approximate location derived from IP addresses. We do not send your name, Google email, cloud-account identifier or puzzle contents to Analytics. Analytics advertising-ID collection and advertising-personalization signals are disabled in this integration. On iOS, Analytics IDFV collection and Firebase's automatic ad-network registration remain disabled. The separate Apple install-measurement request in iOS 1.0.1 is described below. AdMob has its own settings described above.
In iOS 1.0.1, you can turn usage analytics off or on through Profile > Privacy & support > Usage analytics. Android provides its Usage analytics control under Privacy & support; its initial setting depends on regional privacy requirements and available consent status. Turning it off stops future Analytics event collection from this integration; it does not automatically erase information already received by Google. If the updated iOS app cannot save an Off choice, it stops collection for that session and tells you that you may need to turn it off again next launch. Analytics data is processed by Google under its service terms and retention settings, separately from our Canada-hosted game-progress database. For privacy requests, contact us below. Read Google's Privacy Policy.
Optional Apple install measurement in iOS 1.0.1
In the prepared production update, allowing Usage analytics also permits the game to request install measurement through Apple's SKAdNetwork system. This helps measure whether an ad led to an installation. This request does not use your advertising identifier or ask for tracking permission. It submits an install-only conversion value of zero, not puzzle progress or gameplay conversion values, and Apple controls any resulting attribution reporting.
The app records a local submission marker to avoid repeating a completed request. If the request fails before that marker is saved, a later launch with analytics allowed may retry. Turning Usage analytics Off stops future app-initiated submissions, but cannot cancel an OS request already submitted or erase reporting already processed. A successful request does not prove that Apple attributed an installation. Diagnostic and simulator builds do not make this production request.
No Ads Forever and payments
No Ads Forever is the game's only paid item: a non-consumable purchase through Google Play on Android or the App Store on Apple devices. Its verified entitlement removes banners and interstitials across Lumen, Parcel and Echo. Optional rewarded videos remain available. There is no in-game currency.
The platform store processes payments. Zyntra does not receive your payment-card details. Our backend processes product details, encrypted purchase proof, hashed purchase tokens and purchase, acknowledgement or refund status to verify and restore the entitlement. On Apple devices, our service verifies StoreKit transaction proofs with Apple and keeps transaction references, an original-account binding hash, product and refund status, and product-access links used to restore No Ads. Explicit App Store restoration briefly processes a device-verification identifier with the signed proof to check that the proof belongs to that device. The raw identifier and signed proof stay in memory during verification and are not stored in our progress database or ordinary logs. A one-way retry fingerprint is retained in a short-lived restore receipt, normally for up to 24 hours after completion before successful cleanup. Restoring No Ads does not change your current puzzle progress. Deleting progress is not a refund request to either store.
Deletion and retention
You can request account and data deletion without reinstalling the game. We verify authority before erasure. The account-deletion transaction removes active sessions, attempts, progression, assistance and reward records, and active account-owned purchase records. You can request deletion in the game through Account > Delete account, or use the support request route below without reinstalling.
A limited deletion receipt retains a request reference, proof hash and timestamp for interrupted-request recovery. It expires after 24 hours and is removed by scheduled cleanup when that job succeeds. Separate hashed purchase-token, Apple transaction-reference and original purchase-account binding records are retained for lifetime purchase restoration and fraud prevention; these limited records currently have no automatic expiry and do not contain deleted gameplay or raw purchase tokens.
Encrypted operational backups can contain earlier account data. Deletion does not rewrite existing backups. New dedicated game-progress backup copies expire after 30 days through scheduled cleanup. Some historical pre-release archives remain outside that automatic policy, so we cannot yet promise a fixed expiry for every older copy. Successful cleanup can be delayed by an offline host or a failed job. We keep limited deletion records separately from progress backups to prevent deleted accounts returning when an older backup is restored. These records contain a hash derived from a generated player identifier, a request reference and a deletion timestamp; they contain no gameplay, email, password or raw purchase token. They currently have no automatic expiry. Restoration is blocked when the current deletion record cannot be established. Operational service and proxy logs are also retained for security and troubleshooting; the verified service-log limit is two files of up to 5 MB per service, rather than a fixed number of days.
Contact and updates
Email [email protected] to ask about access, correction or deletion of your game data. Do not send passwords, session credentials, recovery keys or payment-card details. We may update this notice when the game or its data practices change.