Privacy in the Brain Froggy app
What the app on your phone collects, why it collects it, and who else sees it. Short, plain, no legalese theatrics. The website has a separate policy at /privacy/.
Last updated: 2026-06-07
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 are the same company that runs 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.
What this policy covers and what it doesn't
This document covers the Brain Froggy mobile app on iOS and Android. It does not cover this website (read /privacy/ for that). It also does not cover Apple and Google as billing controllers. When you buy a subscription, the App Store or Google Play handles your payment card, your tax address, and your invoicing. We never see that data. Apple's and Google's privacy policies cover the billing relationship; this page covers everything else.
What the app collects
Six things, named explicitly. Firebase Analytics records anonymous app-usage events and session counts (which screens you open, how often). Firebase Crashlytics sends a stack trace, a Firebase install ID, your device model, and your OS version only when the app crashes. APNs (on iOS) or FCM (on Android) holds the device token we need to deliver a push notification, and you opt in by tapping Allow on the system prompt. Apple App Store and Google Play in-app purchases give us an anonymous receipt that proves you paid; the app never sees your card. Apple Sign-In, if you use it, gives us an opaque subject identifier we use only to restore your purchase across devices through StoreKit. Everything else (your breath sessions, your history, your settings, your preferred hat) lives in on-device storage, which means SQLite and local files, and is never sent to any server we operate.
Why we collect it (and the legal basis)
Different data, different reason, different basis under GDPR Art. 6. Firebase Analytics and Crashlytics fall under Art. 6(1)(f), our legitimate interest in improving the app and diagnosing crashes; you can switch both off in Settings inside the app. The in-app purchase receipt falls under Art. 6(1)(b), performance of a contract, because we need it to deliver the paid features you bought. Push notifications fall under Art. 6(1)(a), your consent. The iOS or Android system prompt is the consent moment, and you can revoke it any time in your OS settings. The Apple Sign-In subject identifier also falls under Art. 6(1)(b), contract, because without it we can't restore the purchase you paid for on a new device. The on-device data isn't processed by us as controller at all; it never leaves the device.
Who else sees your data
Two companies, named with the country they're based in. Google LLC (United States) processes Firebase Analytics, Firebase Crashlytics, and FCM push delivery on our behalf. Apple Inc. (United States) processes APNs push delivery, App Store in-app purchases, and Apple Sign-In on our behalf. That's the full list. No ad networks. No analytics middlemen. No third-party SDKs beyond the ones named here. If we ever add a new processor we update this page and bump the last-updated date at the top.
Transfers outside the EEA
Both Google and Apple process the data above in the United States. The transfer rests on the EU Standard Contractual Clauses (SCCs) that we have in place with each provider, plus the adequacy frameworks Apple and Google publish for their own services. The published documentation for each vendor lays out the safeguards in more detail than we can usefully repeat here; you can find it on their websites under the privacy or data-processing pages.
How long we keep things
Firebase Analytics events follow Firebase's default retention window (14 months at the time of writing; the Firebase console is the source of truth if Google changes the default). Firebase Crashlytics keeps a crash event for 90 days from the moment it happened. The in-app purchase receipt entitlement lives for the lifetime of your subscription, plus whatever period Apple or Google retain the receipt on their billing servers under their own policies. The Apple Sign-In subject identifier stays with us until you delete the app and revoke access from your Apple ID settings. The push notification token survives until you uninstall the app or revoke notification permission in your OS. On-device data is gone the moment you delete the app from your phone.
Your rights
Under GDPR Art. 15 to 22 you can ask for access, rectification, erasure, restriction of processing, portability, and you can object. To exercise any of these, write to hello@wecodemobile.com from the address you want us to match against. Honest scope note: we have very little tied to a personal identifier. Most Firebase events are anonymous, and the install ID is unlinkable to you on our side, so in many cases there is simply nothing to hand over or delete. You can withdraw push consent in your OS settings at any time. The fastest erasure path is to uninstall the app: the on-device data is gone immediately, the Crashlytics install ID becomes unlinkable, and Apple or Google keep the IAP receipt under their own retention rules.
Children
The Brain Froggy app is not directed at children under 16. The App Store and Google Play age-rating gates apply at the store level. We do not knowingly process data from children under 16; if you are a parent or guardian and you 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. The data controller, again, is WeCodeMobile, ul. Potęgowska 20/40, 80-174 Gdańsk, Poland; the contact email is hello@wecodemobile.com. The last-updated date at the top of this page is the honest signal that something changed. We don't send emails about policy updates because we have no mailing list, so re-read this page when the date moves.