Privacy Policy

Your local records

Breeding Journal and Progression Checklist records are designed to stay in your device/browser storage. Clearing browser data may remove them. Export a backup before clearing or changing devices. These records are never sent to this site's server, included in URLs, or written into analytics.

Export and import

Export downloads a JSON file to your device when you ask for it. Import reads a file you choose, validates it, previews the result, and writes only after you confirm. No file is uploaded anywhere.

Plausible analytics (ShipSolo, self-hosted) — active

This site uses Plausible, an open-source, privacy-focused analytics tool, running on an instance operated by the site's hosting provider at plausible.shipsolo.io. Its purpose is aggregate traffic measurement: page views, referrers, countries, and device types.

What it collects: the page URL, the HTTP referrer, browser/OS/device type derived from the User-Agent (which is then discarded), and an approximate country/region/city derived from your IP address — your IP address is not stored. For Plausible analytics, this site removes the query string from the page URL in the event payload before sending it; page-URL query parameters, including ref/utm-style campaign tags, are not included in Plausible event payloads. A same-origin HTTP referrer in the payload is query-stripped the same way. Plausible sets no cookies and uses no persistent identifiers; unique visitors are counted with a daily rotating salted hash. This cookie-free behavior applies to Plausible only.

Custom events: a small set of fixed, predefined action names and values only (for example, that a journal record was saved). Events never contain free text, record contents, horse names or IDs, parent links, trait labels, notes, costs, imported file contents, user or session identifiers, or URLs carrying local data.

Retention: the retention period for these statistics is not publicly disclosed by the operator and is unknown. The statistics are processed on the operator's own instance and are not shared with unrelated third parties.

Microsoft Clarity (session recording and heatmaps) — active on clean allowed URLs, fixed-denied no-consent mode

On clean guide URLs where Clarity is allowed, this site queues a permanent "denied" consent signal using Consent V2 before the Clarity tag loads. This fixed signal does not guarantee that Microsoft sets no cookies or cannot recognize a browser across pages or visits. In fresh-browser QA, Clarity's first-party cookies _clck and _clsk were not observed, but browser QA observed that Microsoft may set Microsoft vendor cookies including CLID, MUID, and SM even under fixed denied. Depending on Microsoft's request chain, its documented vendor cookie names also include ANONCHK, MR, and SRM_B.

What it still collects: on the clean allowed pages where it runs, Clarity still processes interaction data (clicks, scrolls, navigation) and masked page content for session recordings and heatmaps. The site operates Clarity in Strict masking mode, so page text is masked in recordings, and Clarity always masks what you type into any input field — including the Quick Breeding Note on the homepage.

Where it does not load: Clarity does not load at all on /tools/* (including /tools/breeding-journal/ and /tools/progression-checklist/), /corrections/* (including /corrections/), the 404 page, or any URL with a query string. Plausible remains active on those pages. This prevents Clarity recording on local tool pages and prevents query-string data from entering a Clarity request.

Retention: recordings are retained by Microsoft for up to 30 days from the time of recording. Data is processed by Microsoft and stored in Microsoft Azure; see the Clarity Terms of Use and the Microsoft Privacy Statement.

Your choices: use the DAA opt-out (select Microsoft); enable Global Privacy Control (GPC), which Clarity officially supports; or block the clarity.ms domain in your browser — blocking the request prevents any Clarity processing on your device. The same blocking applies to plausible.shipsolo.io: both providers are script-based, so a blocked request means no collection by that provider.

Cookies and consent — no banner by Owner design

Plausible sets no cookies. Clarity's fixed denied signal does not prevent all Microsoft vendor cookies: the browser-QA observations and possible vendor cookie names are disclosed above. The site stores no consent choice and shows no consent banner, cookie preferences panel, modal, toast, drawer, or fixed overlay by Owner design.

Audience

This site is not designed for, marketed to, or directed at users under 18. If that ever changes, analytics will be disabled pending a new privacy review.

Corrections channel

The correction channel is being prepared and currently accepts no submissions. Never include horse names, player IDs, private notes, imported files, or anything you do not have permission to share. Retention and deletion terms will be published before the channel opens. General questions that are not tied to a specific correction can go through the Contact page.

External links

Links to the official Steam store, Steam News Hub, and Steam Community take you to third-party sites with their own privacy policies.

Retention and requests

This site runs no accounts and stores no user records on a server, so there is no server-side account data to delete. Your local data is controlled by you: per-record delete, delete-all, and JSON export are built into the tools. Plausible statistics retention is not publicly disclosed by the operator and is unknown; Clarity recordings are retained by Microsoft for up to 30 days as described above. Privacy questions and requests: email [email protected] (see the Contact page).