Privacy in the Brain Froggy app

What the app on your phone collects, why, where it goes, and how to get it deleted. Plain words, no legalese theatrics. The website has a separate policy at /privacy/.

Last updated: 2026-10-05

Who we are

The data controller for the Brain Froggy mobile app is WeCodeMobile, ul. Potęgowska 20/40, 80-174 Gdańsk, Poland. You can reach a person on our team at hello@wecodemobile.com. We also run this website, but the app is a different product with different data flows, so it gets its own document. The website policy at /privacy/ covers brainfroggy.wecodemobile.com; this page covers the app on your phone.

No accounts, one anonymous ID

Brain Froggy has no sign-up and no login. On first launch the app quietly creates a random anonymous identifier through Firebase Authentication. It is not tied to your name, email address or phone number. Everything we keep in the cloud is filed under that identifier. On iPhone, a small recovery key is stored in your device Keychain so the app can reconnect to the same identifier after a reinstall; the Keychain survives uninstalling the app. On Android the key sits in the app's private storage and is removed when you uninstall, unless Android's own app backup restores it. From app version 1.0.2, that Android backup contains only the app's preferences file, which holds this key, and the local database described below.

What stays on your phone

The app keeps a local database on your device with your settings, your reminder schedule, your session history, your unlocked hats and your onboarding answers. The home screen widget and, on iPhone, the Live Activity read from that local data. Deleting the app deletes this database.

What we back up to the cloud

While you have an active trial or subscription, the app backs up a copy of that data to Google Cloud Firestore, so your progress survives a new phone or a reinstall. The backup holds your onboarding answers (whether you have used breathing or relaxation apps before, how often you get brain fog or headaches, the time your brain fog usually starts, how you heard about Brain Froggy including an influencer name if you typed one, and a referral code if you entered one), your session count and session dates, your install date, which hats are unlocked and which one you wear, your settings (theme, frog colours, font size, high contrast, dyslexia-friendly font, sound, haptics, language) and whether your subscription is active.

Reminders and Live Activities

To keep your reminders on time, the app saves your reminder schedule in Firestore: the start time, how many reminders you want in a day, your time zone and whether your subscription is active. On iPhone it also saves the push tokens Apple issues for Live Activities. Our Cloud Functions, running on Google Cloud in the Warsaw region, use those tokens to start and update your Live Activity through Apple Push Notification service (APNs). Regular reminder notifications are scheduled on your device. You give or refuse notification permission in the system prompt and can change it any time in your phone settings.

Your answer about brain fog and headaches

One onboarding question asks how often you get brain fog or headaches. That answer is health-related information, so we treat it with extra care. Answering is optional: the question comes with a short consent note and a "Prefer not to say" choice, and you can also continue without picking anything. If you answer, you give us your explicit consent (GDPR Art. 9(2)(a)) to store it and use it to tailor your reminders and, anonymously, to improve the app. We never use it for advertising, never sell it, and Brain Froggy does not diagnose anything. You can withdraw that consent at any time by asking us to delete your data (see /delete-data/).

Onboarding statistics

To see where people get stuck in the first-run screens, the app writes one statistics record per install to Firestore. It contains a random install number (separate from your anonymous user ID), the screens you reached and how long they took, your onboarding answers, whether you allowed notifications, how you heard about us (only whether you typed an influencer name, not the name itself), whether you entered a referral code, whether you started a subscription and which plan, plus the app version, platform and device language. Because the install number is not linked to your user ID, we cannot find this record on request; we delete these records after 24 months.

Usage analytics, crashes and performance

Firebase Analytics records app events such as opening a screen, finishing onboarding, starting a trial or tapping a reminder setting. It uses an app instance identifier. From app version 1.0.2 the app does not collect the advertising ID on iPhone or Android; earlier versions read the Android advertising ID through Firebase Analytics but never used it for advertising, and Brain Froggy shows no ads. Firebase Crashlytics sends a crash report (stack trace, device model, OS version, a Crashlytics install ID) when the app crashes. Firebase Performance Monitoring measures things like app start time and how long network requests take. Firebase App Check uses Google Play Integrity on Android and Apple App Attest on iPhone to confirm that requests to our backend come from the genuine app.

