Privacy policy

Last reviewed: 16 October 2026.

Summary

New installations of Blimbi need an account: you sign in with Apple or Google. Installations from before version 2.4.0 may keep using the app without an account. Your history is created on the device first. When you sign in and enable sync, Blimbi encrypts the history on your device before upload; its infrastructure stores the encrypted content but does not hold the key needed to read it. The apps measure with Google and Meta which installs and subscriptions Blimbi’s ads bring, never your fasts; you can turn this off in Profile.

Data stored by the app

The app locally stores fasting sessions and corrections, protocol, reference time, preferences, onboarding state and safety answers. On iOS, optional diary logs are off by default and can be enabled in Profile > diary settings: water; coffee, tea and other drinks; meal times (events only, without food items, calories or nutrition); weight and height (height is used to show BMI); and body measurements (waist, hip, chest, thigh and body-fat percentage). Water, drink, meal-time and waist, hip, chest, thigh and body-fat entries remain on the device and are not included in the synced copy. If you sign in and enable sync, the end-to-end encrypted synced copy includes fasting sessions, weight and height entries, sync preferences and challenge progress. Safety answers remain local and are not included in the synced copy. The Android app records fasting logs only and does not offer these optional diary logs; if you use the same account on Android, weight and height entries synced from iOS are kept in the app’s private storage there. iOS shares a minimal summary with its widgets, Live Activity and Apple Watch app; Android shares it with its widget and active notification inside the app’s private storage. Blimbi does not access Apple Health, Health Connect, device location, contacts, photos, microphone or camera, and does not count calories, track activity or measure metabolism.

Account and encrypted sync

New installations need an account (Apple or Google); installations from before version 2.4.0 may keep using the app without one. When you sign in with Apple or Google, we receive the provider identifier (your account ID) and, depending on what it shares, your name, email address, verification status and image. We retain access sessions, linked providers, and technical security data such as the IP address and device user agent recorded with each session. If you enable sync, we store an encrypted vault, encrypted recovery envelopes, version and update time, and technical device information such as platform, app version and a random identifier. The journal kept in your account is end-to-end encrypted and Blimbi cannot read it. Your history leaves the device only as end-to-end encrypted text.

iOS crash diagnostics

Only in iOS builds configured with a valid DSN, Blimbi uses Sentry to receive technical crashes from the app, widgets and Live Activity. The iOS app may also send fixed technical events if Live Activity startup or Apple Watch synchronisation fails; watchOS does not include the SDK. The data may include the crash stack, app version and limited technical tags. Sentry also records release-health sessions (when a session starts and ends, whether it ended in a crash, the app version and a random installation identifier) to calculate the share of sessions and users without crashes. The configuration excludes fasting history, fasting dates, times and durations, safety answers, account details, email, free text, screenshots, view hierarchy, session replay, analytics, performance traces, logs, navigation breadcrumbs and network request data. Sentry acts as a processor; before activation, IP storage is disabled and access and retention are restricted. Android does not use Sentry in this release.

App measurement

The iOS and Android apps include Google Analytics for Firebase, provided by Google, and the Meta SDK, provided by Meta. The widgets, Apple Watch app and Wear OS do not include them. Blimbi uses them only to measure which of its own advertising campaigns on Google and Meta bring installs and subscriptions.

While app measurement is on, Google receives installation and app-open events, including the first open and sessions; Meta receives the installation and, on iPhone, app-open and session events. Both receive the device model, operating system and app version, language and similar technical details of the device, and the IP address of the connection, from which Google derives an approximate location. They receive an app-instance identifier and, on Android, the advertising ID. On iPhone, Blimbi does not show Apple’s tracking prompt and does not use the advertising identifier; attribution uses Apple’s aggregated SKAdNetwork.

While app measurement is on, when you start a free trial or subscribe, Google and Meta receive the plan, monthly or annual, the price and the currency. Google Analytics may also record its automatic in-app purchase event with the product and price. Neither provider receives fasts, fasting times or durations, weight, measurements, journal entries, safety answers, account details, name, email or which screens you open.

In the EU/EEA, the United Kingdom, Gibraltar and Switzerland, app measurement is off until you tap “Allow” on a question the app shows once. On iPhone the app goes by the device’s region setting. Android has no region setting, so the app goes by the region of the system language and the country of the SIM card and of the mobile network, and asks if any of them is in that area. An unknown region is treated the same way. Elsewhere, app measurement is on from the first launch. You can turn it on or off at any time in Profile with the “Ad measurement” switch. While it is off, the app records and sends no new events to Google or Meta, and if it has not been on since the app was opened, the two SDKs are not started.

Ad personalization is off, Blimbi creates no remarketing audiences and Google signals are off. Google Analytics data is retained for 14 months.

Google Ireland Limited provides Analytics as a processor on Blimbi’s behalf under the Google Ads Data Processing Terms and acts as an independent controller for Google Ads measurement under the Google Ads Controller-Controller Data Protection Terms. Blimbi and Meta Platforms Ireland Limited are joint controllers for the collection and transmission of app data to Meta through its business tools for people in the EU/EEA, Switzerland and the UK; Blimbi and Meta Platforms, Inc. are joint controllers for people elsewhere, under the same Controller Addendum cited under Providers and disclosures below. After transmission, Meta processes the data under its own Privacy Policy.

