Privacy

The short version

No account, email address, or phone number is required to read anything here.
Your question is never sent to a server. The lookup runs in your browser against a static index file.
Your question is never written into a URL by this site, and is stripped if it arrives in one.
Nothing you type into a tool is uploaded. No file upload exists anywhere on the site.
No analytics event ever contains free text.
No session replay, anywhere, ever.

Why the lookup runs on your device

An insurance question can be unavoidably personal. Someone asking about a claim denial, a health plan, or a dispute with a landlord is telling you something about their life. The safest way to handle that is to never receive it.

So the search index is a static file. Your browser downloads it once and runs every lookup locally. We can see that the index file was requested, the same as any image or stylesheet. We cannot see what you searched for, because it never travels.

We also ask you not to type private facts in the first place, on the field itself. You do not need a policy number or an address to get a useful answer here, and the site is not built to receive them.

What is stored, and where

Everything this site stores. All of it is on your own device.
What	Where it lives	What it contains	How it goes away
Your question on the Ask page	Never leaves your device	Held in memory while you are on the page. Handed between pages in sessionStorage and deleted on arrival.	Closing the tab
Your filter selections	localStorage on your device	Only fixed values such as "commercial" or "CA". Never free text.	Clearing site data
Tool entries	localStorage on your device	Whatever you typed into a tool, saved only when you press Save on this device.	Pressing Start over, or clearing site data
Search index	Downloaded to your device	A static file of published page text. Downloading it tells us nothing about what you then search for.	Normal browser cache rules

Everything this site stores. All of it is on your own device.

Your question on the Ask page

Where it lives: Never leaves your device
What it contains: Held in memory while you are on the page. Handed between pages in sessionStorage and deleted on arrival.
How it goes away: Closing the tab

Your filter selections

Where it lives: localStorage on your device
What it contains: Only fixed values such as "commercial" or "CA". Never free text.
How it goes away: Clearing site data

Tool entries

Where it lives: localStorage on your device
What it contains: Whatever you typed into a tool, saved only when you press Save on this device.
How it goes away: Pressing Start over, or clearing site data

Search index

Where it lives: Downloaded to your device
What it contains: A static file of published page text. Downloading it tells us nothing about what you then search for.
How it goes away: Normal browser cache rules

There is no server-side store of anything a visitor types. There is no database of questions, no log of searches, and no profile of any kind.

Analytics

Aggregate analytics are enabled on this deployment under the constraints below.

When analytics are enabled in production, they are constrained in code rather than by policy. Every event is filtered against a published contract before it can be sent: an event name that is not on the list is dropped, a parameter that is not on the list is dropped, and a parameter value that is not in that parameter's fixed vocabulary is dropped. A free-text value cannot pass that filter, because there is no vocabulary that accepts one.

The complete set of events that can ever be sent:

research_search_started
research_answer_viewed
source_opened
related_question_opened
tool_started
tool_completed
correction_started
bollinsure_handoff_clicked

Allowed parameters are limited to fixed vocabularies: insurance family, line, state, source type, page type, tool name, answer status, and a completion percentage rounded to the nearest ten. The full specification is in ANALYTICS-EVENT-SPEC.md in the repository, and the same contract is embedded in every page so the filter and the documentation cannot drift apart.

Never sent, under any configuration: your question, anything you typed into a tool, a name, an email address, a phone number, an address, a policy or claim number, or the contents of any document.

If you choose to contact Bollinsure

The licensed-help links are optional and appear only after content you came for. Following one passes a small, fixed set of values so the destination knows where you came from:

the page path you came from;
the insurance family and line, as fixed values;
the tool name, if you came from a tool;
a completion percentage rounded to the nearest ten, if you came from a tool.

Your question and anything you typed into a tool are never included. Personal information is collected only if you choose to provide it in Bollinsure's own disclosed intake, which is a separate site with its own privacy terms.

Third parties

Fonts are served from this site, not from a font CDN, so no third party sees your visit.
There is no advertising, no ad pixel, and no retargeting tag.
There is no chat widget, no heatmap, and no session replay.
Links to sources open the publisher's own site. What they do is governed by their policies, and they are marked as external.

Security posture

The site is statically rendered. There is no application server to breach and no user database to leak.
No API secret exists in browser code, because the site makes no authenticated call.
Preview and production are separate environments with separate configuration.
Response headers set X-Content-Type-Options, X-Frame-Options, a referrer policy, and a permissions policy that denies camera, microphone, and geolocation.

Questions about this page

Email quotes@bollinsure.com. If you find a difference between what this page says and what the site does, that is a bug worth reporting, and it will be fixed in the behaviour first.