CandyBlast Privacy Policy

Last updated: April 16, 2026

1. Introduction

CandyBlast is a mobile game app that uses Firebase for account login and cloud save features. This privacy policy explains what data the app collects, how it is used, and how it is stored.

2. Data we collect

Authentication

We use Firebase Authentication with email and password. We collect the user’s email address only for login and account identification.

Game progress and save data

The app stores the following data per signed-in user:

• coins
• boosters
• game progress
• lives
• daily reward status
• spin reward status
• game session state

This data is stored in Firebase Cloud Firestore under a document associated with the user’s Firebase uid.

3. Where data is stored

Data is saved in Firebase Cloud Firestore in the collection gameSaves. Each user’s data is stored in the document gameSaves/{uid}.

4. Ads and analytics

CandyBlast may display ads in the app. If you use AdMob or another ad network, the ad provider may collect device identifiers or other ad-related data. The app itself does not send analytics unless you add another analytics service.

5. Why we collect this data

We collect and store this information to:

• let users sign in securely
• save game progress across devices
• restore previous game state after reinstall
• provide rewards and game continuation

6. No sharing with third parties

The app does not sell personal data. User save data is only stored in your Firebase project and is not shared with external parties except service providers required to run Firebase and ads.

7. Security

Your data is stored in Firebase and protected by Firebase security rules. The app uses authentication and Firestore access rules so each user can only access their own record.

8. Your rights

If you want to delete your account, change your email, or request removal of your saved game data, please contact the developer at:

Email: codewab.official@gmail.com

9. Changes to this policy

We may update this privacy policy from time to time. The latest version will be published on the same GitHub Pages URL.