Skip to main content
Bubble Shot
HomeAboutHow to PlayFeaturesFAQPrivacy PolicyTermsContactDownload Game
← Back to Bubble Shot
Android app privacy

Bubble Shot Privacy Policy

Intended effective date: October 3, 2026 · Sanu Tech Innovation LLP

On this page1. Introduction2. Information We Collect3. Information We Do Not Collect4. How Information Is Used5. Advertising6. Analytics and Crash Diagnostics7. Third-Party Services and Sharing8. Children’s Privacy9. Data Security10. Data Retention11. Data Deletion and Your Choices12. Third-Party Links13. Changes to This Privacy Policy14. Contact Us
APP-PRIVACY DRAFT — NOT READY FOR PLAY REVIEWThis page is specifically for Bubble Shot. The app’s SDKs, data flows, permissions, audience and retention details have not been confirmed. Complete the marked sections from the released app before using this URL in Play Console. Do not just remove the notices.
App
Bubble Shot · Bubble shooter puzzle game
Developer
Sanu Tech Innovation LLP
Privacy contact
bubbleshot@sanutechservices.com
Scope
Android app, its service providers and app support

1. Introduction

This Privacy Policy is intended for Bubble Shot, the Android bubble shooter puzzle game developed by Sanu Tech Innovation LLP. It covers information handled by the mobile app, its integrated service providers, and support requests relating to the game. It is not a policy for all Sanu Tech products.

Bubble Shot involves aiming, matching and popping bubbles of the same color, clearing levels and working toward higher scores. The Bubble Shooter wording inside the supplied promotional logo describes the game category; this policy identifies the app as Bubble Shot.

Developer confirmation requiredConfirm that Bubble Shot is the exact name on the Google Play listing. Add the actual Android package name and listing URL if available; do not invent them.

2. Information We Collect

Support messages you choose to send

If you email our support address, we receive your sender address and the contents you send. The website contact form asks for your name, email address and message and sends those details to the support mailbox when email delivery is available. Do not include passwords, payment-card information, or unnecessary sensitive details.

Information handled by the app

Developer confirmation requiredList each category actually accessed, collected or shared by the production app and every included SDK. For each category, identify whether it stays on the device or leaves it, who receives it, whether collection is required or optional, and why it is needed. Check device identifiers, IP/network information, app interactions, gameplay progress, crash diagnostics, account information and purchase records; these are review prompts, not claims that all are collected.

Website contact security

The supplied support endpoint uses a session cookie for request verification and temporary hashed IP-based counters to limit repeated submissions. It emails the message rather than saving a new enquiry database in the website code. Hosting and email providers can have their own operational logs.

Developer confirmation requiredConfirm the hosting/mail providers used in production, their logging practices and applicable retention periods. These website-only controls must not be represented as app SDK behaviour.

3. Information We Do Not Collect

Developer confirmation requiredAfter reviewing the released app, identify any relevant data categories the app and its SDKs do not access or collect. No blanket “we collect no data” statement has been made, because app-side data handling has not been confirmed.

The website support form does not ask for a password, card number or government identity document. Do not send these to support. This statement concerns the form, not unverified behaviours of the mobile app.

4. How Information Is Used

Information voluntarily sent to support is used to understand the question or problem and communicate with the person requesting assistance.

Developer confirmation requiredDescribe the actual app-side purposes for every data category: for example game functionality, synchronising progress, diagnostics, analytics, advertising or abuse prevention only where implemented. Identify consent or other applicable grounds and user choices where required. Do not retain purposes that do not apply.

5. Advertising

Developer confirmation requiredConfirm whether Bubble Shot contains ads. If it does, name every advertising/mediation SDK, relevant identifiers and other data processed, ad-personalisation or consent choices, recipient privacy-policy links and settings for children/mixed audiences. If it has no ads, say so only after verifying the release build.

No ad network, personalised-ad setting or advertising identifier collection is asserted in this draft. Installing this website does not add an advertising SDK to the mobile game.

6. Analytics and Crash Diagnostics

