Privacy & Analytics

Last updated: August 18, 2026

FloridaLicenseIndex uses Google Analytics to understand how this site is used — for example, which pages are read and whether the license search is helping people reach official records.

Ordinary pageview measurement

Like most sites using Google Analytics, ordinary pageview measurement may include the address (URL) and title of the page you view, the page that referred you here, information about your device and browser, and approximate geographic information. This data is handled and processed by Google. Because some page addresses on this site include a license number (for example, a license record page), a page address collected this way can include that license number.

Cookies and the Analytics client ID

Google Analytics ordinarily uses first-party cookies, including the _ga cookie. That cookie stores a client ID that Google Analytics uses to distinguish a browser or device and its sessions — for example, to tell a returning browser apart from a new one. This is separate from any FloridaLicenseIndex account or login, because this site currently has neither. Our custom measurement events, described below, do not intentionally add an FLI user ID of any kind as a custom parameter.

Our custom measurement events

Separately from pageviews, this site sends a small number of custom measurement events — for example, "a search was submitted" or "an official-source link was followed." These events intentionally use only coarse, fixed categories (such as which section of the site you were in, or whether a search had zero results). They are designed not to send what you typed into the search box, license or credential numbers, names, email addresses, telephone numbers, mailing addresses, an FLI user ID, the raw address or title of the page you were on, the text of links you click, or the full destination address of a link as custom event parameters.

These custom events are still Google Analytics events. Google may associate each of them with the _ga client ID described above and with the ordinary session, device, browser, and approximate-geography context that Google Analytics attaches automatically. The safeguards described here govern the custom parameters FLI defines (and the three page-context fields FLI overrides with coarse synthetic values) — not the entire Analytics event.

These custom-event safeguards apply to the custom events only. They are distinct from the automatic pageview collection described above, which works the same way here as on other sites that use Google Analytics.

Google's role, and your controls

Google processes Analytics data on our behalf. You can read about how Google uses information from sites that use its services atpolicies.google.com/technologies/partner-sitesand Google's privacy policy atpolicies.google.com/privacy.

Browser privacy controls, content blockers, and similar tools may limit or prevent Analytics collection. The site works normally either way — search, license records, and every link function the same with Analytics blocked.

Questions about this page? Email[email protected]. For how affiliate links work on this site, see theAffiliate Disclosure.