Two product facts can both be true: Quit Alcohol keeps the drink log and personal tracking settings on the device, and the app uses external services for narrower functions. Firebase Analytics supports product-usage measurement. RevenueCat supports purchase entitlement handling. Google Play processes the store transaction. Understanding those roles is more accurate than calling the app either “cloud-based” or “completely offline.”
What Firebase Analytics is for
Product analytics can report app-interaction and device information so the team can understand whether screens or features are being used and functioning. That is different from operating an account that stores your calendar. The official privacy explanation should define the information involved and available controls. If you want to limit optional analytics, review device settings where available and the current policy for the supported choices.
What RevenueCat is for
RevenueCat helps the app determine whether a weekly or lifetime purchase entitlement is active. It needs purchase-related identifiers and status to perform that job, not the text of a journal or your daily drink history. Entitlement systems are why reinstalling or changing a store state may involve a network check even when the actual calendar is kept locally.
What Google Play is for
Google Play supplies the confirmed Android listing and handles the payment flow shown to you. Prices, taxes, renewal terms, cancellation choices, and refund rules are presented through the store. The app developer does not need to handle your card directly for an in-app purchase. Always review the live purchase screen because store terms and regional offers can change.
What these services do not make true
Their presence does not mean the Quit Alcohol website receives a copy of every alcohol entry. Conversely, local drink storage does not justify saying no information ever leaves the device. Keep the categories separate: personal calendar data, interaction or device analytics, and purchase or entitlement records. Clear categories help you ask useful privacy questions instead of relying on an absolute slogan.
How to evaluate a privacy claim
Prefer the official policy’s effective date, the current Google Play data disclosures, and direct support answers. Be cautious with reviews that describe an older build or infer behavior from a single network request. A trustworthy summary names the service, its purpose, and the boundary around the personal log. If those elements change, the official documentation should be updated.
What you can control on your device
Use Android privacy and notification settings, restrict lock-screen previews, protect the Google account used for purchases, and manage subscriptions or payment history through Google Play. Clearing local storage or uninstalling may remove the calendar, so do not use those as casual privacy experiments when you want to keep the record. Contact support before making a destructive change you do not understand.
Use precise language when asking for help
When contacting support, name whether the question concerns a local entry, an analytics choice, a Google Play charge, or an entitlement. These are different systems. A specific description, app version, device model, and non-sensitive purchase status can make troubleshooting clearer without sending the contents of your calendar.
Keep three data categories distinct
- Local drink entries and calendar settings
- App-interaction and device analytics
- Purchase, store, and entitlement information
Questions, answered
Does RevenueCat need my drink-count history?
Its stated product role is purchase entitlement handling, not storing the daily alcohol log.
Why might the app use a network connection?
Analytics, entitlement checks, store transactions, and store availability can require communication even with a local calendar.
Where should I manage a weekly purchase?
Use the subscription and payment controls associated with the Google Play account that made the purchase.