Privacy

Registry Docs uses self-hosted, cookie-free aggregate analytics and, with your permission, optional visit tracking shared with the main Registry Stack website. This page describes that processing and the choices available to you.

Who operates Registry Docs

Aubex Consulting LLC, 28 Geary St, Ste 650 #189, San Francisco, CA 94108, United States, publishes Registry Stack and operates Registry Docs. Aubex is the controller responsible for this site. You can contact Aubex at contact@registrystack.org.

Aggregate analytics

Registry Docs loads self-hosted Umami analytics from stats.registrystack.org only on the canonical documentation at docs.registrystack.org/. The /dev/ tree and versioned /v/<version>/ archives do not load Umami. Umami records page views, including URL query parameters, referral sources, general browser and device information, approximate location, and selected outbound-link clicks. The tracker does not set cookies or use a persistent visitor identifier. Umami uses the request IP address to estimate location but does not store the address.

Registry Stack uses these records to understand page use, improve navigation, and prioritize documentation work. The analytics records are not sold, used for advertising, or shared with advertising networks.

Optional visit tracking

Optional tracking is available on canonical released pages and the public /dev/ documentation. Versioned archives and error pages do not offer optional tracking.

If you accept optional cookies, that choice applies to the main Registry Stack website and Registry Docs for six months. Registry Docs sends approved visit details through a hidden tracking bridge on the main website. The Mautic tracker and its browser identifier remain in that bridge; Registry Docs does not store a Mautic identifier or load Mautic directly.

For each accepted documentation visit, Registry Stack can record the public page URL, page title, referring site’s origin, and reviewed external campaign labels. It does not send search terms, other query parameters, URL fragments, or the full referring page. The shared bridge can recognise an accepted journey between the main website and Registry Docs without putting an identifier in links between them.

If you later contact Registry Stack through the main website, accepted earlier visits may be linked to the details you provide with that enquiry. Registry Docs has no contact form and does not send marketing email. Registry Stack does not use these records for advertising or sell them.

Hosting data

Registry Docs is hosted on GitHub Pages. GitHub processes request and server-log data to deliver and protect the site under the GitHub Privacy Statement.

Legal basis and retention

Where the General Data Protection Regulation or UK General Data Protection Regulation applies, Aubex relies on legitimate interests to operate aggregate documentation analytics. Analytics records remain in the self-hosted Umami database while they are useful for improving Registry Docs and are removed when they are no longer needed for that purpose. Optional visit tracking relies on your consent. Its records remain in the self-hosted Mautic system while they are useful for understanding and responding to Registry Stack enquiries, subject to Aubex’s retention and deletion processes.

Your choices and rights

You can block the analytics script with browser controls or a content blocker without losing access to the documentation. Use Tracking preferences in the footer to accept, reject, or change optional visit tracking. Rejecting or withdrawing consent stops future optional tracking and clears the shared browser identifier controlled by the tracking bridge. It does not automatically delete records already stored in Mautic. Registry Stack also treats Do Not Track and Global Privacy Control browser signals as a request to keep optional tracking off.

Email contact@registrystack.org to request access to, correction of, deletion of, or restriction of personal data, or to object to its processing. Umami analytics are not connected to a name or email address, so Aubex may not be able to identify records associated with a particular visitor. You can also complain to the data protection supervisory authority in your country.

Effective date: October 24, 2026.