Privacy
This page separates two things that are usually run together: what this template’s own code does, which can be checked, and what a deployment of it does, which cannot be known from here. Only the first is stated as fact.
The controller, the retention periods, the applicable data-protection regime and the channel for a rights request are all outstanding. What the template's own source does is stated below and is verifiable; everything the hosting arrangement does is not.
Each outstanding fact is marked below. This notice is configuration rather than copy: it is driven by NEXT_PUBLIC_LEGAL_REVIEWED, and npm run legalcheck reads the served page and refuses when the two disagree. Removing this markup by hand does not clear the review.
What this template does
These statements are about the source in this repository, and each is verified by npm run legalcheck, which loads the served pages, records every network request and reads the cookie jar.
- It contains no analytics script, no tag manager and no tracking pixel.
- It writes no cookie and no browser storage of its own.
- Its typefaces are downloaded once at build time and served from the same origin as the page, so displaying them makes no request to a font host.
- Its photographs are local files, so no image is fetched from another origin.
- Its forms have inert handlers. Nothing you type into the reservation form or the contact form leaves your browser, because there is nowhere for it to go.
What this template cannot tell you
A site is more than its source. Whoever serves these pages will have a web server that records requests, may sit behind a CDN, and will eventually wire the forms to something. None of that is visible from the repository, so none of it is described here.
If you are reading this on a published site and the notice above is still showing, the page has not yet been completed and you should not rely on it.
What the operator has to supply
Ten decisions, all of them legal rather than technical. Retention periods and the applicable regime in particular are jurisdictional: they depend on where the business trades and where its visitors are, and neither is knowable from a template.
- Data controller
- TODO(operator) — the legal entity that decides how visitor data is used
- Controller's address
- TODO(operator) — the registered address to publish for data questions
- Privacy contact
- TODO(operator) — the channel a rights request is sent to
- Data protection officer
- TODO(operator) — whether a DPO or a local representative is required
- Hosting and logs
- TODO(operator) — who hosts, what the server logs, and for how long
- Analytics and embeds
- TODO(operator) — any analytics, tag manager, map or embed added after this build
- Form endpoints
- TODO(operator) — where form submissions go, and that processor's terms
- Cookies
- TODO(operator) — any cookie or storage set outside this template's source
- Retention
- TODO(operator) — how long each category of data is kept, and why
- Rights and complaints
- TODO(operator) — the applicable regime, the rights it grants, the complaint route
Changes to this notice
Once written, a privacy notice needs a date and a change history. Neither exists yet, and a version date invented now would misdescribe when the policy was actually decided.