Last updated: September 18, 2026
phrodia uses browser storage and app integrations to support sign-in, remember choices, collect feedback and measure service use. This policy distinguishes the public website, browser rating pages and the app. Read it with the Privacy Policy.
1. Cookies, local storage and app SDKs
Cookies are browser-held values that may be sent with web requests. Local storage and IndexedDB are other browser storage mechanisms. Local storage usually has no automatic expiry unless the application implements one or your browser removes it. Mobile SDKs can process device identifiers and events without using browser cookies.
Under § 25 TDDDG in Germany, storage or access that is not strictly necessary for a service you requested generally requires informed consent. The use of personal data also needs an applicable legal basis. These rules cover cookies and other forms of device storage or access.
2. Public website and browser rating pages
The public website includes Google Analytics 4 and Google Ads tags. It also uses local storage for choices and specific interactions:
| Name or pattern | Where and why it is used | Lifetime in the current implementation |
|---|---|---|
phrodia_consent_v2 |
Remembers the public website's consent choice (granted or denied) |
Until cleared by the browser or user; no automatic expiry is set |
rated_photos |
Remembers photos rated through browser links to avoid repeated submissions in that browser | Until cleared; no automatic expiry is set |
storeClick_* |
Prevents repeated counting of a store-button interaction from the same browser; the key can include the source, store and photo-share token | Until cleared; no automatic expiry is set |
_ga and _ga_* |
Google Analytics identifiers and session measurement when analytics storage is enabled | Controlled by Google's cookie settings and browser limits; the default Google Analytics duration can be up to two years |
| Google Ads cookies or identifiers | Advertising/conversion measurement where the relevant Google consent settings permit it | Depends on the Google service, configuration and browser restrictions |
The consent preference is stored in your browser; Google tags receive the corresponding consent signals. The inventory explains the purpose and lifetime of each browser-held value.
Photo links and codes identify the shared photo. Submitting a browser rating also sends the answers, optional comment and demographic information, and technical request information to the backend. An IP-derived identifier is used to help prevent repeated ratings. See the Privacy Policy for that server-side processing.
3. Website consent choices
The current public website offers Accept and Decline. Accept updates the consent settings for analytics storage, advertising storage, advertising user data and advertising personalization. Decline sets those settings to denied. The choice is remembered in phrodia_consent_v2.
For new visitors, the banner appears based on a European browser time zone, including Iceland. Google tags separately use region-based denied defaults for analytics and advertising in the EEA, UK and Switzerland. Outside those configured regions, analytics initially uses a granted setting and advertising uses a denied setting.
The tags are loaded even where storage consent is denied. Under Google Consent Mode, requests without analytics or advertising cookies can still be sent. These requests can include technical information, such as an IP address, together with consent or measurement signals.
Changing your choice: In the current website, remove phrodia.com's stored consent preference through your browser's site-data settings and return to the site to choose again where the banner is shown. Clearing all site data can also remove saved sign-in and rating information. Browser tracking protections can restrict additional requests. The public website preference and the app's privacy settings are separate controls.
4. Web app
The web app at /app uses Firebase Authentication and browser persistence to maintain sign-in. It also uses its own local consent settings, separate from the marketing website:
| Name | Purpose |
|---|---|
1to10_consent_status |
App consent state |
1to10_consent_timestamp |
Time at which the app choice was saved |
1to10_personalized_ads |
Saved advertising preference |
1to10_analytics_consent |
Saved analytics preference |
The app checks the saved consent timestamp against a 395-day validity period. After that period, the app reassesses the saved choice. Removing site data resets browser-held values, but does not itself delete your phrodia account or backend records.
Firebase and sign-in providers may use additional browser storage as part of authentication. Advertising features can also use Google AdSense and its consent tooling. Check the options shown in the app under Profile → Settings → Ad & Privacy Settings.
5. iOS and Android apps
The mobile apps integrate services that can process data without browser cookies:
- Firebase Analytics: app events, screen/activity information and device information for usage measurement.
- Google AdMob: advertising requests, device/advertising identifiers where available, IP addresses and ad interactions. Non-personalized ads use contextual information and can also process personal data for delivery, security and measurement.
- RevenueCat and the app stores: account-linked purchase and product information for processing credit purchases.
- Firebase Cloud Messaging: device notification tokens and related delivery information for notifications.
The mobile apps use Google's consent tooling where applicable. iOS tracking permission is a separate system choice. Manage app privacy options in Profile → Settings and notification, location or tracking permissions in your device settings. Permission availability and labels can vary by system version.
6. Storage and retention choices
Browser cookies expire according to their configured settings and browser rules. Local storage does not inherit a cookie expiry. Provider-side analytics, purchase, support and operational records have separate retention requirements and settings; browser deletion does not erase those records.
For account deletion or other data requests, use the account deletion instructions or contact info@phrodia.com.
7. Further information
Provider information: Google technologies and cookies, Firebase privacy, Apple privacy and RevenueCat privacy.
We update this policy when the relevant technologies or controls change. For questions, email info@phrodia.com.