Privacy

Today, as shipped

This site's JavaScript (/assets/analytics.js) can measure a fixed set of acquisition events using Google Analytics 4 (GA4) — but only once a GA4 property is actually configured. As of today, no property is configured: this site sets no Measurement ID, so the script loads nothing from Google, sets no cookie, shows no consent banner, and sends zero network requests of any kind. You can verify this yourself: open your browser's network inspector and reload any page on this site — there is no request to googletagmanager.com or google-analytics.com.

Once a Measurement ID is configured, a small banner appears at the bottom of the page asking whether you consent to analytics. Analytics stays off (Consent Mode v2, "denied") until you choose Accept. Declining, or not answering, keeps it off. Advertising and remarketing signals (ad_storage, ad_user_data, ad_personalization) are never turned on by this site, whichever you choose — Google Signals is also disabled on the property itself.

The measured events are: a landing page view, and clicks on the Docs, Live demo, Self-host, MCP, and Request pilot links, each carrying only a hand-authored link identifier, the page path, and standard campaign-attribution (UTM) parameters when present in the URL. This is a closed, six-event set — adding a seventh requires a documented architecture decision. This site never sends Product Truth data, entity names, repository or organization names, ticket keys, document titles, file paths, or finding text to Google Analytics — none of that data is ever in scope for this script.

The pilot request form sends nothing over the network from this site itself: submitting it opens your own email client with the fields you entered, pre-addressed. This site does not store, log, or transmit what you type into that form.

A pilot request submitted through the form above may, once a real destination is chosen, be retained by Horonom to follow up on your request — that decision, its retention period, and its lawful basis are still being finalized and will be reflected here before the form's destination changes from a local mailto: link.

The product itself

This page covers only the marketing site. For how the Horologium product (self-hosted or the synthetic hosted demo) handles evidence, provider credentials, and data boundaries, see Security, privacy and data boundaries in the docs.