The clinical Assist app uses local storage, session storage and IndexedDB to provide requested features, keep the service secure and remember your settings. It does not load advertising, audience-measurement or session-replay tools.
Public Assist marketing pages use optional tracking only after you consent. You can change or withdraw that consent through Cookie settings. Your choice is saved in local storage until you change it or clear site data.
The Assist pages you read are on helpdental.ai and the app you sign up to is on assist.helpdental.ai. We keep your choice in a first-party cookie that both addresses can read, so you are only asked once.
With analytics consent, Google Analytics measures visits and interactions, and Microsoft Clarity records how public pages are used: a replay of the page as it appeared to you, heatmaps, scroll depth, dead clicks, rage clicks and where people leave. With advertising consent, Meta Pixel measures visits and advertising interactions, and when you tap Try Assist free our server also tells Meta about that tap (your IP address, browser details and Meta's browser identifiers, no name or email). These tools may store identifiers in cookies.
While a split test of the public Assist landing page is running, browser storage remembers which page version you see. We carry that version and campaign identifiers into signup and checkout. Session storage lasts for the tab. A pending signup also saves these fields in local storage to connect an email confirmation within 48 hours. That record is removed when confirmation is processed or the browser data is cleared. With analytics consent, Clarity also receives the page version tag.
After analytics or advertising consent, we also store campaign parameters and advertising click identifiers in local storage to attribute visits. They remain until you clear site data. No optional tracking tools load in the clinical app, and clinical notes and recordings are not sent to these tools.
Assist stores the signed-in session and a device identifier in local storage. This keeps you signed in, refreshes the session securely and helps prevent account sharing or unauthorised devices. Authentication data lasts until you sign out, it expires or you clear site data. The device identifier remains until you clear site data.
Local storage remembers choices such as theme, microphone, note style, notation, templates, phrases, sign-off mode, audio-saving preference, interface layout and the names of assistants you add for sign-off. Most remain until you change them or clear site data. Account-scoped settings may also be saved to Assist so they follow you to another device.
Session storage keeps job references and, while a note is being prepared, the working transcript and draft context so the same tab can recover after a reload. It is removed as work completes and is otherwise cleared when the browser session ends.
While recording, audio chunks are stored in the browser's IndexedDB so a crash or lost connection does not destroy the appointment. They are removed after the note is generated or when you discard the recovery copy. Older abandoned copies are cleared after 24 hours; the newest recoverable recording remains until recovered or discarded.
A patient who unlocks a shared plan stores an unlock token in local storage so the plan remains open on that device. The server rejects it after the share expires or is revoked; clearing site data removes it from the device.
You can clear Assist data through your browser settings. Doing so signs you out, removes local preferences and can remove an unfinished recording before it is recovered. Blocking all browser storage may stop login, recording recovery and other core features from working.
Questions about storage can be sent to hello@helpdental.ai.