Useful traffic data without personal profiles.

CausewayPulse is designed to provide live traffic information without requiring an account.

Crossing reports

When you submit a report, we store the checkpoint, direction, duration, approximate completion time, a limited source label and one-way anti-abuse identifiers. The form does not request your name, phone number, email, vehicle number or precise location.

Anonymous crossing-report rows are retained for up to 120 days so CausewayPulse can calculate its 90-day community patterns, then removed automatically.

Operational data

Our hosting provider may process standard security and request logs needed to operate and protect the service. A random identifier is stored on your device for repeat-report checks. The application converts that identifier and a daily connection-and-browser signal into separate one-way hashes; raw connection addresses and full browser strings are not stored in the report database. Rate-limit counters expire within four hours, hashes are never displayed publicly, and they are not used to build a personal profile. We do not sell crossing reports as personal data.

To improve the report form, CausewayPulse counts form views, first interactions, submission attempts and outcomes in hourly aggregates. These 30-day counters contain only an event count, language, limited source label, checkpoint and direction. They do not store a raw device identifier, connection address, name or contact detail, and they never influence the public traffic signal.

Advertising links

Clearly labelled advertising links may include campaign parameters so an advertiser can measure visits. An advertiser’s site is governed by its own privacy policy.

Local device settings

Advertising-consent choices are stored in your browser so the site can remember whether Google advertising may load. CausewayPulse currently requests non-personalized Google ads only. These may use ad storage for purposes such as frequency capping, aggregated reporting, security and fraud prevention after you allow advertising.

To make repeat visits faster on weak mobile connections, the latest successful official traffic-camera response may be kept on your device for up to four minutes. Cached images are always shown as delayed while a fresh official update is requested, and the cache contains no account or journey information.

Google explains how it uses information from sites that use its services in its Business Data Responsibility notice.

If you enable a traffic-threshold alert, the chosen checkpoint, target time and last-notification timestamp are stored only in your browser. CausewayPulse does not require an account for this feature.

If you choose a preferred checkpoint on the mobile home screen, that preference is stored only in your browser so the same live view opens first next time.

Updates

This notice may be updated as new features are added. Last updated: 2 August 2026.