Cookie Policy
- Version
- 0.4-draft
- Draft dated
This policy lists every cookie and item of browser storage that Which Dental uses, explains which ones are optional, and tells you how to change your choice about analytics cookies.
1.Cookies and similar technologies
Cookies are small files a website stores in your browser. Local storage and session storage are similar browser features: local storage keeps an item until it is removed, and session storage keeps it only until you close the tab. The Privacy and Electronic Communications Regulations 2003 (PECR) require consent for them unless they are strictly necessary to provide a service you have asked for.
Which Dental runs on two sites, whichdental.com (the marketplace) and app.whichdental.com (where you book, manage bookings and run a provider workspace). Your analytics consent is shared between them through a first-party cookie. Your light, dark or automatic appearance choice is also shared between the sites on this browser.
2.Strictly necessary cookies and storage
These are needed for signing in, keeping your account secure and remembering your cookie choice. They are always on.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
wd_[deployment]___convexAuthJWT | Which Dental (first-party cookie shared by both sites) | Authenticates requests to your account. The short-lived access token is also held in browser storage. | Access token lasts about one minute and is renewed while signed in; storage is cleared on sign-out |
wd_[deployment]___convexAuthRefreshToken | Which Dental (HTTP-only first-party cookie shared by both sites) | Keeps you signed in between visits and renews your access token. Browser scripts cannot read it. | Up to 30 days, renewed while signed in, or until you sign out |
| Sign-in and email-verification state | Which Dental (local storage on the platform) | Protects Google and Microsoft sign-in and verifies that email links are opened in the browser that requested them. | Until the flow completes, is replaced by a new request, or you clear browser storage |
wd-analytics-consent | Which Dental (shared first-party cookie and local storage) | Records whether you accepted or rejected analytics cookies, and when, across both Which Dental sites. | 12 months, after which we ask again |
__ph_opt_in_out_[project key] | PostHog for Which Dental (local storage, on each site) | Records the same choice for our analytics software, so it knows whether it may use analytics cookies. Set once you accept or reject. | Until you clear your browser storage or your choice expires |
Cookie names include a deployment identifier to keep separate environments apart. When our analytics software starts, it may briefly write and then remove a test item, such as __mplssupport__ or __ph_cookie_support_[random id], to check whether your browser allows storage. Nothing is kept.
3.Settings you choose
These items are set only when you use the feature concerned. They remember a choice you made so that the feature works as you left it.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
wd-theme | Which Dental (shared first-party cookie and local storage) | Remembers your light, dark or automatic appearance choice across both sites. Automatic appearance estimates sunrise and sunset from your browser's time zone, not your location. | Cookie: 1 year. Local storage: until you clear your browser storage. |
wd-compare-v1 | Which Dental (local storage, whichdental.com) | Holds the courses you add to compare: up to three, with each course's web address, title and when you added it. | Until you remove the courses or clear your browser storage |
wd-compare-tray-v1 | Which Dental (local storage, whichdental.com) | Remembers whether you collapsed the comparison tray. | Until you clear your browser storage |
which-dental:last-provider-slug | Which Dental (local storage, app.whichdental.com) | Remembers the provider workspace you last opened, so signing in returns you to it. Set only when you use a provider workspace. | Until you clear your browser storage |
which-dental:last-surface | Which Dental (local storage, app.whichdental.com) | If you both book courses and work in a provider workspace, remembers which of the two you used last, so signing in reopens it. | Until you clear your browser storage |
wd:provider-setup-dismissed:[provider id] | Which Dental (local storage, app.whichdental.com) | Remembers that you hid the set-up checklist for a provider workspace after launch. | Until you clear your browser storage |
4.Analytics cookies (optional)
We use PostHog, a product analytics service, to understand how Which Dental is used and to find and fix problems. Each site shows a short notice headed "Analytics cookies" with two equal choices: Reject cookies and Accept cookies.
Before you choose, and if you reject. We still count visits and record which pages and features are used, but without cookies or any storage on your device. Instead of recognising your browser, PostHog's servers group the requests from one visitor using an anonymous code that changes every day, so you cannot be followed from one day to the next. Your IP address is used to estimate your approximate location and is then discarded. No session recordings are made and no surveys are shown.
If you accept. PostHog stores the items below on that site so that it can recognise your browser on later visits, link the pages you view into a visit, and record visits as session recordings so we can see where pages are confusing or broken. Recordings hide everything you type into forms; on app.whichdental.com they also hide all the text on the page, including names, emails and GDC numbers. We do not record console logs or the content of network requests. If you are signed in, analytics events are linked to an internal account identifier, never to your name, email address or GDC number. We may also show you a short survey, and a help button that lets you chat with our team. If you use the help chat, the name and email address you give us and your messages are kept with that conversation and linked to the same identifier, so we can reply; the chat is never included in session recordings.
| Name | Type | Purpose | Duration |
|---|---|---|---|
ph_[project key]_posthog | Cookie and local storage, on the site where you accepted | An anonymous identifier for your browser, your current visit and analytics settings, so visits can be counted and linked. | Cookie: one year from your last visit. Local storage: until you reject analytics or clear your browser storage |
ph_[project key]_posthog_cpm | Cookie, on the site where you accepted | Technical details that PostHog keeps alongside the cookie above. | One year from your last visit |
ph_[project key]_posthog__flags, ph_[project key]_posthog__surveys and survey items such as seenSurvey_[id], inProgressSurvey_[id] and lastSeenSurveyDate | Local storage | Which version of a feature you see while we test changes, and which surveys you have seen or answered, so you are not asked twice. | Until you reject analytics or clear your browser storage |
ph_conv_[project key] | Local storage | A random browser identifier and conversation ID so this browser can see your earlier conversations with our team, whether the chat is open, and the name and email you provide in the chat. | Until you sign out, reject analytics or clear your browser storage |
ph_[project key]_posthog, ph_[project key]_window_id, ph_[project key]_primary_window_exists and ph_replay_pending_buffer_[id] | Session storage | Keeps track of the current tab and visit, and briefly holds a session recording until it is sent. | Until you close the tab |
With your consent PostHog also records clicks, scrolling (shown to us as heatmaps), clicks that do nothing, page speed and errors. The details of what PostHog collects, who can see it and how long it is kept are in the Privacy Notice.
Some events, such as a booking being confirmed or a payment succeeding, are recorded by our servers when they happen, whatever you choose here. They use no cookies or storage on your device and are described in the Privacy Notice.
5.Your choice across Which Dental
- whichdental.com and app.whichdental.com share your choice through a first-party consent cookie. Accepting or rejecting on either site applies to both.
- When you follow a link from whichdental.com to app.whichdental.com, and you have accepted analytics on whichdental.com, the link carries your anonymous analytics identifiers so that the two parts of your visit can be joined. They are used on app.whichdental.com only if you have accepted analytics there too.
- Your choice lasts 12 months. We also ask again if this policy changes in a way that affects analytics.
- To change your choice, select "Cookie settings" in the footer of whichdental.com, or in the footer of the app.whichdental.com sign-in and account pages. If you reject after accepting, PostHog removes its analytics cookie and storage from that site and goes back to measuring without them.
6.Third-party pages and videos
Card payments open on Stripe's own checkout pages at checkout.stripe.com, and provider billing and payouts open on Stripe-hosted pages. Stripe sets its own cookies on those pages under Stripe's cookie policy. We do not load Stripe scripts on Which Dental pages.
Some course pages include a video from YouTube or Vimeo. Until you press play, the page shows our own image and nothing loads from YouTube or Vimeo. When you press play, the video loads in YouTube's privacy-enhanced mode (youtube-nocookie.com) or with Vimeo's do-not-track setting, and that service may then use its own cookies or storage under its own policy.
Which Dental does not use advertising, retargeting or social media tracking cookies or pixels.
7.Managing cookies
Use "Cookie settings" to accept or reject analytics cookies at any time. You can also delete or block cookies and storage in your browser settings. If you block Convex Auth's cookies, you will not be able to sign in, book a course or use a provider workspace. Browsing the marketplace works without them. If you clear your browser storage, we will ask for your analytics choice again.
8.More information
The Privacy Notice explains how we use personal data, including the analytics data PostHog processes for us and the technical data our hosting and sign-in providers process.