Information processed during normal site use

When you visit NH Fuel Watch, technical request information is processed through Cloudflare infrastructure that hosts and delivers the site. That typically includes standard web-request metadata used to operate, secure, and diagnose the service.

Analytics and error diagnostics (PostHog)

NH Fuel Watch uses PostHog in the browser, after the page hydrates, for privacy-conscious site usage analytics, pageviews, browser and device diagnostics, Web Vitals performance measurements, and browser error reporting.

We use these analytics to understand:

  • Which fuel-provider profiles visitors view.
  • Which provider-published price links visitors click to verify pricing.
  • Which towns and fuel types are useful to visitors, measured strictly through structured identifiers (such as canonical town slugs and fuel types).
  • How users navigate between market listings and local pricing so data coverage, freshness, and site features can improve.

NH Fuel Watch does not use this tracking to determine which provider a visitor purchased from. The site does not operate as an ordering platform, marketplace, or broker.

PostHog processes technical information such as page URLs, browser and device information, pseudonymous visitor identifiers, performance measurements, and browser error details as part of providing analytics. PostHog uses browser storage (such as cookies and localStorage) for session continuity and metric aggregation.

To safeguard visitor privacy, client-side event sanitization scrubs free-form search parameters (such as municipality queries and addresses) from page URLs, referrers, entry URLs, exception messages, stack frames, and event properties before events are dispatched to PostHog. If an event cannot be safely sanitized, it is dropped entirely (fail closed). While automated tests verify this sanitization across outgoing payloads, client-side controls cannot provide an absolute guarantee against every possible browser extension, network proxy, or unexpected client environment.

Session Replay, console log capture, heatmaps, surveys, dead-click capture, advertising tracking, and broad autocapture are disabled. NH Fuel Watch does not use person identification or customer profiling, and does not intentionally send contact-form fields — name, email, or message — to PostHog.

Contact form

If you use the contact form, NH Fuel Watch receives the name, email address, and message you choose to submit so I can respond. Form submissions are emailed to the site operator. NH Fuel Watch does not store contact submissions in the site's D1 database. Submitted messages may remain in the recipient email mailbox under normal email retention.

Cloudflare services

Cloudflare provides hosting and delivery, security services, Turnstile bot verification on the contact form, and contact email delivery. Turnstile processes technical and security signals needed to distinguish legitimate visitors from automated traffic. Turnstile itself does not access, store, or transmit the name, email, or message text you enter in the form.

How this information is used

Technical and contact information is used to operate and secure the site, understand site usage, diagnose performance and errors, respond to messages, and improve data quality and usefulness. NH Fuel Watch does not use the contact form to build advertising profiles and does not sell contact-form information. There are no ads on this site.

Links to provider websites

Provider pages and source links lead to external websites with their own privacy practices. NH Fuel Watch does not control those sites.

Questions

Questions about this privacy notice can be sent through the Contact page.