Cookie Policy

This is the complete list. There is nothing else, and there are no cookies in it.

Neither entry identifies you, and neither is transmitted to us or to anyone else. They are read by your own browser to render the page the way you asked for it.

A cookie is a small file a site stores in your browser and sends back to the server with every request. Local storage is a different mechanism: the browser keeps the value, but it is never attached to a request automatically — the page has to read it deliberately.

We use local storage rather than cookies for the two items above, which means those values never travel to our server at all. We still disclose them here. The law that governs this — Article 5(3) of the ePrivacy Directive, and the UK’s PECR — is written in terms of storing or accessing information on your device, not in terms of cookies specifically. A policy that disclosed only cookies would be technically accurate and substantively misleading, so this page covers both.

If you opt in, we load Plausible Analytics, which counts page views in aggregate. It does not use cookies, does not store an identifier on your device, and does not build a profile of you across sites or sessions. Plausible is designed to operate without processing personal data and is hosted in the European Union.

What we see is limited to:

• page views, in aggregate rather than per person;
• the referring site, if any;
• country-level location, derived without storing your IP address; and
• whether you are on a mobile or desktop browser.

Why we run no advertising pixel

We considered adding one to measure our advertising, and decided against it. The pages you read here — and the address of this site itself — reveal an interest in cycles, fertility, pregnancy or menopause. Handing that to an advertising network would tell it something about your health, and no amount of careful configuration fully removes that signal. So we do not. We would rather measure our marketing less precisely than make you the product.

Analytics is denied by default. Nothing loads until you make an affirmative choice, and declining is as easy as accepting.

When you choose, we write the entry named lova-cookie-consent to local storage, recording your answer, the moment you gave it, and a version number so that we can ask again if what we are asking about materially changes. That record is the proof of consent that the law requires us to keep, and it is kept on your device rather than ours.

To withdraw consent, use the “Cookie settings” link in the footer of any page. Withdrawal takes effect immediately: analytics stops, and we do not ask again until something material changes.

If your browser blocks local storage — in private browsing mode, for example — we cannot record a consent decision. In that case we treat the absence of a record as a refusal and load nothing optional, rather than assuming agreement.

Global Privacy Control

This site honours the Global Privacy Control signal. Because optional analytics requires an affirmative opt-in before it will load, sending a GPC signal produces the same result as declining: nothing optional runs.

This policy is about the website. The Lova app is a different thing and behaves differently: it is not a browser, so it uses no cookies and no browser local storage, it contains no advertising or behavioural analytics SDK, and it keeps your health data on your device.

The app does communicate with us in a small number of defined situations — validating a subscription, fetching Learn Library content, and sending a crash report if you have switched that on. Those are set out in the Privacy Policy, which is the authoritative description of what the app sends and when.

Where we embed content hosted by someone else — for example a code repository — that provider may set its own cookies or storage once the embedded content loads, under its own policy rather than ours. We keep such embeds to a minimum for this reason, and we do not embed anything from an advertising network.

The quickest route is the “Cookie settings” link in the footer, which changes your analytics choice directly. Beyond that, you can:

• clear this site’s data in your browser settings, which removes both entries listed in clause 1 and returns you to the default denied state;
• block storage for this site entirely — the site will still work, and will simply ask about analytics again on each visit and forget your theme preference;
• use private or incognito browsing, in which nothing persists after you close the window; or
• enable Global Privacy Control in a browser that supports it.

Instructions for the major browsers:

• Chrome
• Firefox
• Safari
• Edge

If we ever add a cookie, or store anything beyond the two entries in clause 1, we will update this page before doing so and bump the consent version so that you are asked again rather than carried over. Every revision is recorded in the amendment history at the foot of this page.

• Privacy enquiries: legal@lova.health
• Contact form: lova.health/contact