Privacy Policy

Last updated: October 1, 2026

phrodia helps you choose photos with confidence through structured feedback from other people. This policy explains how we use personal data to deliver that experience and how you can manage your choices when you use the website, the mobile and web apps, shared photo links, the Photo Feedback API and support services. The Cookie Policy gives more detail about browser storage, analytics and advertising technologies.

1. Who is responsible for your data?

Marsrock — Pascal Maurice Philipp (owner)
Feldmochinger Str. 217b
80995 Munich, Germany
Email: info@phrodia.com

See the Impressum for provider information. You can use the same contact for privacy questions and requests concerning your data.

2. Data used to provide phrodia

Account and profile

When you sign in with Google, or Apple on iOS, we process the account identifiers and profile information provided by that sign-in service. Your phrodia profile includes your user ID, email address, display name, date of birth or age information, gender, profile photo where provided, setup status and settings. Profile and demographic information supports account management, age checks, audience matching and feedback insights.

phrodia is for people aged 16 and over. If you believe someone under 16 is using the service, report the account or contact us.

Photos, tests, feedback and conversations

We process uploaded photos, the selected Dating, Social, Business or Fitness test, the three criterion responses, the derived overall score, comments, audience settings and activity timestamps. We also process chat requests, messages, shared chat images, blocking preferences and reports where you use those features.

Profile information and feedback needed for an interaction can be shown to other participants. Photo owners can see received feedback and available demographic and city-level information about raters. Messages and chat images are made available to the conversation participants. Authorized operational or moderation access is described below.

API access and connected assistants

If you connect an assistant or another integration to the Phrodia Photo Feedback API, we process your account identifier, connection and key records, uploaded photos, test settings, approval records, credit balance, results and purchase status as needed for the features you request. API onboarding uses Google sign-in; it does not require you to add a name, date of birth, gender or country to a new profile at that step. Existing account information remains subject to this policy.

The integration you authorize can retrieve your available credit balance and API-test results, upload photos, prepare and cancel tests, prepare sharing requests, retrieve shared-photo feedback, obtain your invitation link and prepare a credit checkout. The account response also includes your user identifier and first name where already present. Publication of a test and activation of a public photo link each require your separate approval in the browser. Payment is confirmed separately in Stripe Checkout. We record approval timestamps and the applicable consent-version identifier.

Your selected assistant or integration provider receives the information you give it and the API responses it requests, which can include photo identifiers, scores, comments, sharing links, invitation codes and purchase status. Its own terms, privacy policy and storage practices also apply to its handling of that information. Revoking Phrodia access stops future authenticated API access; it does not erase copies already held by the integration or cancel tests already started.

You can create a personal key or revoke all your connector keys on the API access page. Keys expire after 30 days. Creating a replacement does not revoke earlier keys. Phrodia stores key hashes and associated access records; enter a personal key only in your integration's secure credential field. Do not send it in chat, email or support screenshots.

Website quick tests without registration

Where the guest quick test is available, we create a technical guest identifier and store access credentials in your browser. These connect your photo and results to your browser session. Registration can retain those results for access on other devices. Clearing browser data before registration can remove your access.

We use Cloudflare Turnstile to check for automated requests before issuing a guest test. Cloudflare processes the IP address and browser/device signals needed for this security check. Photos are uploaded to our existing Firebase storage and moderation services, not to Turnstile. We also keep keyed hashes of network addresses with daily usage counters to limit repeated free tests. The counters are scheduled for deletion after three days; expiry does not necessarily mean immediate physical deletion. See Cloudflare's Turnstile Privacy Addendum.

Location

With the relevant device permission, phrodia uses location coordinates to determine geographic information for audience matching and location-based insights. Coordinates may be processed by the device's geocoding service and, when needed, our backend geocoding service.

The current account setup stores a city, country, region, a coarse geographic identifier and, where available, city-centre coordinates. The map uses city-level information about raters. Precise coordinates are used for this geographic lookup. You can manage location permission in your device settings.

Shared links and browser ratings

When you share a photo, people with its link, QR code or rating code can access the shared photo and associated results. You choose when to share a photo. Anyone who receives a forwarded link or code can also use it; in-app audience filters apply to community distribution within phrodia.

Browser ratings can be submitted without a phrodia account. We process the responses, optional comment and demographic information, the photo/share identifier and submission time. We also use an IP-derived identifier and request information to limit repeated submissions and abuse. This supports convenient participation while helping protect the quality of feedback.

Credits and purchases

We process balances, reward activity, credit expiry, spending records, referral information and purchase or refund events to operate the wallet. Apple or Google processes mobile payments; RevenueCat supports purchase validation and delivery of credits.

RevenueCat receives the app user identifier and purchase-related information, including store transaction and product information, together with technical information needed by its SDK. The user identifier can be linked to your phrodia account. Payment card details are entered through the store's payment process rather than a phrodia payment form.

Web credit purchases: Stripe hosts checkout and processes the payment, including Link where selected. We send Stripe your Phrodia account identifier, order reference, package and transaction details. Stripe collects the payment, contact and billing information needed for checkout, tax calculation, fraud prevention and its payment services. Payment details are entered on Stripe's checkout page. Phrodia receives transaction information and keeps order, payment-status, credit-delivery and refund records linked to your account. RevenueCat receives your account identifier and Stripe checkout reference to track the purchase.

Notifications and support

We process device notification tokens and preferences to deliver notifications. Transactional and activity emails can include account or activity information relevant to the message. Support requests include your contact details, message and any attachments you choose to send. Send only the information needed to explain your request; do not send passwords or full payment card details.

3. Moderation, security and operations

Photo uploads and chat images can be processed by Google Cloud Vision for content checks. These content checks support moderation; account eligibility and reports are handled separately. Flagged content and reports can be reviewed by authorized administrators.

