Help and policyLoading public guidance
Preparing quick answers, policy topics, public data links, and contact paths.
Preparing quick answers, policy topics, public data links, and contact paths.
How we use cookies for sessions, preferences, alerts, and basic measurement.
Choose the topic that matches your question. Each topic explains scope and shows the next action when one is available.
Cookies are small values a site stores in your browser to remember state or preferences.
We use necessary cookies for sign-in, language, forms, security, abuse prevention, preferences, and requested functions.
We may measure page views, wait cards, ads, and alerts to understand what works and improve the site. Our first-party field measurement uses tab-only session storage, not a cookie or persistent identifier.
Public pages, latest waits, history, nearby crossings, wait cards, daily report, and public page lists can be read without a private cookie; preserve credit, update time, and delay notes when reusing them.
Use the data guide or contact us for reuse questions. Account, dashboard, alert, billing, and support cookies stay separate.
Sponsored placements may measure views, clicks, calls, and coupons for business reporting.
If you enable notifications, your browser may store permission and subscription keys. You can revoke permission in browser or device settings.
Private areas use signed session cookies to recognize authorized access without showing private links in the public menu.
Strictly necessary cookies may operate without consent. Where law requires consent for non-essential cookies, a clear accept or reject choice should be shown.
Some browsers send Do Not Track or Global Privacy Control signals. Our first-party field measurement honors both signals and does not collect events when either is active.
You can clear cookies in your browser, block third-party cookies, or avoid functions such as login, alerts, and forms if you do not want storage.
Contact us if this page does not answer your question.