Rhino Inquisitor is currently a public, read-only Hugo site. It does not provide public logins, comment submission, checkout flows, or other visitor features that require first-party account or session cookies.
What this means in practice
- the site does not intentionally set first-party login or comment cookies for visitors
- the site does not currently publish the legacy Complianz consent widget from the old WordPress implementation
- embedded or linked third-party services may still use their own cookies or local storage when you interact with them
Third-party services and embeds
Some pages include or reference third-party services such as YouTube, GitHub, LinkedIn, or external documentation sites. Those services may place cookies or use local storage according to their own policies, especially after you start a video, follow a link, or interact with embedded content.
Where practical, Rhino Inquisitor uses privacy-friendlier embed patterns such as YouTube’s youtube-nocookie.com domain, but that does not eliminate all third-party processing once you interact with the media.
Browser and infrastructure storage
Your browser, hosting stack, or intermediary infrastructure may still use technical storage required to deliver pages, secure the service, or manage network behavior. Those technical mechanisms are separate from the legacy WordPress consent tooling that is no longer published from this repository.
Managing cookies
If you want to limit cookies or similar browser storage, you can manage that through your browser settings and through the privacy controls offered by any third-party service you choose to interact with.
Changes to this page
This page will be updated before any new visitor-facing consent, analytics, or cookie-dependent feature is added to the public site.