Cookie Policy

Last Updated: April 27, 2026

What Are Cookies & Tracking Technologies?

Cookies are small text files stored on your device when you visit a website. Tracking technologies (including SDKs in mobile apps) are similar tools that help us understand how you use our Service.

This policy explains how phrodia uses cookies and tracking technologies.

Mobile App (iOS & Android)

Our mobile apps do not use browser cookies. Instead, we use SDK-based tracking technologies:

Firebase Analytics SDK

Purpose: App usage analytics, screen views, feature tracking

Data Collected:

• App opens and session duration
• Screen views (which screens you visit)
• Feature interactions (which buttons you tap)
• Device information (model, OS version)

Retention: 14 months (Firebase default)

Control: Profile Settings → Ad & Privacy Settings

Google AdMob SDK

Purpose: Display advertising (personalized & non-personalized)

Data Collected:

• IDFA (iOS): Identifier for Advertisers (requires ATT consent)
• AAID (Android): Google Advertising ID (requires UMP consent)
• IP address
• Ad interaction data (views, clicks)

Retention: Varies (managed by Google)

Control:

• iOS: Settings → Privacy → Tracking → phrodia (toggle off)
• Android: Profile Settings → Ad & Privacy Settings

Default: Non-personalized ads (no tracking) until you opt-in

RevenueCat SDK

Purpose: In-app purchase tracking, credit purchase management

Data Collected:

• Purchase confirmations
• Purchase status
• User ID (anonymous)

Retention: Duration of account + 10 years (tax requirements)

Control: Cannot be disabled (required for purchases to work)

Firebase Cloud Messaging (FCM)

Purpose: Push notifications

Data Collected:

• FCM push token (device-specific identifier)
• Notification delivery status

Retention: Until device logout or account deletion

Control:

• System: Device Settings → Notifications → phrodia
• App: Profile Settings → Notification Preferences

Website (phrodia.com)

Our public website at phrodia.com is a static marketing site. It does not require login and sets no session or authentication cookies. The only technologies used are Google Analytics 4 and a consent preference stored in localStorage.

Functional Storage (Always Active)

Purpose: Remember your consent choice so the banner does not reappear on every visit

This is not a cookie — it is stored in your browser's localStorage and is never sent to our servers.

Analytics Cookies (Google Analytics 4)

GA4 Measurement ID: G-G4Z0FCVQCB

EU/EEA/UK/CH users: Requires consent (opt-in via the cookie banner). No analytics cookies are set until you accept.

All other users: Set on the basis of legitimate interest (Art. 6(1)(f) GDPR).

What GA4 collects: Page views, session duration, app store button clicks (app_store_click event), browser/device info, and country derived from anonymized IP. No name, email, or personal data is collected from website visitors.

Control: Cookie consent banner (EU/EEA users) or clear browser cookies at any time.

Consent Management

Website (EU/EEA/UK/CH Visitors)

Cookie Banner: A consent banner appears on first visit if your device timezone indicates a European location (e.g., Europe/Berlin, Europe/Paris). This is a client-side heuristic — your timezone is checked locally in your browser and never sent to our servers.

Options:

• Accept: GA4 analytics enabled — we can see page view data and click events to improve the site.
• Decline: Only cookieless pings are sent to Google (no identifiable data stored, no GA4 cookies set).

Storage: Your choice is saved in localStorage key phrodia_consent_v2 (value: granted or denied). It persists until you clear your browser storage.

Withdraw: Clear your browser's localStorage for phrodia.com to reset your choice. The banner will appear again on your next visit.

Non-EU users: The banner does not appear. GA4 analytics run on the basis of legitimate interest. You can still block GA4 by using browser settings or an ad blocker.

Google Consent Mode v2: Regardless of your choice, IP addresses are anonymized and cross-site tracking is disabled. If you decline, Google receives only aggregate, cookieless data used for modeling — no personal data.

Mobile Apps

Android:

• Google UMP (User Messaging Platform)
• IAB TCF 2.2 Framework
• Consent dialog appears during onboarding

iOS:

• App Tracking Transparency (ATT) prompt
• Consent required to access IDFA for personalized ads

Default: Non-personalized ads until consent

How to Manage Cookies

Web Browsers

Chrome:

1. Settings → Privacy and Security → Cookies
2. Select "Block third-party cookies" or "Block all cookies"

Firefox:

1. Settings → Privacy & Security
2. Select "Strict" tracking protection

Safari:

1. Preferences → Privacy
2. Enable "Prevent cross-site tracking"

Note: Blocking all cookies may break app functionality.

Mobile Apps

iOS:

1. Settings → Privacy → Tracking
2. Toggle off "Allow Apps to Request to Track"
3. Find "phrodia" and toggle off

Android:

1. Settings → Google → Ads
2. Select "Opt out of Ads Personalization"
3. Or in-app: Profile Settings → Ad & Privacy Settings

Do Not Track (DNT)

We respect browser Do Not Track (DNT) signals:

• If DNT is enabled, we disable analytics and personalized advertising
• Necessary cookies still function

Cookie Duration

Auto-Deletion: Cookies are automatically deleted when they expire

Third-Party Privacy Policies

Our app integrates third-party services. Please review their privacy policies:

• Google (Analytics, AdMob, Firebase): https://policies.google.com/privacy
• Apple: https://www.apple.com/legal/privacy/
• RevenueCat: https://www.revenuecat.com/privacy

Note: We are not responsible for third-party practices.

Updates to This Policy

We may update this Cookie Policy from time to time. Changes will be reflected in the "Last Updated" date above.

Notification: We will notify you of material changes via in-app notification or email.

Contact Us

For questions about our use of cookies:

Email: info@phrodia.com
Subject: "Cookie Policy Inquiry"

Related Documents

• Privacy Policy - Full data protection details
• Terms of Service - Usage rules and conditions
• Community Guidelines - Content standards

Last Updated: April 27, 2026
Version: 2.1.0