🍪 Cookie & Analytics Policy

This policy explains the difference between how our marketing website (philiabit.com) uses cookies and how the Philiabit mobile app uses analytics SDKs. Since these are different technologies, we address them separately below.

Our website currently uses a minimal set of cookies:

• Strictly necessary — session and security cookies required for the site to function (e.g., remembering your cookie preference itself).
• Functional — remembering simple preferences like language, if applicable.
• We do not currently use third-party advertising or cross-site tracking cookies on philiabit.com. If that changes (e.g., adding a marketing pixel), we will update this policy and present a cookie consent banner where required by law (e.g., for EU/UK visitors).

Because we only use essential/functional cookies today, no consent banner is required in most jurisdictions — but you can still block or delete cookies at any time through your browser settings. Note that blocking strictly necessary cookies may affect basic site functionality.

The mobile app does not use browser cookies. Instead, it uses Firebase Analytics (a Google product) to collect event-based usage data — for example, when you join a challenge, complete onboarding, level up, or join a team. This helps us understand which features are working and where people get stuck.

Firebase Analytics data is tied to an app-instance identifier, not directly to your name, and is used in aggregate for product decisions — it is not used to build cross-app advertising profiles, and we do not sell it to data brokers or ad networks.

Separately from analytics, the app registers a device token with Firebase Cloud Messaging so we can deliver push notifications you've enabled. This token identifies your device for delivery purposes only and is described further in our Data & Permissions page.

Philiabit does not currently integrate third-party advertising SDKs, ad-attribution networks, or cross-app tracking tools (such as the advertising identifier for ad personalization). If this changes in the future, we will update this policy, request any legally required consent (e.g., iOS App Tracking Transparency), and provide an in-app opt-out before enabling such tracking.

• In-app: turn off Analytics sharing in Settings → Privacy at any time — see Privacy Settings.
• On the website: use your browser's cookie controls, or ask us at [email protected] if you have questions about a specific cookie.
• On iOS: analytics collection also respects the system-level "Allow Apps to Request to Track" setting where applicable to any future tracking SDKs.