Website and technical data

When you visit this website, Cloudflare may process the IP address, date and time, requested URL, technical security identifiers and basic browser data to deliver content, prevent abuse and maintain availability. Cloudflare Web Analytics and Ahrefs Web Analytics measure aggregate usage without cookies, device storage or cross-site identifiers. To produce visit statistics, Ahrefs receives the IP address, the full page address, page title, referrer, browser language, screen size, and the destination of links you follow and forms you submit; it does not receive what you type into forms. Blimbi does not use advertising profiles or cross-site tracking for advertising unless you accept the cookies described below; it does not use session replay.

The website uses Google Analytics and the Meta Pixel, described below. The banner appears on every page until you make a choice, and you can reopen it at any time through “Cookie preferences” in the footer. Accept and Reject are equally prominent. Your choice is stored for 12 months in the first-party, strictly necessary blimbi_consent cookie. If you select Reject, Blimbi deletes the Google (_ga, _ga_*, _gcl_*) and Meta (_fbp, _fbc) cookies on blimbi.app.

Google Analytics 4 measures visits and taps on the store buttons. Its Google tag (gtag.js) loads with Google signals and ad personalization signals turned off, without User-ID and without any data you type. In the EU/EEA, the United Kingdom and Switzerland, Google’s analytics and advertising storage stay off until you select Accept: until then, or after Reject, the tag sets and reads no cookies and sends Google only cookieless requests (page views and the store-button events described below) with the consent state, page address, referrer and browser data, which Google uses for aggregate, modelled measurement. Elsewhere, Google Analytics sets its cookies when the page loads and you can turn them off with Reject, while Google’s advertising storage still waits for Accept. Google Analytics receives the page address and title, the referrer, browser, device and language data, an approximate location that Google derives from the IP address, page_view events, and store_click events with the store (ios or android), the page language, the button’s text and destination and the visit’s campaign labels. Blimbi keeps Google Analytics data for 14 months and receives only aggregated reports.

Blimbi measures its Google Ads campaigns with the same tag. If you arrive from a Google Ads ad, the address carries a click identifier (gclid, gbraid or wbraid). Before you accept, Blimbi does not store it: it stays in the page address, which reaches Google with the cookieless requests described above, and the gclid is added to the Google Play link you tap on that page. After you accept, Blimbi keeps it in your browser’s session storage until you close the tab, and Google may set _gcl_au and _gcl_aw to attribute the visit to the campaign. Ad personalization is turned off, so this data is not used to build advertising audiences. The legal basis for Google Analytics cookies and Google Ads measurement is your consent under GDPR Article 6(1)(a) and, in Spain, Article 22.2 of the LSSI. You can withdraw it at any time through “Cookie preferences” in the footer.

After you accept, on pages where the Pixel is allowed, Meta’s fbevents.js loads with automatic events disabled and does not use advanced matching. The Pixel receives your IP address, browser and device data, page URL, referrer, PageView events, custom StoreClick events with platform: "ios" | "android" when you tap a store button, the _fbp and _fbc cookies, and Meta’s own identifiers if you are logged in to Meta. The data goes directly from your browser to Meta and is used to measure and improve Blimbi’s ads on Facebook and Instagram; Blimbi receives only aggregated reports from Meta. The legal basis is your consent under GDPR Article 6(1)(a) and, in Spain, Article 22.2 of the LSSI. You can withdraw consent at any time through “Cookie preferences” in the footer, without affecting the lawfulness of processing carried out before you withdraw.

Neither Google nor the Pixel ever loads on guides whose subject is a medical condition, medication, pregnancy, menopause, an eating disorder or dehydration, on the fasting quiz or on the fasting tools. App Store links carry at most the campaign name when campaign measurement is configured and never carry click identifiers. Google Play links carry the campaign name, source, medium, content and term and, when present, the Google Ads gclid described above, so downloads can be attributed to each campaign. The campaign labels (utm_*) of the address you arrive with are kept in your browser’s session storage until you close the tab, so a later tap on a store button keeps its campaign; they contain no personal identifier.

The apps do not use the Pixel. The Blimbi app downloads public guide content from blimbi.app; these requests contain no account or device identifiers, and Cloudflare processes the IP address to deliver it.

Cookies

Google Analytics cookies follow the regional rules above. Advertising cookies are used only after you select Accept. The necessary cookie records your choice whether you accept or reject.

Cookie	Provider	Category	Duration
blimbi_consent	Blimbi	Necessary	12 months
_ga	Google	Analytics	13 months
_ga_B29V1H01VK	Google	Analytics	13 months
_gcl_au and _gcl_aw	Google	Advertising	90 days
_fbp	Meta	Advertising	90 days
_fbc	Meta	Advertising	90 days
fr and other Meta cookies on facebook.com	Meta	Advertising	Set by Meta under its own policy

Support messages

If you contact support or privacy, we process your address, message and any details you choose to provide to respond, investigate the issue and meet applicable obligations. Please do not send medical information that is not necessary. Messages sent from the in-app form include the category, message, optional email, platform, app version and language, and are deleted automatically after 180 days.

Purposes and choice

We use account data to authenticate you, link providers, maintain sessions, sync the encrypted vault, support recovery and deletion, prevent abuse and provide support. Technical data is used to operate and protect the app and website and for the advertising measurement described above. We do not use technical data for commercial profiling or data sales, or for advertising other than the Google Ads and Meta measurement described above, under the website and app choices stated in those sections. Installations from before version 2.4.0 can keep using local features without an account; new installations need one.

Notifications

If you grant permission, Blimbi schedules local notifications on your device. Blimbi does not receive their content or schedule; you can disable them in Profile or system settings.

Purchases and stores

Apple or Google processes Blimbi Plus as controller of its respective store. Blimbi does not receive your card details. RevenueCat validates purchase receipts or tokens and maintains purchase history and subscription and Plus-entitlement status, which we also use in aggregate to measure subscription performance. If you are not signed in, RevenueCat uses a random anonymous identifier generated by its SDK. If you sign in, the app links your purchases to your random Blimbi account identifier so Blimbi Plus follows you across your devices; it does not send your name or email address to RevenueCat, and signing out returns the device to an anonymous identifier. RevenueCat may also receive basic app and device technical data needed to provide this service. Store policies govern the account, payment and refund.

Providers and disclosures

Cloudflare provides the API, database, hosting, delivery, aggregate web metrics and protection for the app and website. Ahrefs provides cookieless aggregate web metrics for the website. Apple and Google provide sign-in and, where applicable, the store and payment. RevenueCat manages validation and Blimbi Plus status. Sentry processes technical diagnostics only in iOS builds where it is enabled. Google Ireland Limited provides Google Analytics for the website and apps as a processor on Blimbi’s behalf under the Google Ads Data Processing Terms; for Google Ads measurement, Google acts as an independent controller under the Google Ads Controller-Controller Data Protection Terms. Google may transfer data to the United States under the EU–US Data Privacy Framework and explains its own use in How Google uses information from sites that use its services. The service providers above may process data in other countries under their terms and applicable safeguards. Blimbi and Meta Platforms Ireland Limited are joint controllers for the collection and transmission of data to Meta through the Pixel and Meta SDK for people in the EU/EEA, Switzerland and the UK; Blimbi and Meta Platforms, Inc. are joint controllers for people elsewhere, under Meta’s Controller Addendum. After transmission, Meta processes the data under its own Privacy Policy and transfers data to the United States under the EU–US Data Privacy Framework. We disclose data only when needed to provide, protect, support or measure the advertising of the service as described in this policy, or where required by law. We do not sell personal data.

Retention

Local data remains on your device until you erase it or uninstall the app. Account, device and encrypted-sync data is retained while you keep the account and is erased when you confirm account deletion, unless an exceptional legal duty applies. Sessions have limited validity, and technical records and support messages are retained only for the operational, security or legal period required.

Your rights

You may request access, correction, deletion or objection, withdraw consent or limit use and disclosure by emailing the privacy contact with your name, specific request, affected data and a reply method. Requests about data Meta holds from the Pixel or Meta SDK can also be made to Meta, which is responsible for them under the Controller Addendum. We may request the minimum information needed to verify identity and will respond within applicable legal deadlines.

Export and deletion

You can export your history, erase local data and delete your account from Profile. Confirmed account deletion removes the profile, sessions, devices, linked providers and all encrypted content stored by Blimbi. It does not cancel an App Store or Google Play subscription. Blimbi cannot recover erased data, decrypt the vault or access the export destination you select. Confirmed account deletion also deletes the customer record, including purchase history, that RevenueCat keeps under your account identifier; if that step fails, the account is not deleted and you can try again. Measurement data already sent to Google and Meta is not tied to your Blimbi account and is not erased when you delete the account: Google Analytics retains it for 14 months and Meta retains it under its own policy.

Security and children

We apply data minimisation, private platform storage, HTTPS transport and reasonable protective measures. No system is infallible. Blimbi is not directed to children and its safety questionnaire disables the timer where appropriate.

Changes and contact

We will publish changes at this URL and show the review date. The controller’s legal identity and the email for privacy and data-rights requests appear at the end of this policy.

Controller and contact

HURTADO GLOBAL MEDIA GROUP S DE RL DE CV · RFC HGM160624EP4

Avenida Nuevo León 161, 2º piso 201, sección C, Hipódromo, 06100, Cuauhtémoc, Ciudad de México, México.

hi@blimbi.app

Newsletter data

Once the newsletter service is active, it will process a normalized email address, locale, consent version, source placement, subscription state and relevant timestamps. Confirmation and unsubscribe tokens are stored as hashes. Short-lived abuse controls use a keyed transformation of network identifiers; full IP addresses are not stored in the subscriber records. Open and click tracking are disabled.