DMV Fee Calculator Privacy Notice

The registration worksheet runs in your browser without an account. Vehicle values, weights, model years, MPG, fuel classifications, county tax amounts and fee dates entered into the calculator are not included in our usage-event payload. The tool does not need your name, address, VIN, plate number, insurance policy or DMV login. Do not put identifying records into a free-text correction merely because you have them on a notice.

Inputs, result links and browser storage

The worksheet reads the values in its visible controls to produce an itemized receipt. Copy result link places those controls in the URL fragment after the hash character. A fragment is handled by the browser rather than sent as the HTTP request path, but anyone receiving the full link can read and reopen its inputs. Browser history, copied messages, screenshots and printouts may retain those figures. Sharing is your choice; remove the fragment before distributing only the general page.

No registration form is forwarded to an agency, and the site does not process a DMV payment. Following an official source link takes you to that agency's separate service and privacy practices. We cannot delete records that another recipient or an external agency independently retains.

Limited usage events

First-party usage events help locate broken calculators and understand which jurisdiction pages people use. The events table stores a timestamp and day, site, same-origin pathname without query or fragment, event name, bounded event label, page-view identifier, referring host, country header and mobile/desktop category. When present, it also stores a page template and coarse acquisition source and medium. Events include page views, calculator interaction, state selection, successful displayed calculations, scrolling, source links, sharing and printing. They do not send the entered monetary or vehicle fields.

The endpoint reads a request user-agent to drop automated traffic and does not store that string in these event rows. It does not store an IP address in the events or corrections table. Infrastructure providers necessarily receive connection information while delivering requests and may operate their own security logs. This statement describes our application tables, not a promise that network delivery requires no technical metadata.

Cloudflare page performance reports

Our hosting zone adds Cloudflare Web Analytics to every page. Its script comes from static.cloudflareinsights.com and, after the page has painted, posts a timing report to the /cdn-cgi/rum path on dmvfeecalc.com itself. Cloudflare keeps those reports; they never enter our own usage-event or corrections tables. A report can carry how you arrived (navigation type and referring address), your browser and operating system, a page-view identifier, how many bytes loaded and how long that took, and the Core Web Vitals scores. It records the page address with anything after a question mark or hash removed, and the script never looks at the vehicle value, weight or fee-date fields in the worksheet.

Cloudflare receives the report request and processes connection information under its own service policies. A performance report is not a DMV transaction or a saved calculator receipt. Browser privacy controls can prevent that reporting. We keep the existing beacon and its configuration explicit in the published page so a release can be compared to the built HTML without adding another measurement service. Cloudflare's data collection documentation describes these performance measurements.

Corrections are intentionally submitted text

The report form on the contact page sends the problem type you pick, a page path on this site, your explanation and an email if you add one to this site's own report endpoint. Its table stores those fields with a timestamp, day and site. The message is information you choose to transmit, so keep it limited to a public rule, source or reproducible software example. A honeypot field filters automated submissions. The form checks length and origin before saving a report.

Current advertising is disabled and the page does not load an advertising account in this build. Contact the Editorial Team through the form for questions or an access/deletion request, identifying your prior report without adding sensitive registration details. There is no published fixed retention deadline or guaranteed response time. Changes to actual collection behavior require an updated notice.