Subscriptions and purchases

Google Play and the App Store handle your payment, card details, billing address and invoices. We never see your card. RevenueCat, our subscription service, receives the store receipt and your subscription status, linked to your anonymous ID, so the app knows which features you paid for and can restore them on a new device.

Messages you send us

When you use Share feedback in the app's settings, we store your email address, your message, the message type (Feature idea, Bug or Translation), your app language, app version, platform and your anonymous ID in Firestore. We use them only to read your message, reply to you, and act on what you asked for. The form attaches your anonymous ID automatically from app version 1.0.2; messages sent from older versions arrive without it.

Why we use it (and the legal basis)

Cloud backup, reminders, Live Activities and subscription handling fall under GDPR Art. 6(1)(b), performance of our contract with you: they are the features you use. Notification delivery relies on your consent, Art. 6(1)(a), given in the system prompt. Your brain fog and headache answer relies on your explicit consent, Art. 9(2)(a). Analytics, onboarding statistics, crash reports, performance monitoring and App Check fall under Art. 6(1)(f), our legitimate interest in keeping the app working, secure and getting better. Feedback messages fall under Art. 6(1)(f) too: answering you.

Who else processes your data

Three companies process data for us, and only on our instructions. Google LLC (United States) and Google Ireland Limited run Firebase (Authentication, Firestore, Cloud Functions, Analytics, Crashlytics, Performance Monitoring, App Check), Play Integrity and Google Play billing. Apple Inc. (United States) runs APNs, App Attest and App Store billing. RevenueCat, Inc. (United States) runs subscription status and receipt validation. We do not sell your data, we do not share it with advertisers or data brokers, and there are no ad SDKs in the app. If we add a processor, we update this page and the date at the top.

Transfers outside the EEA

Some of the data above is processed in the United States by Google, Apple and RevenueCat. These transfers rest on the EU Standard Contractual Clauses and, where the provider is certified, on the EU–US Data Privacy Framework. Each provider publishes the details in its own privacy and data-processing terms.

Security

All traffic between the app and our services goes over HTTPS with TLS encryption. Firestore security rules let each anonymous ID read and write only its own records. Google encrypts the data at rest. On your phone, the data sits in the app's private storage, protected by your device's own encryption and lock screen.

How long we keep things

Cloud backup and reminder data stay until you ask us to delete them. Onboarding statistics records are deleted after 24 months. Feedback messages are kept until we have handled them and for at most 24 months after that. Firebase Analytics keeps events for 14 months. Crashlytics keeps crash reports for 90 days. Performance Monitoring data follows Google's default retention. RevenueCat keeps purchase records for as long as your subscription exists and as long as accounting rules require; Apple and Google keep their billing records under their own policies. On-device data is gone when you delete the app, except the iPhone Keychain recovery key described above.

Your rights and deleting your data

Under GDPR Art. 15 to 22 you can ask for access to your data, correction, erasure, restriction of processing and portability, and you can object to processing based on legitimate interest. To delete your data, follow the steps at /delete-data/: the quickest route is Settings → Share feedback inside the app, which attaches your anonymous ID so we can find your records. The form attaches the ID from app version 1.0.2; on an older version, update the app first or write to us by email as described there. For anything else, write to hello@wecodemobile.com. We answer within one month.

Children

The Brain Froggy app is not directed at children under 16. We do not knowingly process data from children under 16. If you are a parent or guardian and believe we have, write to hello@wecodemobile.com and we will delete what we can find.

Complaints, contact and the date stamp

You have the right to lodge a complaint with the Polish data protection authority, PUODO (Prezes Urzędu Ochrony Danych Osobowych), at https://uodo.gov.pl, or with the authority in your own EU country. The data controller is WeCodeMobile, ul. Potęgowska 20/40, 80-174 Gdańsk, Poland; email hello@wecodemobile.com. The last-updated date at the top of this page tells you when something changed. We have no mailing list, so re-read this page when the date moves.