Cookie status of the generated files
The generated static files do not set cookies by themselves. They do not include JavaScript, tracking pixels, analytics tags, advertising tags, embedded third-party widgets, cookie-consent tools, or affiliate tracking scripts.
Because no generated cookie-setting tools are included, this policy does not invent cookie names, analytics vendors, advertising networks, retention periods, or tracking categories.
What is not present
The generated site does not contain account login systems, player registration forms, payment forms, newsletter forms, comment forms, pop-up widgets, embedded videos, social media embeds, or advertising placements. It also does not include generated scripts that would store identifiers in a visitor’s browser.
Hosting and browser behaviour
A visitor’s browser may still cache static files such as HTML or CSS after publication. Hosting providers may also process server logs. Those functions are different from cookies set by the generated website files and should be assessed by the publisher in the live hosting environment.
When this cookie policy must be updated
If the publisher adds analytics, advertising, embeds, consent tools, affiliate tracking, live chat, form processors, personalisation scripts, or any other tool that sets or reads cookies or similar browser storage, this cookie policy must be updated before publication.
The updated policy should describe the actual cookies or similar technologies used, the purpose of each category, the provider where relevant, retention where relevant, and how visitors can manage their choices.