Privacy

What this site collects

Nothing. The booking and contact forms on this site do not submit anywhere: the multi-step form validates and summarises entirely in your browser and then stops. No analytics, no tag manager, no advertising pixels, no third-party fonts, no embedded maps and no cookies are set by this site.

Local storage — the four things, named

Two keys in your browser's localStorage, and nothing else:

• opalesce.v1 — the room (light, dark or follow the system), the illuminant, and your comfort settings: text size, contrast, motion and link underlines.
• enamel.cz.v1 — the palette you picked in the shade drawer, plus, if you have opened the studio panel at ?studio=1, the colours, type pairing and identity fields you set there.

That is the complete list. It is functional state, not tracking, but it is still storage and it is still yours: the notice at the top of the page on your first visit lets you decline, and declining is real. Nothing is written, anything already written is removed, and the site keeps working for the length of the tab. The refusal itself is kept in sessionStorage under opalesce.declined, because recording"do not store anything about me" in persistent storage would be the exact thing you had just refused — which does mean you will be asked again on your next visit.

None of it leaves your device and none of it reaches a server. Clearing your site data removes it, and the comfort panel's reset and the studio panel's reset each clear their own share explicitly.

Images

Every portrait of a person on this site — the four team members, the patient in the hero, and both frames of every before-and-after pair — is a synthetic image generated for this build. None of them is a photograph of anybody, none depicts an identifiable patient, and none records treatment carried out by anyone. The before-and-after frames say so on their own face. A small number of supporting photographs are licensed stock and are attributed in CREDITS.txt in the repository.

What a real practice's notice would have to cover

A live dental practice in the United States handles protected health information and would need a HIPAA Notice of Privacy Practices setting out, at minimum:

• the categories of information collected, including clinical records, radiographs, photographs and payment data;
• the permitted uses for treatment, payment and healthcare operations, and the uses requiring separate written authorisation — marketing and the publication of clinical photographs among them;
• the patient's rights to inspect, obtain a copy of, amend and receive an accounting of disclosures of their record;
• the right to request restrictions and confidential communications;
• retention periods, which in Arizona are governed by state record-keeping rules;
• the practice's breach-notification obligations; and
• how to complain, both to the practice and to the Office for Civil Rights.

A live site would also need to disclose any analytics, advertising or chat tooling, since third-party scripts on a healthcare site can transmit information about which treatment pages a person read.

Questions

This site is a demonstration and there is no practice behind it. In a live deployment, enquiries would go to hello@dental1.thesamplesite.com.

Last reviewed: September 2026.