What we collect
Contact submissions contain your category, message, optional reply email and submission time. Outcome reports contain your selected flight context, original weather-score snapshot, reported outcome, optional comments and receipt time. Do not include passenger names, booking references or confidential information.
Why and where
The site administrator uses submissions to reply where appropriate, investigate concerns and assess the service. Records are stored server-side in the Sites hosting platform’s Cloudflare D1 database. Only an explicitly authorised administrator can read messages, email addresses and private notes. Submitted flight outcomes are unverified until reviewed; agreement between visitors is not verification.
Minimal abuse prevention
A necessary first-party cc_feedback cookie lasts up to 90 days and identifies a browser for submission limits and duplicate reports. It is not an advertising tracker or a public account. The server creates a daily keyed hash of the request IP for rate limiting; raw IP addresses are not stored in the feedback database. Hosting and sign-in providers may keep their own security logs. The administrator uses ChatGPT sign-in; public feedback requires no registration.
Retention and deletion
Messages, optional emails, outcome comments and review notes are available for up to 90 days. Cleanup runs in bounded batches during submissions and administrator activity; if the service is inactive, physical deletion awaits the next cleanup. De-identified flight/snapshot records may be retained for up to two years for evaluation. Security-rate records expire after their short abuse-prevention window; administrator audit records last up to one year. Use the private receipt on your confirmation to delete your contact or outcome submission, or raise a privacy concern through Contact & Feedback. No email address is required. The administrator can delete submissions and run retention cleanup.
Notifications and service providers
Email notifications are not connected at launch. No message or email is sent to a third-party email-delivery service by this implementation. Any future sending service needs separate configuration and an updated notice. ChopperChecker collects first-party public-page traffic counts: non-refresh page openings and browser refreshes. No analytics cookie or device identifier is stored in your browser, and query strings, booking details, referrers and form content are not collected for these counters. Random per-page event receipts are retained for up to two days solely to avoid counting retries twice; daily totals are retained for 400 days, and cumulative totals contain counts only. Raw IP addresses are not stored in the analytics database. See the network/browser estimate described below. Admin pages, common bots and browser opt-out preferences are excluded where detectable. Unique people are not measured exactly.
Optional destination statistics
Destination statistics are on by default for the sole purpose of improving ChopperChecker’s coverage and usability. You can switch them off free of charge beside Flight plan & location or in “Optional destination analytics” at the bottom of Flight Outlook. A browser-local preference remembers your choice. Existing switch-offs, Do Not Track and Global Privacy Control are respected. No analytics cookie, stored device ID or advertising profile is introduced. For visitor estimates, the server creates a secret-keyed, pseudonymous hash of the connection address and coarse browser/platform family. The key namespace rotates every 90 days; neither the raw address, full browser version nor a device fingerprint is retained. Shared offshore networks can merge visitors, while network changes can split them, so counts are estimates of browsers/networks, not identified people. These statistics must not be used to identify or target people or groups of people.
Explicit requests contribute to aggregate counts by catalogue ID/name, coarse offshore region and type. Exact custom coordinates, weather values, flight dates and booking details are not collected. Name-like unmatched terms are eligible only on an explicit Search/Enter or forecast request, never on each keystroke. Email-like text, URLs and long numbers are rejected before transmission and again on the server. Please do not enter personal information.
New forecast requests record the server UTC timestamp, catalogue destination ID/name, region/type, action and pseudonymous network/browser estimate for up to 90 days. Private history displays UK local time. Exact custom coordinates, intended flight dates, weather and booking information are excluded. Unlinked retry receipts prevent duplicate counting and expire after 90 days. Older daily-only data is not assigned invented times. Unmatched-term daily aggregates last 90 days, destination daily/hourly aggregates 730 days, and cumulative destination counts indefinitely. Day-level aggregate timestamps describe statistics, not an individual visit. Older explicitly opted-in event records from the previous collection policy expire after 90 days. Expired data is deleted on collection, admin reads or manual cleanup; there is no unattended cleanup job. The administrator can remove an accidentally personal term immediately.
Separate daily keyed hashes support short-lived abuse rate limiting. Pseudonymous visitor estimates linked to timestamped searches and public-page events expire after 90 days. These statistics are used only to understand service usage and improve coverage, not advertising or identifying people. Opting out stops future optional destination and visitor-estimate collection. No third-party advertising or tracking service receives the statistics. A clear notice, free opt-out, purpose restriction, retention limits and access controls support privacy-conscious collection. The network/browser estimate is pseudonymous rather than a claim of irreversible anonymisation. ICO guidance.
Home-screen installation and app-use statistics
The same destination/app-use statistics switch also controls aggregate installation actions: Apple/Android button clicks, native prompt displays, prompt acceptance/dismissal, manual instruction views, browser-reported installations and approximate standalone app openings. Only a browser appinstalled event is counted as a browser-reported installation; clicks and accepted prompts are separate. iOS/manual installations cannot be confirmed universally. Standalone openings are not unique visitors or guaranteed operating-system launches. Coarse platform labels (iOS, Android, desktop or other) are used without retaining browser versions, visitor IDs, destinations or device fingerprints. Daily totals are retained for 400 days; unlinked retry receipts for two days, with cleanup on writes or admin reads. These events are solely for improving installation and site usability and are not added to ordinary page-view totals.
The service worker never stores forecasts, flight data or private admin content. It fetches public navigation from the network and shows a plain offline message if the connection fails. An internet connection is required for current weather, flight status and journey data.
Forecast transparency
The percentage is an uncalibrated weather-suitability score, not verified operational flight odds. Prediction snapshots are timestamped at the server; weather data sent from a visitor’s browser still requires provenance review. Post-departure, unidentified and otherwise unverified records are excluded from verified performance statistics. Delayed flights and cancellations remain separate outcomes. Evaluation does not automatically retrain or alter the forecast algorithm.
ChopperChecker is an independent, unofficial project and is not affiliated with helicopter operators or weather-data providers. The operator and commander make operational decisions. For privacy, data, copyright or legal requests, use the corresponding contact category.
Saved rigs and sharing
Favourites, your default installation, departure heliport, journey direction and weekly flying-hours preferences are saved only in this browser, without an account. Remove favourites or clear site storage to delete them. Shared links contain a public installation identifier, heliport, direction and flight time; recipients retrieve new forecasts. Share images capture the labelled assessment and can be retained by recipients. ChopperChecker does not receive their identity or your contacts.
The optional destination/app-use analytics setting also controls aggregate favourite and sharing actions, including default restoration, copy actions, browser download requests and browser-confirmed share-sheet completion. Completion does not prove delivery. UTC daily counts by installation and action are retained for 400 days; unlinked hashed event receipts prevent duplicate requests and expire after two days. No previous probability is restored from a favourite.