Pulsar Privacy Policy

This Privacy Policy explains how Pulsar collects, uses, stores, and shares information when you use the Pulsar mobile application. It is written to support production release readiness for Apple App Store and Google Play review and should be updated whenever the app's data practices, SDKs, or permissions change.

Information We Collect

Pulsar does not currently ask users to create a traditional account with a name, email address, or password. Instead, the app uses anonymous Firebase Authentication to assign a backend identifier and then stores gameplay-related data connected to that identifier.

• Anonymous account identifier: a Firebase-generated UID used to associate backend records and analytics events with a returning player session.
• Gameplay profile data: XP, rank, coin balance, highest score, highest sector, games played, lifetime sectors completed, ads watched, total words played, nexus activations, streaks, milestone claims, and record-setting words and scores.
• Usage and telemetry data: session IDs, app version, timestamps, local time zone, local hour and day, tutorial flow data, sector progression, power-up usage, daily challenge activity, ad reward events, and similar interaction events.
• Crash and diagnostics data: crash reports, error traces, and contextual keys such as rank, sector, round, app version, and session ID when a failure occurs.
• Configuration data: feature flags and balance settings delivered through Firebase Remote Config.
• Local device data: session timing and counters stored locally through SharedPreferences to support analytics continuity and app behavior.

How We Use Information

• To operate the app, persist progression, and restore a player's gameplay profile across launches.
• To analyze gameplay behavior, product stability, and feature adoption through Firebase Analytics and related telemetry events.
• To detect, diagnose, and fix crashes or technical issues using Firebase Crashlytics.
• To remotely adjust gameplay balance, feature availability, reward values, and operational settings using Firebase Remote Config.
• To support rewarded and interstitial advertising flows through the Google Mobile Ads SDK.
• To monitor abuse, protect the service, and maintain the integrity of game progression systems.

Firebase and Backend Services

Pulsar relies on Firebase as a core backend service layer. Firebase may process data on infrastructure operated by Google or its subprocessors. Based on the current codebase, Pulsar uses Firebase Authentication for anonymous sign-in, Cloud Firestore for user profile and progression storage, Firebase Analytics for event logging, Firebase Crashlytics for crash reporting, and Firebase Remote Config for feature and balance delivery.

Because Firebase is central to the app's production operation, iOS and Android production disclosures should clearly describe that backend identifiers, gameplay data, analytics events, and crash diagnostics are transmitted to Google Firebase services.

Advertising and Monetization

The app includes the Google Mobile Ads SDK and contains rewarded-ad and interstitial-ad flows. When ads are loaded, displayed, or completed, advertising partners may collect or receive device, network, and ad-performance information according to their own privacy notices and platform policies.

If Pulsar later enables personalized advertising, app tracking, advertising ID usage, or cross-app measurement beyond the current implementation, this Privacy Policy, App Store Nutrition Label disclosures, Google Play Data safety responses, and any required in-app consent flows should be updated before release.

Platform and Device Permissions

As currently configured in the reviewed repository, Pulsar requires internet access to communicate with Firebase services and ad infrastructure. The current project files do not indicate collection of contacts, precise location, photos, camera input, or microphone audio, and they do not currently include App Tracking Transparency permission text in the iOS configuration.

• iOS production note: if future builds use tracking, notifications, camera, microphone, photos, or location, the relevant Info.plist usage descriptions and privacy disclosures must be added before submission.
• Android production note: if future builds use additional sensitive permissions or advertising identifiers in new ways, the Android manifest and Google Play disclosure answers should be updated to match.

How We Share Information

Pulsar may share information with service providers that support hosting, analytics, crash reporting, remote configuration, and advertising. In the current implementation, those providers include Google Firebase services and Google Mobile Ads. Pulsar may also disclose information when reasonably necessary to comply with law, enforce terms, protect users, or prevent fraud or abuse.

Data Retention

Pulsar retains information for as long as reasonably necessary to operate the app, maintain progression records, analyze performance, resolve support or security issues, and satisfy legal obligations. Retention periods may differ depending on the data type, the storage system involved, and whether deletion is technically available for anonymous accounts.

Data Security

Pulsar uses commercially reasonable measures to protect information, but no mobile app, network transmission, or cloud platform can guarantee absolute security. Users should understand that backend and advertising services may apply their own technical and organizational safeguards as separate service providers.

Children's Privacy

If Pulsar is directed to children or made available in child-directed contexts, additional compliance review may be required, including review of SDK suitability, ad settings, analytics behavior, and parental notice or consent obligations. Unless and until that review is complete, the app should not be described as designed for children under the minimum age required by applicable law.

Your Choices and Rights

1. You may stop using Pulsar at any time.
2. You may reset or remove the app from your device, although some backend data associated with an anonymous identifier may remain until deleted through backend operations or retention processes.
3. You may use device-level settings that affect advertising, analytics, or privacy controls where supported by your mobile platform.
4. If Pulsar later offers direct support contact or account-linked deletion tools, this section should be updated to explain those options clearly.

International Processing

Backend and service-provider processing may occur in countries other than the country where a user is located. By using Pulsar, users understand that their information may be transferred to and processed in jurisdictions that may have different data-protection laws.

Changes to This Privacy Policy

Pulsar may update this Privacy Policy from time to time. When material changes are made, the effective date should be revised and any additional notice required by law or platform policy should be provided.

Contact Information

Before production launch, replace this paragraph with a monitored support or privacy contact email and, if applicable, the legal entity name responsible for Pulsar. App store reviewers generally expect a real contact method to be available in the policy before submission.

Production Disclosure Snapshot