Skip to main content
DQF Expiration Tracker
  • Tracker
  • Guide
  • Privacy
  • Terms
Last rule update: 2026-11-13·Estimated dates, not legal advice

Legal

Privacy Policy — DQF Expiration Tracker

How the DQF Expiration Tracker handles driver labels and dates locally, and what optional anonymous analytics (bucketed counts, page path, device type) are recorded with your consent.

Last updated: 2026-11-13

Summary

The DQF Expiration Tracker is a free, single-page tool. The driver labels and dates you enter are stored in your browser's localStorage and are never uploaded. Analytics are optional: if you accept, we record anonymous, aggregated usage events (page path, device type, referrer host, bucketed counts). If you reject, the tracker works the same and we only receive event names and counts. You can export a JSON backup or delete your data at any time.

What this build stores in your browser

  • Driver label or nickname (optional). Used only for display in your browser.
  • Document dates you enter for the medical certificate, MVR, CDL, annual review, road test, and employment verification.
  • CDL switch, which controls whether a CDL expiration is included in the calculation.
  • Record metadata: a random identifier, a last-modified timestamp, the schema version, and the site identifier.
  • Your analytics choice, stored under the key dqf_consent_v1.

Tracker records are stored under the localStorage key dqf_tracker_v1. If saved data cannot be read, the original text may be moved to a quarantine key beginning withdqf_tracker_quarantine_ so it is not silently overwritten. You can download that text from the warning banner and then delete it through your browser's site-data controls.

Optional analytics (your choice)

Analytics are off until you choose. The banner asks after your first interaction, and both "Allow analytics" and "Reject" are always available. If you allow, the page sends events to our own first-party endpoint /bff/dqf-tracker/track. We do not load third-party analytics, advertising, or social scripts.

Event rows can contain:

  • Event names such as page_view, tracker_started, driver_added, result_viewed, json_exported, json_imported, data_cleared, dwell_recorded, and error_shown.
  • Bucketed counts such as "1 driver", "2 drivers", or "3–5 drivers"; overdue counts as "0", "1", or "2 or more". Exact counts are not sent.
  • Context fields: page path, device type (desktop, tablet, mobile), referrer host, a time-on-page bucket, a render time in milliseconds, and fixed error codes.
  • Session and visitor identifiers: a random session identifier stored in sessionStorage for the tab session, and a salted, one-way hashed visitor identifier computed on the server. We do not keep your IP address in analytics records.

Never recorded: driver names or nicknames, any document date, CDL dates, the contents or file name of an exported or imported backup, your email address, or the full URL including query string. Tracking is decoupled from your driver records: even if localStorage is blocked, aggregated analytics still work.

If you reject analytics, the tracker sends only anonymous aggregate rows — the event name and a count — with no business fields, no page path, and no identifiers. Refusing does not reduce the functionality of the tracker.

You can change your choice at any time:

What this build does not collect

  • No account, login, or email address is required.
  • No advertising, social, or third-party analytics script is loaded.
  • No payment information is collected. Payments are not available in this build.
  • No email reminders are available in this build.
  • No driver data is sent to a server for calculation. The calculation runs in your browser.

The static site and API may be delivered by hosting providers that keep standard access logs, such as an IP address and request time, as part of normal web serving. API requests for analytics are configured not to write access logs. We do not connect hosting logs to the data in your browser.

Where the data lives and how long it is kept

The data lives in the browser profile you use. It stays there until you delete it, clear the browser's site data, or the browser removes it under its own storage policies. It is not synced between browsers, devices, or profiles. If you use private browsing, the browser may discard localStorage when the private session ends.

If the browser blocks localStorage, the tracker switches to memory mode and shows a persistent warning. In memory mode, data is kept only for the current page session and is lost when the tab closes. Export a JSON backup if you need to keep the data.

How to access, export, or delete your data

  • Access: open the tracker. The entered drivers and dates are displayed in the page.
  • Export: use "Export JSON backup" in the Saved data panel. The file is created in your browser; it is not uploaded.
  • Delete one driver: use "Remove driver." You have five seconds to undo the removal.
  • Delete everything: use "Clear all driver data" and confirm. The tracker asks you to download a backup first.
  • Delete through the browser: clear site data for this domain in your browser settings.

An exported backup contains the labels and dates you entered. Treat it like any other record file and store it somewhere private.

California privacy notice (CCPA/CPRA)

This build does not sell or share personal information, and it does not use analytics for cross-context behavioral advertising. The driver labels and dates you enter stay in your browser; the operator does not receive them. Analytics, when you allow them, are limited to the aggregated usage events described above. Because the operator does not receive the driver labels or dates, a request to access or delete that data is usually fulfilled by the controls described above. If you believe the operator holds personal information about you, contact us using the address below and we will review the request.

Children

The tracker is intended for commercial drivers and fleet operators. It is not directed to children, and we do not knowingly collect information from children.

Changes to this policy

If a future version adds payments, email reminders, or new analytics fields, this page will be updated before those features are enabled. The "Last updated" date at the top shows the current version.

Contact

Privacy questions: apj56423@gmail.com.

DQF Expiration Tracker

A free date tracker for owner-operators and small fleets. Driver data stays in your browser.

These are estimated dates based on the information you entered and 49 CFR Part 391. This is not legal advice and does not guarantee compliance or audit results.

  • Tracker
  • How to build your first DQF
  • Privacy policy
  • Terms of service
  • llms.txt
Last rule update: 2026-11-13·Version 1.1.0·Based on FMCSA Part 391