Developer confirmation requiredConfirm separately whether analytics and crash reporting are enabled. List actual providers, events/diagnostics, identifiers, purposes, retention, sharing and available controls. For example, the presence of a Firebase-related dependency alone does not establish which Firebase products are enabled.

The game’s analytics configuration has not been supplied, so no particular analytics or crash-reporting service is named as active.

7. Third-Party Services and Sharing

Developer confirmation requiredAdd the actual SDK/service list with provider names, data categories, purposes, retention details or links, and public privacy-policy URLs. Check the game’s source/dependency list and the SDK versions used. Google Play distribution alone is not evidence that the game integrates Google Play Services, Play Games, AdMob or Firebase.

Review service-provider access, onward sharing, international processing and any applicable safeguards before finalising this section. A provider link does not replace a clear explanation of how that provider handles data in this particular app.

8. Children’s Privacy

Developer confirmation requiredState the actual intended age groups and whether the app is directed at children or a mixed audience. Describe any age screen, parental consent or child-specific data/advertising settings that genuinely exist. Match the Google Play Target audience and content declaration; do not choose an arbitrary age restriction just to complete this policy.

A parent or guardian with a question about information relating to a child can contact bubbleshot@sanutechservices.com. Please identify the app and concern without sending unnecessary sensitive information.

9. Data Security

Developer confirmation requiredDescribe safeguards actually implemented for app data in transit and at rest, access controls, relevant SDK security, and incident handling. Confirm actual network traffic is encrypted; do not mark encryption as verified from this website template alone.

No online service or device can be described as completely secure. The public website must be served over HTTPS before collecting support messages.

10. Data Retention

Developer confirmation requiredState the actual retention period or justified criteria for gameplay/progress data, identifiers, diagnostics, account data, support emails and backups as applicable. Include relevant service-provider retention and exceptions for legal or security obligations. No arbitrary deletion deadline has been invented.

The website’s temporary rate-limit counters expire after an hour and old entries are pruned during later submissions; that counter lifetime is not the retention policy for support emails or app data.

11. Data Deletion and Your Choices

For a Bubble Shot privacy or data-deletion request, email bubbleshot@sanutechservices.com with the subject Bubble Shot privacy or deletion request. Explain which information or interaction your request concerns and provide only the minimum information needed to locate it. Do not send passwords.

This email route allows you to ask the developer for assistance; it does not automatically delete data or prove that all categories can be located. The developer must confirm the applicable identity checks, process, timing, exceptions and third-party handling.

Developer confirmation requiredConfirm whether users can create an account in Bubble Shot. If yes, provide the real in-app deletion route and an accessible external deletion resource, explain deletion of associated data and retention exceptions, and enter the actual deletion-resource URL in Play Console. An email link alone is not a verified implementation of the complete account-deletion process.
Developer confirmation requiredState the confirmed method for removing on-device progress/preferences and any separate cloud/provider records. Do not imply that uninstalling the app erases remote copies.

12. Third-Party Links

Links to Google Play, the company website or other services open sites with their own terms and privacy notices. Read the applicable notice before sharing information there. This does not remove the developer’s responsibility for SDKs integrated into Bubble Shot.

13. Changes to This Privacy Policy

The policy should be updated when Bubble Shot’s actual processing, service providers or user controls change. The effective date and any notice shown in the app must reflect the version adopted for the released game. The intended effective date of this draft is October 3, 2026.

14. Contact Us

App: Bubble Shot
Developer: Sanu Tech Innovation LLP
Privacy and support: bubbleshot@sanutechservices.com
Company website: sanutechservices.com

No physical address has been assumed. If required for the final notice, insert the company’s confirmed address rather than a guessed location.

Email privacy supportContact page
Bubble Shot

Bubble Shot is a casual bubble shooter puzzle game designed for fun, colorful and engaging gameplay.

Developed by Sanu Tech Innovation LLP ↗

Game

AboutHow to PlayFeaturesFAQ

Support

Contact UsEmail SupportDownload Game

Legal

Privacy PolicyTerms & Conditions
© 2026 Sanu Tech Innovation LLP. All rights reserved.Bubble Shot · Bubble Shooter Puzzle Game