Reports contain information identifying the reporter, the reported content or account, the reason and supporting details. phrodia uses this information to assess the report. The reporting feature keeps the reporter’s identifiers out of the information shown to the reported user.

We also process technical request information, diagnostic logs and activity or transaction records to operate the service, investigate errors and prevent abuse.

Operational communication: Activity notifications support service administration through third-party messaging services used for internal operations. Where enabled, notifications about accounts, uploads, ratings, purchases and conversations can include user identifiers, profile or demographic details and uploaded photos. The messaging providers receive and process the information included in those notifications. Contact us for details about the recipients, operational access or a request concerning your data.

4. Analytics, advertising and local storage

The public website uses Google Analytics 4 and Google Ads tags. It also measures store-button activity. The apps use Firebase Analytics and advertising integrations such as AdMob or AdSense where available. Depending on the service and settings, these technologies can process device or browser information, online identifiers, IP addresses, viewed pages/screens, interactions, advertising events and consent choices.

The website uses Google Consent Mode and a consent banner. Accepting the current website banner enables both analytics and advertising-related consent settings. In the regions covered by the tag's default restrictions, those settings initially remain denied. In that state, Google Consent Mode can send cookie-free requests containing technical information and consent or measurement signals, including personal data such as an IP address.

The Cookie Policy explains the website and app controls separately. Device tracking permission, advertising consent and account deletion serve different purposes.

5. Purposes and legal bases

Where the GDPR applies, the relevant bases depend on the purpose:

• Providing requested services — Article 6(1)(b): account access, photo tests, delivery of feedback, conversations, wallet and purchase handling.
• Consent — Article 6(1)(a): optional processing where consent is requested, including relevant analytics and advertising uses. You can withdraw consent for future processing.
• Legitimate interests — Article 6(1)(f): necessary and proportionate security, fraud prevention, handling reports, diagnosing problems and protecting the service and its users, subject to the balancing of those interests against your rights.
• Legal obligations — Article 6(1)(c): records or disclosures that applicable law requires.

Access to or storage of information on your device is also subject to the applicable rules on terminal equipment, including § 25 TDDDG in Germany. Consent applies to optional analytics or advertising storage where required by those rules.

Providing the account and feature information needed for a service enables us to deliver it. Optional comments, shared links and optional permissions depend on your choices; declining a permission can affect the feature that needs it.

6. Recipients and service providers

Data is made available to recipients according to the feature and purpose:

Providers may act as processors or as independently responsible providers depending on the service. Their published policies include Google, Firebase, Apple, RevenueCat, Stripe and Resend.

Some providers operate internationally, so processing may take place outside your country or the EEA. Where required, international transfers must have an applicable legal transfer mechanism, such as an adequacy decision or appropriate contractual safeguards. Contact us for information about the providers and safeguards relevant to your data.

7. Retention and account deletion

API access and photos: Connection requests expire after 15 minutes and personal keys after 30 days. Private API uploads and unapproved test drafts expire after 24 hours. An hourly cleanup job removes expired private upload files and expired connection/key records in batches. API-test image retention is scheduled for 30 days from test creation; cleanup closes the test, disables sharing and removes its approved image files. Processing can take longer if a cleanup run fails or has a backlog. Test metadata and transaction records have separate purposes and are not all deleted by this image-cleanup job.

Disabling a public share link stops future access through that sharing feature and removes its public lookup/cache records; feedback already received remains associated with the photo. This does not remove copies a recipient has already saved. Revoking keys, cancelling a test and deleting an account are separate actions. Contact us for deletion requests covering other retained records or copies held by connected services.

Account and content data is held to provide the service while your account and content remain active. You can delete a photo or request account deletion. The deletion process covers your account, photos, ratings, conversations and related operational data; requests may require follow-up cleanup across connected services.

In the app: Profile → Settings → Delete Account.
Without the app: email info@phrodia.com with the subject “Delete Account” and your account email or user ID. You do not need to reinstall the app. See the account deletion instructions.

Deletion is permanent. Purchase and transaction records may need to be retained to meet applicable accounting or other legal obligations. Security, support and dispute records may be retained where necessary for their specific purpose. Truly anonymous statistics can remain. Stores and other independently responsible providers handle their records under their own retention requirements and privacy procedures.

We respond to data-rights requests without undue delay and normally within one month. Where an extension is permitted because of a request's complexity or number, we will explain it within that period. We may need reasonable information to verify that a request concerns your account.

Browser storage has its own lifetime, described in the Cookie Policy. You can remove it through browser settings. Provider-side records, backups and operational notifications must be handled according to their purpose and applicable retention requirements; contact us for details or a deletion request.

8. Your rights and choices

Subject to the applicable legal conditions, you can request access, correction, erasure, restriction and data portability. You can object to processing based on legitimate interests and withdraw consent at any time for future processing. Withdrawal does not affect the lawfulness of processing carried out before it.

Contact info@phrodia.com to exercise your rights or request a copy of your data. Device permissions can be changed in your operating-system settings. App advertising/privacy options are available in Profile → Settings; website controls are described in the Cookie Policy.

You may complain to a competent supervisory authority, including the authority in your place of residence, work or the place of an alleged infringement. For a private-sector provider based in Bavaria, the relevant regional authority is the Bayerisches Landesamt für Datenschutzaufsicht (BayLDA): information and complaint form.

9. Security and policy updates

We use encrypted connections, authentication and access controls to protect data. Access depends on the purpose: for example, a photo is shown to eligible raters, a shared photo is available through its link, and authorized administrators can handle support or moderation matters.

We update this policy when the service or its data processing changes. The date above identifies the current revision. Material changes will be communicated as required by applicable law.

Contact: info@phrodia.com · Impressum