Zyntra Apps - Privacy Policy & Terms of Use
Privacy Policy
Zyntra Apps ("we", "our", or "us") develops and publishes global mobile and Wear OS applications, including watch faces, casual games, and companion tools.
We value user privacy and are committed to protecting your information responsibly.
Z Ball: 1v1 Tilt Shot Arena
App-specific privacy notice. Z Ball, previously listed as Z Ball: Tilt Shot Arena, is a game published by Zyntra Apps. This notice covers Z Ball on Android, iPhone and iPad, including its Cloud Player, optional account linking, gameplay, Watch and the advertising, purchase or reminder features offered by your installed version. Features and controls vary by platform and version. It takes precedence over general examples elsewhere in this policy where they differ.
Cloud Player and optional account linking
Cloud Player uses a generated player ID, your display name, game progress, scores, rewards and cosmetic ownership to operate and recover your account. A device-held cryptographic key authenticates the installation. Linking a Google account is optional and is not required for online play. Where Sign in with Google is offered and you choose it, we verify a Google-issued identity token and associate its stable Google account identifier with your Cloud Player. The token may contain basic identity claims; Z Ball uses the verified identifier for account linking and recovery, does not retain the identity token or your Google email address for that purpose, and never receives your Google password. On Android, existing Google Play Games linking remains available through the separately labelled recovery flow. Your progress is stored in Zyntra's OVH-hosted game service, rather than in your Google account. We do not merge players by email address.
Guest players also have an account identifier. The game sends an app-generated public key and a persistent identifier derived from that key to authenticate requests and bind devices to accounts. This identifier is not your advertising ID. Account and gameplay records can be linked to your player or installation even when you have not linked Google or Apple. We retain the account, consent, verification and duplicate-prevention records needed to operate the game separately from optional Analytics exports.
If Sign in with Apple is offered and you choose it, we use Apple's app-specific account identifier to link and recover your Cloud Player. The integration does not request your name or email address and does not receive your Apple Account password. Sign-in and authorization credentials are processed to verify the link and manage its revocation; server credentials needed for this purpose are protected separately from your public profile. You do not need to link Google or Apple to play Online 1v1 or use Watch. Linking a provider does not move your game progress into that provider's account.
Public profiles, live viewing and replays
Your public player ID, display name, equipped cosmetics, level and public game statistics can appear to other players in profiles, leaderboards and matches. Eligible public online matches can also be shown to spectators with a delay and made available as replays. Watch uses recorded game events, ball movement and public participant information; it does not record your microphone, camera or phone screen. Private/friend matches and CPU matches are not included. We process temporary viewer presence and account-bound replay-view records to show viewer/view totals and prevent duplicate counts. Completed Watch recordings are available within a rolling seven-day window and are removed by scheduled cleanup after that window. Replay files downloaded to your device are temporary and are cleared after viewing, exit, cancellation or failure; abandoned files are cleaned on a later launch. Brief backgrounding or an ad can retain the current temporary file so viewing can continue.
Advertising and purchases
On Android, Z Ball uses direct Google AdMob for banners, interstitials and optional rewarded ads. Where advertising is offered on iPhone and iPad, requests apply restrictive age-related treatment for every player and ad personalization is disabled. These restrictions apply regardless of a saved advertising preference or Apple tracking-authorization status. A saved personalized-ON preference does not enable personalized ads. This request treatment does not determine a player's age. Regional privacy choices are managed through Google's User Messaging Platform and can be reopened in Settings when available. When you choose a protected rewarded offer, we supply the persistent public-key-derived installation identifier and a reward-claim ID for server verification. We associate the verified ad completion and reward with your player to prevent duplicate or fraudulent rewards. This exchange does not use your email or password. No Ads and Gold Pass suppress automatic ads while the verified entitlement is active; voluntary rewarded offers remain optional. Android purchases are processed by Google Play, using the prices and currency displayed by Google Play. We validate purchase receipts and entitlement status to deliver, restore and maintain the benefits you purchased; we do not collect your payment-card details.
If an Apple in-app purchase is offered, the Apple purchase sheet shows its product, price and currency before you authorize it. For purchases billed by Apple, we process the product and transaction identifiers, signed purchase proof and entitlement status needed to validate and deliver the purchase, restore eligible benefits and handle refunds or revocations. Apple handles the payment information; this validation does not give Zyntra your payment-card details. See purchase and subscription help.
Z Ball Android advertising-choice update (2026-10-07). These updated advertising-choice screens are included in Z Ball version 0.2.8 and later. Earlier installed versions keep their previous controls until updated. On a fresh installation, the Terms screen initially shows personalized ads ON as an editable draft. Displaying this draft or opening the app does not save the preference or grant permission for personalized advertising. You can turn the draft OFF before accepting. Either "ACCEPT & ALLOW ANALYTICS" or "ACCEPT WITHOUT ANALYTICS" accepts the Terms and saves the advertising choice shown on that screen; the buttons separately select whether to enable optional gameplay analytics. On a fresh installation, optional gameplay analytics remains off unless you choose its opt-in action.
Existing Z Ball Android players whose saved ad-personalization choice is OFF are offered an explicit updated-terms and advertising-choice review on a later app opening, when it can be shown without interrupting gameplay or another active dialog. This includes No Ads and Gold Pass holders. Personalization stays OFF unless you explicitly enable it. You can accept personalized ads or keep your current choice. The game remembers your resolution for this review version, so keeping the current choice does not cause the same review to repeat on every opening. Neither review action changes your saved optional gameplay analytics choice or paid benefits.
You can change the in-game advertising preference at any time in Settings > Privacy & Terms. Google privacy options remain available there when required. The in-game preference does not override Google's User Messaging Platform consent, device privacy choices, age-based restrictions or applicable regional law; on Android, personalized advertising is permitted only where those requirements allow it. On iPhone and iPad, the restrictive advertising policy described above continues to apply. No Ads and Gold Pass continue to suppress automatic ads while their verified entitlement is active, and voluntary rewarded offers remain optional.
Google's Mobile Ads SDK processes IP addresses (including approximate location), ad and app interactions, diagnostics, and device or account identifiers for advertising, analytics and fraud prevention. Requests follow applicable consent and device settings. Advertising providers retain data under their own policies.
See Google's Privacy Policy. Older installed testing versions may contain Unity LevelPlay or Unity Ads; the current game uses direct Google AdMob.
Optional gameplay analytics
Newer versions of Z Ball offer optional gameplay analytics through Google Analytics for Firebase. This measurement is off until you enable Analytics in the game. You can change that choice in Settings. It helps us understand tutorial and first-game milestones, public matchmaking and match completion, friend-match activity, and Z Rush discovery, play and leaderboard interactions so we can improve the game. Events use fixed categories, bounded durations and outcomes; some lifecycle events include a random correlation value, and Z Rush events include a day, score and rank context. On Android, with this choice enabled, selected tutorial and match milestones may also be shared with Google Ads to measure the results of our advertising campaigns. This does not enable personalized advertising or remarketing audiences. The SDK also measures app sessions and interactions, app and device information, approximate location derived from IP addresses, a pseudonymous app-instance identifier, and purchase or subscription events. It does not give us your payment-card details.
Our gameplay analytics events do not include your Google or Apple account identity, email address, game display name, Cloud Player ID, match-room ID, purchase token or credentials. We disable advertising-ID collection for this Analytics integration. On Android, enabling Analytics grants analytics-storage and advertising-measurement consent; advertising storage and ad personalization remain denied. On iPhone and iPad, enabling Analytics grants analytics-storage consent only: advertising storage, advertising user-data and ad-personalization consent remain denied, and vendor-ID collection is disabled for this Analytics integration. Turning Analytics off denies all four consent types. These choices do not describe or authorize the separate advertising SDK's data use. These optional analytics controls are separate from the advertising and UMP choices described above.
Turning Analytics off stops this installation's optional measurement and resets its locally stored Analytics data and app-instance identifier. Deleting your Cloud Player removes its analytics consent, counters, gameplay analytics facts and handoff receipts from our central game service and resets Analytics on the device completing deletion. Limited first-party device and consent metadata can remain in already-signed regional gameplay delivery records until acknowledgement and operational cleanup; those records contain no Google Analytics identifier and cannot create new analytics receipts for a deleted account. These actions do not retroactively erase events already uploaded to Google: we do not keep a mapping from your Cloud Player to Google's Analytics app-instance identifier.
For this optional Z Ball measurement, our current Google Analytics settings retain event-level data for two months and user-level data for fourteen months. New activity resets the user-level retention period, so continuing activity can extend it. Google's standard aggregated reports are not subject to those retention controls. These app-specific rules take precedence over the general analytics-retention example elsewhere on this page. See Google Analytics retention information and Google's Privacy Policy.
We require third parties with which Z Ball shares personal data to provide the same or equal protection described in this policy and required by applicable platform privacy rules.
Optional crash diagnostics on iPhone and iPad
In versions offering this feature, the optional analytics choice also explains crash diagnostics. After you explicitly allow that updated choice, Google Firebase Crashlytics can receive native crash stack traces and exception details, app version/build, device and operating-system information, SDK-generated diagnostic identifiers, and recent analytics events and their parameters. These events can include the gameplay milestones, durations, outcomes, scores, ranks and random match correlation described above. We do not add your player ID, name, email, sign-in credentials, custom text logs or raw gameplay state to crash reports. Native exception details can still contain app or system text.
A previous analytics choice made before this disclosure does not itself enable crash uploads. You can choose again in Settings. New reports enter the upload queue only for an eligible consent and account context; turning analytics off or changing accounts invalidates pending eligibility. The SDK may keep crash files locally after it has initialized, including while report uploads are off. Reports spanning a denied interval are excluded from later uploads; deletion is requested and can take a later startup to finish. Previously authorized reports already in the SDK's upload queue may still upload or retry after you turn analytics off, change accounts or delete your Cloud Player. These actions do not automatically erase reports already received by Google or confirm their deletion. Contact us about privacy or deletion requests.
Storage and account deletion
Game and Cloud Player traffic is encrypted in transit. Music, sound, commentary, haptics and display preferences are stored on your device. Cloud Player data is retained while the account remains active, subject to the deletion and limited retention rules below. The game does not access your device's address book or require precise location, health data, photos or access to your personal files. If you use in-game Friends, we store the player IDs and relationships needed for friend requests, your friends list and presence. Matches can include preset emote messages; these can also appear in eligible public Watch recordings. These features do not read phone contacts or provide free-text chat.
You can initiate deletion from the game's Cloud Player account controls, including for a guest account. If you cannot access those controls, you can request help by emailing [email protected] with your in-game player ID if available. Do not send passwords, private keys or recovery secrets. We verify the request and delete or anonymize account data, remove linked provider mappings, revoke active device sessions and remove associated Watch recordings and viewer records. Copies held by regional game services are removed through queued cleanup. Limited purchase/reward records and a keyed, one-way anti-abuse identifier may be retained where needed to prevent fraud, resolve disputes or meet legal obligations; these retained records are not used to restore your deleted profile. Uninstalling the app alone does not delete the cloud account. Deleting a game account does not automatically cancel a subscription billed by Google Play or Apple. Manage or cancel it with the store that bills you. The Z Ball account-deletion instructions explain the in-game steps and the support option if you cannot access them.
Optional game reminders on Android
Z Ball can send optional reminders about daily login-streak rewards, changes to your leaderboard rank and upcoming leaderboard resets. Reminder preferences start enabled, but Android must allow notifications before this installation can receive them. You can turn each reminder category off in the game's Settings, or turn all notifications off through Android. We combine normal reminders into at most one daily message per player, with at most one additional last-chance message on a leaderboard reset day. The game does not display these reminders while you are actively using it.
For delivery we use Google Firebase Cloud Messaging. When you allow reminders, the game registers a Firebase installation token and an opaque enrollment identifier with your Cloud Player. Our OVH service encrypts delivery tokens at rest. We use your device's time-zone setting, a limited record of your rank changes and your current login-streak claim status to schedule relevant reminders and prevent duplicate messages. The notification payload contains only the reminder type, relevant rank numbers or leaderboard names, dates and opaque delivery identifiers; it does not contain your name, email, Google identity, Cloud Player ID, payment data or credentials. Firebase uses installation identifiers to route messages under Firebase's privacy information.
Turning every reminder category off, revoking Android permission, signing out or deleting your Cloud Player stops future delivery enrollment from this installation. A message already accepted for delivery may still arrive; local permission and enrollment checks also control display. Unrefreshed registrations become ineligible for delivery after 90 days; the encrypted registration can remain until it is revoked or the account is deleted. For active reminder enrollments, scheduled housekeeping normally removes rank baselines older than eight local days and completed or cancelled delivery records older than 35 days. Pending delivery records are retained for retry or cancellation. Deleting your Cloud Player removes its reminder preferences, delivery registrations, rank baselines and delivery records. Login-streak claim receipts remain subject to our existing wallet and anti-abuse retention rules. Notification preferences are separate from optional gameplay analytics, advertising choices and email subscriptions. Rewards do not require notification permission.
Optional game reminders on iPhone and iPad
Where local reminders are offered, Zyntra's game service uses your player and installation identifiers, reminder preferences, time zone and relevant game state to prepare reminder plans and prevent duplicate messages. The game schedules the accepted plan on your device and reports scheduling or cancellation status to the service. The service stores these account-bound planning and status records; local delivery does not mean all reminder processing happens only on your device. This local delivery path does not require registering a remote delivery token. iOS or iPadOS must grant notification permission before reminders can be displayed. You can change the game's reminder preferences or turn notification permission off in your device Settings. Reminder permission is separate from gameplay analytics, advertising choices and rewards.
Request deletion of your Z Ball Cloud Player. Include your in-game player ID; do not send passwords, private keys or recovery secrets.
Visiting this website is separate from using the game. Website hosting and security providers, including Cloudflare, may process your IP address, requested URL, browser user agent and request time to deliver and protect the site. Support emails are used to respond, investigate requests, meet legal obligations and protect services. Questions: [email protected].
Optional game-release emails
If you use our website's release-notification form, we store your email address, the signup date, and your consent to receive Zyntra game-release announcements in our existing server database. Signing up is optional and separate from playing our games or creating a game account. We do not add player-account or support-contact email addresses to this list automatically.
We use this list only for our game-release announcements, not advertising audience uploads, and we do not sell it. We keep the signup while you remain subscribed. To stop these emails or request deletion, email [email protected]. We may retain a minimal opt-out record to avoid sending unwanted messages.
Optional Z Ball launch emails
If you choose to join the Z Ball launch list, we store your email address, consent version, signup and consent dates, and subscription status on our existing server. We use this separate list to notify you when Z Ball is released. Joining it does not subscribe you to general Zyntra updates. Existing studio subscribers are not copied into the Z Ball list.
We do not sell these addresses or add them to advertising audiences. We keep your subscription while it is active for the launch announcement. You can opt out or request deletion by emailing [email protected]. We may retain a minimal opt-out record so we can honour your request.
1. Information We Collect
Our apps are designed for minimal data use. We may collect or process:
- Account data: when users sign in using Google Services, we collect your Google ID, display name, and email to manage gameplay progress, gem counts, and unlocked products.
- Analytics and diagnostics: anonymous usage statistics such as crashes, performance logs, and in-app events.
- Advertising data: Google AdMob identifiers used for ad personalization and frequency control.
- Device information: model, operating system version, screen type, and locale for compatibility.
- Optional wearable metrics: heart rate, step count, or motion data used within watch apps for display or gameplay.
- User feedback: voluntarily provided comments, bug reports, or contact emails.
We do not collect or require sensitive personal data such as payment details, biometric identifiers, or private contact information.
2. How We Use Information
- Authenticate and maintain user progress through Google Services.
- Operate and improve our apps and watch faces.
- Display non-intrusive advertising via AdMob.
- Diagnose issues and enhance performance.
- Respond to user requests or feedback.
- Comply with applicable laws and platform policies, including Google Play Developer Program Policies.
3. Data Storage and Retention
Account and progress storage depends on the app. Google services provide authentication where offered. Z Ball game progress, purchases and cosmetics are stored in the OVH-hosted Cloud Player service described above; linking Google does not move that progress into a Google account.
Diagnostic and analytics data are stored only as long as necessary, typically no more than 12 months, before being deleted or anonymized.
4. Information Sharing
We do not sell or rent user data. Limited data may be shared with trusted providers:
- Google AdMob for advertising and analytics.
- Google Play Games and Google Sign-In Services for authentication and user progress tracking.
- Zyntra local servers for delivering watch-face and game assets.
- Firebase Crashlytics when crash reporting is enabled.
All services follow Google developer policies and align with GDPR and CCPA frameworks.
5. Security
We use encryption, secure network protocols, and limited access controls to safeguard collected data. While no system is completely secure, we follow best practices to reduce risk.
6. Your Choices and Rights
- Manage your Google Account to view or remove linked data.
- Limit ad personalization through your device privacy settings.
- Uninstall any Z App at any time to stop data collection.
- Request data deletion by emailing [email protected].
7. Children's Privacy
Z Apps are not directed toward children under 13. Z Ball is intended for players aged 13 and older, including teenagers. For those players, we process the account and gameplay data described in the Z Ball notice above.
8. Changes to This Policy
We may update this Privacy Policy periodically. Continued use of Z Apps after updates signifies acceptance of the revised terms.
9. Contact Us
For questions or privacy requests, email [email protected].
Zyntra Apps - Global Developer Brand