Cookies and analytics

Strictly necessary

When you are signed in, a session cookie keeps you signed in and a token protects forms against cross-site request forgery. These cannot be switched off without breaking sign-in, and they are not used for tracking.

Analytics, if you allow it

Our analytics are first-party and deliberately minimal. If you allow them we record events like a page view, opening the demo, interacting with the demo, and starting registration.

Each event is stored against a rotating pseudonymous identifier: a hash of a secret salt, the current date and a first-party browser identifier. Because the date is part of the hash, the identifier changes daily and cannot be used to follow you over time. We do not store raw IP addresses for analytics, and where an address is used as a fallback it is first coarsened to a network range.

What is never in analytics

The content of your obligations, names, dates you have entered, or anything you type. Analytics events carry a fixed list of technical properties and nothing else. Visitor analytics are kept entirely separate from the security audit records used to protect accounts.

Active time

Inside the app we measure active time only while a tab is visible and recently interacted with, and we stop counting after a few minutes of inactivity — so a forgotten open tab is not recorded as hours of use.

Your choice

You are asked once, and declining means nothing is sent at all. You can change your mind by clearing this site's stored data in your browser, which will prompt the question again.