Privacy by boundary.

Last updated: 30 August 2026. Herby Projects is a public portfolio website. Its purpose is to describe projects and link to their live experiences and public source code. The portfolio itself does not provide user accounts, advertising, payment processing, mailing lists, or a contact form. It does not intentionally collect names, email addresses, telephone numbers, or private journal content.

Routine web data

The site is delivered through Cloudflare and a private origin server. Those infrastructure providers may process ordinary request information such as IP address, user agent, requested path, timestamps, TLS details, and security signals to deliver the site, prevent abuse, and diagnose faults. Herby Projects does not add third-party advertising pixels or cross-site marketing trackers to these public pages.

Links and separate apps

The portfolio links to GitHub, GitHub Pages, publishers, and project subdomains. Those destinations have their own data practices. Some Herby projects are private applications with authentication and purpose-specific storage. Their protected data is not made public merely because the project is described here. Agents and visitors should use the ungated project summary and must not attempt to bypass login controls.

Cookies and content negotiation

The public portfolio pages do not set an application cookie. The server may vary a response by the HTTP Accept header so browsers receive HTML and compatible agents receive Markdown at the same canonical URL. Private subdomain applications may use an HTTP-only session cookie after a user logs in; that cookie is scoped to operating the private app and is not a portfolio analytics identifier.

Public reports and retention

If you contact Herby Projects through GitHub, the information you choose to post is handled by GitHub and may be public. Do not include secrets or private personal data. Public site content and deployment logs are retained only as needed to operate, secure, and improve the projects. Questions about this notice can be raised through the supported route on the contact page.