These details are not approved for publication. The operator must complete and review the legal information before the public launch.
Still to be supplied and reviewed
- Legal operator: pending
- Operator postal address: pending
- Responsible representative: pending
- Applicable registration and tax details: pending
- Privacy contact, providers and reviewed privacy notice: pending
- Retention and deletion schedules: pending
- Support owner, contact hours and fallback coverage: pending
This preview describes the implemented service. The final operator, privacy contact, purposes, legal bases, providers, international transfers, retention schedules and procedures for exercising your rights remain pending review. It is not an approved privacy notice.
An enquiry records the details you provide: name, chosen email or phone contact, language, treatment questions, selected clinics, travel preferences and any optional existing treatment plan. These details may include health information. An accepted submitted enquiry becomes a case for the ZahnChecker team; it is not a booking. An unsent draft or an explicitly rejected request does not create a new case.
Private search phrases, planner preferences, draft notes, contact choices and submission recovery state use the current tab's session storage. Search and draft validity is bounded to 24 hours for each saved version. The private search handoff keeps the phrase out of the results URL. Reopening a saved planner version does not renew its expiry; expired values are discarded when read. Cookie-backed planner drafts have their own server-confirmed expiry.
Independent comparison selections use persistent browser local storage until you clear them or remove browser data. Comparison links contain selected clinic identifiers and optional treatment filters. Adding a clinic to the comparison alone does not contact it, adopt it into an enquiry or grant sharing consent. An explicit action can adopt the clinic into your draft before you review an enquiry.
Journey continuity stores only bounded receipt and case references in browser local storage: identifiers, type, account owner where applicable, recording time and expiry. Reference validity is at most seven days. Health answers, contact details, access tokens and case statuses are not stored in these references. A reference grants no access; guest receipts require the owning guest cookie and patient case summaries require the current verified account. Statuses are checked again against authorized endpoints.
Guest receipt access lasts until the confirmed receipt expiry, at most seven days. Account verification can connect the same enquiry to your portal case. Receipt and draft expiry limit reuse or access; they do not promise deletion of the underlying case. Case, message, consent, audit, financial and document retention schedules remain pending.
You choose a contact method and consent to enquiry processing. Sharing with selected clinics, contact permission and optional portal email permission are recorded separately where offered. Patient–team and team–clinic conversations remain separate. Team members explicitly share approved information with permitted clinics; clinical responses released to patients require the existing clinical approval workflow. Selecting a clinic alone does not release a conversation or a document.
Authentication and guest access use cookies. Where enabled, form checks, sign-in, email, WhatsApp and private document storage use configured external services. Clinic images connect your browser to their public image host; embedded maps connect to Google only after you choose to load them. Configuration does not establish successful live delivery, approved provider terms or verified production storage. The final provider and data-handling disclosures remain pending.
Where newsletter signup is enabled, it records email, chosen language, signup and consent information, and confirmation time. The subscription becomes active only after confirmation through a link valid for 24 hours; consent can be withdrawn. Provider and retention details for these records are also pending final review.
Portal document access is checked against the case and sharing permissions. Uploaded files use quarantine and scanning, and authorized downloads require an eligible file state. These implemented controls do not replace approval of production storage, recovery procedures or retention schedules. Published contact channels and live team availability are shown only from the available contact configuration and status response; no individual advisor identity is claimed.
Optional Umami visitor analytics
After your explicit permission, we use self-hosted Umami on the ZahnChecker server. It records approved public pages without URL parameters or fragments, the referring website's domain, language, browser, operating system and device type, and approximate IP-based country, region and city where available. Phone and email clicks and successful newsletter requests are counted only by fixed event names; they do not confirm a connected call, a sent email or a confirmed subscription.
Form contents, search phrases, treatment planners, enquiries, the care journey, portal, clinic and management workspaces are excluded. Umami sets no analytics cookies; the configuration uses daily rotating anonymous session values and 13-month retention. There is no session replay, heatmap or advertising profile. Do Not Track and Global Privacy Control prevent analytics even when permission has been given.
The necessary zahnchecker-consent cookie remembers only your choice, format version, decision time and expiry for 180 days. It contains no visitor identifier and is not shared with the analytics subdomain. You can reject analytics or withdraw permission anytime in Privacy settings; the website remains usable.