HOW THE SITE REMEMBERS
Cookies & browser storage
An explanation of essential browser storage, guest access and current analytics in the DetailLink pilot.
Essential local storage
DetailLink uses browser storage to keep quote form drafts, guest-request access tokens, private support case access codes and certain onboarding progress. This helps you resume work and reopen a guest request or support case in the same browser.
If you sign in to a DetailLink account, one secure, HttpOnly session cookie keeps you signed in for up to 30 days, or until you sign out or change your password. It is essential to the account and is not used for advertising or tracking across sites.
Clearing browser data, switching devices or using a private session can remove that access. Guest request pages offer a private recovery key you can save yourself; email-based recovery is not yet available.
First-party activity counts
The current pilot records limited first-party activity milestones, such as starting a quote request or reaching a form step, to understand where the experience needs improvement. These events are aggregated for internal reporting and are not an advertising profile.
Session storage is also used to avoid counting the same browser milestone repeatedly within a session.
For new quote submissions, the first observed visit in the current browser session is categorized using campaign tags or the referring site. We keep only a coarse traffic channel, recognized source, safe campaign label and page category. We do not retain the raw referrer URL, search query, cross-site visitor ID, IP address or browser fingerprint as part of this attribution. This session information is saved with a submitted request for internal analysis of which sources lead to quotes and bookings. If browser session storage is unavailable, the request origin is Unknown.
Campaign attribution is based on browser-provided information and may be incomplete. Historical requests are not retroactively attributed; aggregate form milestones cannot be tied back to individual people or used as an exact abandonment funnel.
Other technologies
The site uses third-party infrastructure for hosting, identity and display assets such as web fonts. Those services may process technical request information according to their own operations. The production privacy inventory will be reviewed during the domain and authentication handoff.
We do not currently provide a separate preference centre. If optional advertising or analytics trackers are introduced, their disclosures and any required consent controls will be added before enabling them.
Your browser controls
You can clear stored site data through your browser. Doing so may erase unfinished forms or a guest access key. Save the recovery key from each guest request before clearing storage. Protect it like a password; anyone holding the key can inspect the private request.