Privacy Policy

Clap Stars

Last updated: August 31, 2026

1. Introduction

This Privacy Policy describes how Clap Stars ("we", "our" or "the application") collects, uses and protects information when you use our mobile application.

By using Clap Stars, you accept the practices described in this policy. If you do not agree, please do not use the application.

2. Information We Collect

2.1. Account Information

Clap Stars can create an anonymous Firebase account when the app starts. If you choose to sign in with Google, we may also receive basic Google profile information.

• Anonymous Firebase user ID: Used to keep your favorites and selected star associated with your app account.
• Google profile information: If you sign in with Google, we may receive your name, email address, profile picture and unique Google/Firebase user ID.
• Authentication tokens: Used by Firebase Authentication to keep your session secure.

2.2. User Profile

We store the minimum data needed to provide the app experience:

• Favorite stars: The stars/entities you mark as favorites.
• Selected star: The star/entity currently selected for clapping.
• Last selected favorite: Used to reopen the Clap screen with your preferred favorite.
• Public clap submissions: Claps sent to stars through Cloud Functions to update public star counters and rankings.

2.3. Local-Only Economy Data

Your clicker economy, including available claps, local season claps and upgrade ownership, is stored locally on your device. This local economy may reset by season and is not intended to be a permanent cloud-backed account economy.

2.4. Public Star and Ranking Data

Clap Stars contains public star/entity documents, seasonal ranking documents and optional public fan ranking rows. Star data may include names, categories, descriptions, images and external source URLs. If you enable your public fan profile, your username, profile photo and seasonal claps may appear in a star's fan ranking. Your private contribution history remains visible only to your account.

2.5. Discovery Data from Wikipedia/Wikidata

The app uses Wikipedia and Wikidata as discovery sources to find people, groups, teams, franchises, characters, brands and other entities with fans. Search results may include page titles, descriptions, images, page IDs, Wikidata IDs and source URLs. When you add a discovered result, the app creates or updates a public star/entity record through a Firebase Cloud Function.

2.6. Automatic Technical Information

Through Firebase Analytics and Crashlytics, we may automatically collect:

• Crash and error data: Information about crashes and non-fatal errors.
• Device information: Device model, operating system version, app version and system language.
• Usage data: App events such as discovery searches, ranking loads, sign-in events and clap submission results.
• Performance and protection signals: App Check and Firebase service data used to protect backend access.

2.7. Information We DO NOT Collect

Clap Stars does not collect:

• Payment or financial information.
• Contacts from your device.
• Precise geographic location.
• Browsing history outside the app.
• Access to camera, microphone or device files.

3. How We Use the Information

We use collected information for:

• Authentication and account management: Create and maintain your app account.
• Core app functionality: Store favorites, selected star and public clap submissions.
• Rankings: Update public daily, weekly and monthly-season star rankings, optional fan rankings and permanent Hall of Fame achievements.
• Discovery: Search external public sources and create public star/entity records.
• Security: Protect backend services with Firebase App Check, authentication and server-side validation.
• Stability: Identify and fix crashes and technical issues.
• Product improvement: Understand feature usage through aggregated analytics.
• Advertising: Show App Open Ads via Google AdMob to support the free app.

4. Advertising

Clap Stars shows ads through Google AdMob:

• App Open Ads: Shown when the app is opened or resumed after being in the background

AdMob may collect device identifiers and usage data to serve personalized or non-personalized ads. This is governed by Google's Privacy Policy.

5. Data Storage and Sharing

5.1. Firebase / Google (Service Provider)

Clap Stars uses Firebase services provided by Google LLC:

• Firebase Authentication: Anonymous and Google authentication.
• Cloud Firestore: User profile data, public stars and materialized rankings.
• Cloud Functions for Firebase: Server-side star creation, clap submission and ranking maintenance.
• Firebase Crashlytics: Crash and error monitoring.
• Firebase Analytics: Usage analytics.
• Firebase App Check: App integrity and backend protection.

These services process data according to Google's Privacy Policy.

5.2. Wikipedia and Wikimedia Services

Discovery searches use public Wikimedia endpoints, including Wikipedia and Wikimedia pageviews APIs. These services may receive your search requests as part of normal internet communication. Their processing is governed by Wikimedia's own policies.

5.3. No Other Third Parties

Clap Stars does not sell, rent or trade your personal information to third parties for commercial purposes. Advertising is delivered by Google AdMob as described above.

6. Data Security

6.1. Technical Security Measures

We use several security measures:

• Encryption in transit: Communications use HTTPS/TLS.
• Firebase security: Firebase services encrypt data at rest and in transit.
• Authentication: Firebase Authentication protects user-specific data.
• Security Rules: Firestore rules restrict client access.
• Cloud Functions: Public clap writes and star creation are validated server-side.
• App Check: Helps prevent unauthorized backend access.

7. Data Retention

• Account profile data: Retained while your account remains active.
• Favorites and selected star: Retained while your account remains active.
• Season and star ranking aggregates: Retained permanently as public game history. Hall of Fame achievements are also permanent.
• Private seasonal contributions: Retained while your account remains active and deleted with your account.
• Public fan ranking rows: Scheduled to expire 12 months after the relevant season ends. Firestore TTL deletion is asynchronous and normally completes within approximately 24 hours after expiry. Disabling public visibility or deleting your account triggers immediate server-side removal instead of waiting for TTL.
• Processed clap batches: Normally deleted automatically after 7 days. Short-lived rate-limit records are retained as needed for service integrity.
• Crash and analytics data: Retained according to Firebase/Google retention settings.
• Local economy data: Stored on your device and removable by clearing app data or uninstalling the app.

7.1. Account Deletion

You can request account deletion at any time. For detailed instructions, visit our Account Deletion page.

8. Children's Privacy

Clap Stars is intended for users over 13 years old. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has used the app and provided personal information, contact us so we can delete it.

9. Your Rights

Depending on your location, you may have the right to:

• Access the personal data we store about you.
• Request correction of inaccurate data.
• Request deletion of your account and associated personal data.
• Object to or restrict certain processing.
• Withdraw consent where processing is based on consent.

10. Changes to this Privacy Policy

We may update this Privacy Policy occasionally. We will update the "Last updated" date when changes are made. Significant changes may also be communicated in the app where appropriate.

11. Legal Compliance

We aim to comply with applicable privacy requirements, including Google Play policies, the General Data Protection Regulation (GDPR), Spanish data protection legislation (LOPDGDD) and other applicable laws. We may disclose information if required by law or to protect our rights, users or service integrity.

13. Transparency

We believe in total transparency. This policy is written in clear language so you understand exactly what we do with the data. If anything is unclear, don't hesitate to contact us.