Privacy

Short version: the site has no accounts, sets no cookies, and keeps nothing that identifies you on its servers. What it does store stays in your own browser.

What stays on your device

Your theme choice and your timer settings are saved in your browser’s local storage. They never leave the device and are never sent to us. Clearing your browser’s site data removes them, and the site works exactly the same afterward — it simply forgets your preferences.

To keep the timers working without a connection, your browser also saves a copy of this site’s own files — its pages, scripts and icons — in its cache storage. That copy contains nothing about you, is replaced when the site changes, and is removed together with the rest of the site data.

What we measure

Page views are counted by Umami, a cookieless analytics service, in aggregate: which pages were opened, on what kind of device. It sets no cookies, stores no identifier on your device, and cannot follow you to other sites. We cannot tell one visitor from another, and we do not try to.

Two more things are counted: starting a session and finishing one. Starting records which technique you opened, its pattern of phase lengths (for example 4-4-4-4) and how many cycles were set as the goal. Finishing records the same technique and pattern plus how many seconds it ran and how many cycles it actually completed. Both records also say where the session ran: on this site, in a timer embedded on someone else’s page, or in the live preview on the embed code generator. Nothing in either record points back to you — no identifier, no settings. We count both because the gap between them is the only way to tell whether the tool actually gets used to the end, not just opened.

We also count clicks on the links that lead to a timer: the preview circle on the home page, the technique cards there, and the technique and timer links in the site header. The record says which link was clicked and, for a technique link, which technique. On the paced breathing and breathing timer pages, and on the embed code generator, picking a preset records which page it was picked on and which preset was picked. Opening the embed code generator from a technique page counts one embed-open event, and pressing its Copy code button counts one embed-copy event; neither carries anything about the code that was generated. On a timer itself, three controls are counted when clicked: the Sound & length panel, Focus mode and the sound on/off button. The record says which control it was, which technique the timer was for, and what the click did — opened or closed the panel, turned focus mode or sound on or off. When a page stays open in a visible tab for 30 seconds, we count one engaged event with nothing attached to it — without it, a visit that stayed and a visit that left at once look the same. None of these carries an identifier.

Three more signals concern the home-screen app. A click on the Install button counts an install-click event, and when your browser reports that the site was installed, we count an app-installed event; nothing is attached to either. When the installed app opens, its page view carries the marker utm_source=pwa, so launches from the home screen can be told apart from visits in a browser tab. None of these signals carries an identifier.

Analytics requests are served from this domain rather than a third-party one, so ad blockers do not drop them before they are recorded. Umami still receives and processes them — the domain change only keeps the request from looking like traffic to a separate company’s server.

Embedded timers

Other websites can embed our timers with the code from the embed page. The timer then runs inside a frame served from breathecadence.com. It uses the same cookieless analytics as this site and keeps its settings in your browser the same way; the page around the frame passes us nothing except its address as the referrer.

What we never collect

No name, no email address, no account, no session recording, no cross-site tracking, no advertising profile. If you write to us, we hold that email in the mailbox for as long as it is useful and nowhere else.

Hosting

The site and its email address are served by Cloudflare. Like any hosting provider, it keeps short-lived technical logs, including IP addresses, for delivery and abuse prevention, and deletes them on its own schedule. That is standard infrastructure logging, and we do not use those logs for analytics.

Why this is allowed

Counting visits and sessions in aggregate, and the hosting logs above, rely on our legitimate interest in keeping the site running and knowing whether the timers are used (Article 6(1)(f) of the GDPR). Answering an email you sent relies on the same interest. Nothing here relies on consent, because nothing here needs it: there are no cookies to accept and no profile to build.

How long records are kept

• Analytics records are kept by Umami for six months and then deleted.
• Emails stay in the mailbox for as long as the conversation is useful.
• Settings in your browser stay until you clear the site’s data.

Advertising

There are no ads on the site today. If that changes, this policy is rewritten before a single ad script loads, and the change is dated at the top of this page.

Your rights

You can ask what we hold about you, ask for it to be corrected or deleted, and object to how it is used. In practice the analytics records carry no identifier, so there is nothing we could find and attribute to you — but if you have written to us, we can delete that correspondence on request. You also have the right to complain to the data protection authority in the country where you live.

Questions

Write to hello@breathecadence.com — for questions about this policy and for any of the requests above.