This policy covers the Brekk mobile app for Android, published by Stone Creek Apps
(“we”). The app’s package name is com.dailywell.fasting.
In short: Brekk has no accounts and no login. Your fasting history, weights, measurements, notes and photos are stored on your phone. A small number of features send data off the device, and each is listed below by name — most importantly, if you use the AI food scan, the photo you take is sent to Google for recognition.
The following is written to the app’s private storage on your phone. We have no server that receives it, and no way to read it:
Brekk participates in Android’s standard backup so that your history survives getting a new phone. This is handled by Android and your Google account, not by us.
| What | Cloud backup | Direct phone-to-phone transfer |
|---|---|---|
| Fasting history and all trackers | Included | Included |
| Profile and preferences | Included | Included |
| Fasting photos and profile picture | Not included | Included |
Photos are deliberately left out of cloud backup: Android caps an app’s backup size, and a large photo set would cause the whole backup to fail rather than just the photos. They do come across on a direct device-to-device transfer, which has no such limit.
You can turn backup off entirely for all apps in your device settings, and delete existing backups from your Google account.
Each of these is a separate service with its own privacy policy. Nothing here receives your fasting history.
| Service | When | What is sent |
|---|---|---|
| Google Firebase AI (Gemini) | Only when you use the AI food scan | The food photo you took, so it can be recognised and turned into a calorie estimate. Not your fasting data, and not photos you attach to a fast. |
| Open Food Facts | Only when you scan a barcode | The barcode number, to look up the product. Open Food Facts is an open, non-commercial food database. |
| Google Play Billing | When you buy or restore a subscription | Purchase tokens and subscription status. Card and payment details are handled by Google — we never see or store them. |
| Google Firebase Analytics | While you use the app | Pseudonymous usage events (which screens are opened, which features are used), an app instance identifier, and standard device data such as model, OS version, language and coarse region. No fasting entries, notes or photos. |
| Google Firebase Remote Config | Periodically | A request for the app’s current settings, so features can be adjusted or switched off without an update. It carries an app instance identifier and basic device data. |
| Google Play Integrity (App Check) | Before an AI scan | An attestation that the request comes from a genuine, unmodified copy of the app. This exists to stop other people running up our AI bill. |
| Google Play | Review prompts and app updates | Standard Play Store interactions when you are asked to rate the app or offered an update. |
| Google AdMob | Advertising in the free version — see Section 4 | Advertising identifier and standard ad request data. |
On-device barcode reading and the initial “is this food?” check are performed by Google Play services on your phone and send no image anywhere. Only the AI scan, which you start deliberately, uploads a photo.
The free version of Brekk shows advertising. Anyone with an active Brekk subscription or free trial sees none at all, and nobody sees any during their first days with the app.
If you are in the European Economic Area, the United Kingdom or Switzerland, you are shown a consent form before any personalised advertising is requested. You can agree, refuse, or open the full list of purposes and partners and decide among them one by one. Refusing costs you nothing in the app. You can change your answer at any time from Settings.
| Permission | Why |
|---|---|
| Camera | Only when you photograph food or attach a photo to a fast. |
| Physical activity | To read the step counter for the Steps tracker. Declining it leaves the tracker empty and nothing else changes. |
| Notifications | Fasting timer, phase and reminder notifications. |
| Foreground service | To keep an accurate timer running and visible while a fast is in progress. |
| Run at startup | To restore your running fast and your reminders after the phone restarts. |
| Vibrate | Haptic feedback, which you can switch off. |
| Internet and network state | For the services listed in Section 3. |
| Advertising ID and related | To select and measure the ads shown in the free version; see Section 4. |
| Billing | Subscriptions through Google Play. |
Brekk does not request your location, your contacts, your files, or your microphone.
Brekk records fasting, weight and body data that may count as health information in your jurisdiction. It is stored as described in Section 1 and leaves the device only through Android’s backup (Section 2).
Brekk is a wellness and educational tool and does not provide medical advice. Consult a qualified healthcare professional before changing how you eat or fast — particularly if you are pregnant or breastfeeding, under 18, have a history of disordered eating, or have a medical condition such as diabetes.
Asking us to delete something. Clearing the app’s data removes everything held on your phone, which is almost all of it — but the analytics described in Section 2 sit with Firebase rather than on your device, and no button in the app can reach them. Email support@dailywell.app and we will delete what we hold about your installation. There is no account to identify you by, so please send the request from a device with Brekk installed and tell us roughly when you installed it; that is what lets us find the right records. We answer within 30 days.
Brekk is not directed to children and is intended for people aged 18 and over. We do not knowingly collect data from children. If you believe a child has provided data, contact us and we will address it.
Your data is held in the app’s private storage, which other apps cannot read on a device that has not been rooted or otherwise compromised. Everything exchanged with the services in Section 3 is encrypted in transit over HTTPS. No method of storage or transmission is completely secure, but we use standard safeguards.
Depending on where you live — for example under the EU or UK GDPR, or California’s CCPA and CPRA — you may have the right to access, correct, delete or port your personal data, and to object to or restrict certain processing.
Because Brekk holds your data on your own device, you can exercise most of these rights directly: export it, edit it, or delete it from within the app and your device settings. For data held by the services in Section 3, contact us and we will help, including by forwarding your request to the relevant provider.
The providers in Section 3 may process data on servers outside your country, including in the United States. Where required they rely on appropriate safeguards, such as Standard Contractual Clauses, for those transfers.
If we change how Brekk handles your data, we will update this page and the date at the top. Where a change is significant — a new kind of data, or a new use for data already collected — this policy will say so before the change takes effect, not after. That is how advertising was handled: this section described it in full while the app still showed none.
Questions or requests about this policy or your data: