Privacy policy

The short version: your saved journal stays on your device, there are no user accounts, and analytics only runs if you allow it. One thing worth knowing up front: if you do allow analytics, the readings you look up or save are part of the usage data that goes to Google Analytics. Section 2 spells that out.

1. Who is responsible

EPSILON WEBCRAFTS LLC, 271 W. Short St Ste 410 #1522, Lexington, KY 40507, USA — contact: info@epsilonwebcrafts.com.

2. Your journal and health data

Readings you save on this site are stored exclusively in your browser's local storage on your device (bse_journal_v1). They are not transmitted to us or to anyone else — there is no server component, no account and no sync. You can export, import or delete the data at any time on the journal page; deleting your browser's site data removes it as well. Because the data never reaches us, we could not access, restore or delete it for you even on request.

That applies to the journal itself — the entries you save. It does not mean the numbers stay private from everyone: if you have allowed analytics (section 4), the reading you look up or save is sent to Google Analytics as part of the interaction data, together with the page address, which contains the value (for example /blood-sugar-180/). The same applies to the settings in the "Refine this result" panel, including the pregnancy option. Independently of your analytics choice, the page address is also visible to Google's advertising system as page context, because the ads on this page are served by Google. If you would rather not have that, decline analytics and use the site without saving readings — every feature keeps working.

3. Server logs

Our server writes technical access logs (IP address, requested URL, timestamp, user agent) for security and operations. The site runs behind a content delivery network, and the server restores your own IP address rather than recording the network's — so the address in those logs is yours, in full. We also read these logs ourselves, but only automatically and only in aggregate: to notice errors, broken links and outages. They are rotated and overwritten automatically as they grow, are never combined with any other data, and are never analysed to build a picture of an individual visitor.

4. Analytics (consent-based)

We use Google Analytics 4 to understand how the site is used (pages, referrers, coarse location). Analytics does not store your IP address: it is used to derive a coarse location and then discarded. That is how the service works and there is no setting for it — unlike the server logs above, which do keep the full address. Whether we ask you first depends on where you are: in the EEA, the UK and Switzerland, Google's consent dialog decides; in Canada, Brazil, Thailand and Morocco we ask with our own banner; elsewhere analytics is on by default and you can switch it off at any time under "Cookie settings". Until you allow it — and if you decline, permanently — no cookies are set. We do still count the visit itself in an anonymous, cookieless form, and that count carries the page address and title of the page you are on. Because our pages are named after readings, the address of a page you look up (for example /blood-sugar-180/) is part of that count even without your consent. What is never sent without it are the values you enter: saving a reading to your journal, checking a value, or adjusting the refine settings are only reported to Google once you have allowed analytics. The data includes the pages you visit — whose addresses contain the readings you looked up — and events describing what you did, such as saving a reading to the journal, checking a value, or adjusting the refine settings; the reading itself is part of those events. You can decline in the consent banner — every feature of the site works identically without it — and change your choice anytime via "Cookie settings" in the footer; where Google's consent dialog governs your region, that link reopens Google's own dialog. Your consent choice is stored locally (bse_consent_v1). If you allow analytics, that choice is refreshed after six months; if you decline, the refusal is kept until you change it yourself. Legal basis where GDPR applies: Art. 6(1)(a) GDPR (consent).

5. Advertising

The site shows ads via Google AdSense. In the EEA, UK and Switzerland, ad consent is collected by Google's certified consent management platform in a separate dialog, where you can also refuse personalized advertising. In regions where our own banner asks instead, declining there also switches off advertising cookies. Google may process data as described in Google's privacy & terms.

6. Your rights

Depending on where you live (GDPR, CCPA and similar laws), you have rights to access, correct, delete or port personal data and to object to processing. For anything this site actually processes — essentially server logs and consent-based analytics — contact info@epsilonwebcrafts.com. California residents: we do not sell personal information.

7. Children

This site is not directed at children under 13 and we knowingly collect no data from them.

8. Changes

We update this policy when the site's data practices change. Last updated: 2026-08-21.