A static website should make static claims.
This page explains the privacy boundary according to what this website actually does and does not do in the current release scope.
This website is delivered in production as a static export. It does not create user accounts, does not provide a public submission backend, and does not currently expose open forms for direct data submission.
Ordinary technical data may exist at the hosting, CDN, or security-operations layer, for example an IP address, user agent, access time, or HTTP logs required for availability and protection of the service.
If a new data layer is ever introduced, this page has to change together with the real implementation. Not the other way around. Privacy text must not pretend the site has capabilities it does not actually have yet.
Frequently asked questions
Does this site store user accounts or dashboard data?
Not in the current release scope. The public site is static and has no account system.
Does this site use cookies for sign-in or preview sessions?
Not in the production scope. Runtime preview and similar session layers are not publicly shipped.
Related content
bojnansky.sk
A meta-project where information architecture, route ownership, and content structure become a public product surface.
Postmortem of the mock-first content layer
Postmortem on why the foundation slice had to leave mock-only mode and move to real Sanity wiring.