Your baking data — recipes, bakes, feedings, starters and photos — is stored only on your device and never leaves it. The app does send anonymous, aggregated usage and crash diagnostics to help us improve it; see the Usage Analytics and Crash Reporting sections below. We keep no account and no central record of your content.
Your recipes, bake sessions, and starter logs are stored in a local SQLite database on your device. This data never leaves your phone.
The Bake Log uses Google Firebase Analytics to understand how the app is used — which runs by default. We collect anonymous, aggregated interaction events (for example: a bake or feeding saved, a recipe or starter added, a guided bake started, a Baker's Mark earned, a screen opened, or a Premium purchase) plus the app-standard measures Firebase provides. These never include your recipes, notes, photos, or any content you enter — only that an action happened. Advertising personalisation is turned off, so this data is never used to target ads. In the EEA, the UK and Switzerland, analytics collection is governed by Google Consent Mode through the ad consent form shown on first launch; you can revisit that choice anytime via Settings → Manage Ad Consent.
Firebase Crashlytics collects anonymised crash and error diagnostics to help us fix bugs, under legitimate interest and separately from the analytics above. No personal data is included in these reports.
Google AdMob may collect limited data for ad targeting on the free tier. Upgrade to Premium to remove all ads.
Purchases are processed through Google Play (Android) or Apple App Store (iOS). We do not handle payment data directly.
All your data is yours. You can export or delete it anytime by uninstalling the app. We have no central record of your data.
For questions or concerns, contact: admin@eritech.studio