Privacy Policy

Last updated: November 1, 2026

Liquid Coffee is operated by Mert Pekdüzgün. This policy explains the information used for coffee discovery, your private journal, accounts, subscriptions and advertising. Contact help@liquidcoffee.co about your data or privacy choices.

1. Your private journal

Tasting notes, recipes, aromas and brewing equipment saved in your journal are stored on your device. When iCloud is available, the app uses Apple CloudKit to synchronize journal data through your iCloud account. Journal entries are not automatically published as coffee reviews or uploaded to our account database. You choose when to export or share a journal entry; the recipient then receives the information in that export.

Your private journal and your public coffee reviews are separate. Signing out or deleting a Liquid Coffee account does not automatically delete your device or iCloud journal. You can delete journal entries in the app and manage iCloud data through Apple’s settings.

2. Accounts, profiles and coffee reviews

You can browse coffees and keep a journal without a Liquid Coffee account. If you sign in with Apple or Google, we receive the provider identifier and the name and email address made available by that provider. Apple may provide a private relay address. We use account identifiers and authentication tokens to maintain your session and secure account features.

We store the username, display name, optional bio and profile photo you choose to save. When you post a coffee review, its rating, text and any brewing details you include are stored with your account. Reviews and public profile information may be visible to other users. Profile photos are processed to resize the image and remove image metadata.

Saved coffees and equipment may be transferred to your account when account-library features are available. Public profile, collection, equipment and follow features can make those account details visible to others; the private tasting journal remains separate. Blocks and reports are used to restrict access and investigate abuse. Do not include information in public profile fields or reviews that you do not wish to share.

3. Subscriptions and purchases

Apple handles payments. We do not receive your full payment card details. RevenueCat processes purchase and subscription information, product identifiers, entitlement status and an app user identifier so we can provide Pro access, restore purchases and respond to subscription changes. Deleting your Liquid Coffee account does not cancel an Apple subscription. Manage or cancel it through your App Store subscription settings.

4. Optional analytics, diagnostics and notifications

In version 1.3.0 and later, optional usage analytics are off until you enable them. Firebase Analytics and Amplitude receive app interactions, device/app version information and pseudonymous identifiers when analytics are enabled. This can include categorical information about discovery, journal usage, purchase flows and aggregate journal counts. Private tasting text and photos are not included in these usage events. You can change this choice in Settings; disabling analytics stops new optional analytics collection but does not itself erase information already collected.

Firebase Crashlytics processes crash reports and technical diagnostics to help us find and fix failures. Crash diagnostics are separate from optional usage analytics. If you enable notifications, Firebase Cloud Messaging and our notification service use a device token and notification preferences to deliver messages. You can change notification choices in the app and in iOS settings.

5. Advertising and advertising choices

The free version may display Google AdMob ads. Pro removes in-app ads. In version 1.3.0 and later, we request non-personalized ads and disable Google’s publisher first-party ID. We do not ask for permission to track you across other companies’ apps and websites.

Non-personalized ads still involve data processing. Google may process IP-derived approximate location, device and app information, ad interactions and diagnostic information for ad delivery, measurement, fraud prevention and security. Non-personalized does not mean that no data is collected.

In version 1.3.0 and later, Google’s User Messaging Platform checks which privacy messages apply in your region before ads are requested. Where required, it presents your choices. Advertising choices are separate from optional usage analytics. You can reopen the advertising-choice form from Settings when it is available for your region. If the check fails, the app remains usable and does not request new ads until a successful check.

See how Google uses information from partner apps and Google’s advertising controls.

Older versions may use the previous advertising flow and may collect usage analytics without the in-app choice introduced in version 1.3.0. The new regional advertising form and analytics controls require the updated app. This policy also covers data processed by those older versions.

6. Location, network requests and support

The app may ask for device location to help select coffee catalog content. You can decline location permission or choose a country manually. Apple’s geocoding service converts the device location into a country code; we retain the country selection, not the device coordinates, for this feature. Network services receive your IP address as part of a request, and the backend may infer your country from it. We do not add precise device location to advertising requests.

Catalog searches are sent to our service to return matching coffees. Server access logs can contain the search terms, requested URL, IP address and technical request details. We use these operational records to provide, protect and troubleshoot the service.

When you contact support, we receive your message, contact details and attachments you send. Please avoid sending passwords or information you do not want us to receive. Operational servers process request and security information needed to run and protect the service.

7. Service providers and international processing

We use Apple (sign-in, iCloud and purchases), Google (sign-in, Firebase and AdMob), RevenueCat (subscriptions), Amplitude (optional analytics), Railway and Neon (backend hosting and database). Providers may process data on servers outside your country under their applicable terms and safeguards. AI features are retired in the new client; older versions may still send submitted questions and selected images through our backend to OpenAI when those legacy services remain available.

8. Retention, deletion and your choices

We retain account information while it is needed to provide your account and associated features. You can request account deletion in Settings → Account; provider reauthentication may be required. Account deletion removes account/profile information and associated reviews according to the deletion flow. Backup copies, purchase records, security records or information required for legal obligations may remain for the applicable retention period. We do not promise that deleting an account immediately erases every provider’s independent records.

In version 1.3.0 and later, open Profile → Settings to change usage analytics or open the regional advertising-choice form when available. Manage location and notification permission in iOS Settings. To delete private journal content, delete the entries in the app and manage their iCloud storage separately. For account deletion or a data request, use the in-app account deletion action or contact us below.

You can request access, correction or deletion, or ask about the applicable retention period, by contacting help@liquidcoffee.co. Depending on your location, you may also have rights to portability, restriction or objection and to complain to your data protection authority. Withdrawing consent does not affect processing that took place before withdrawal. We may need to verify your identity before fulfilling a request.

9. Security and changes

We use authenticated access and encrypted network connections to protect information. No service can guarantee complete security. We update this policy when our practices change and will provide additional notice where required.