Skip to content

Leebow

Privacy

This policy covers RegattaPages event hosting and Offwind weather routing. The sections name the data each service uses because an event entry and a routing request are different.

RegattaPages event data

Information collected

When you create an account or enter a regatta, we collect the information you enter: name, email address, sail number, boat name, class, rating-certificate details, and the contact details needed by a race committee. Server logs record requests, IP address, and browser to operate the service and investigate abuse.

Use and publication

The data runs scoring, results, and tracking, supports account and regatta email, helps find service problems, and protects against fraud and unauthorized access. We do not send marketing email. Entry lists, crew lists, and results may be public for a regatta, including names, boats, and finishing positions.

Cookies and traffic measurement

After sign-in, RegattaPages sets one HttpOnly, SameSite=Strict, Secure, host-only session cookie. There are no advertising cookies or third-party analytics. Theme preference remains in browser local storage and is not sent to us.

Our traffic collector sets no cookies and stores nothing on your device. It combines IP address and browser string with a random daily salt and stores the resulting hash, never the address; the salt is discarded after two days. It records page, referrer, browser and device type, response time, screen size, and standard performance timings. Read the collector privacy page for detail.

Offwind

Your polar and routes

A pasted polar is normalised for its request, returned to your browser in a no-store response, and held in session memory. It is not logged or stored by default; routes keep only its digest. A polar you deliberately save stores its table and name under your account so you can reuse it. It is not shared or used for analytics, aggregation, or training, and deleting it removes the stored table immediately.

Offwind stores the course, forecast model, departure window, and computed track so share links can reopen a route and accounts can list and rerun routes. These are deleted when the applicable plan retention period ends. Share links are unguessable tokens, not passwords: anyone holding one can see its course, forecast, and track, but not the polar.

Account, logs, and cookies

Offwind stores an email address and person record for sign-in, operational request counts, timings, error traces, job-queue depth, and rate-limit records keyed by account or hashed IP address. These records operate and protect the service; they do not build a profile. Offwind, RegattaPages, and Saildex use one Leebow account and host-only session on this origin; permissions still control private and administrative features.

External services

GRIB files are fetched server-side, so NOAA and ECMWF do not receive your browser visit. Map tiles and bathymetry are served from infrastructure run for the site. When payments launch, card details are entered on Stripe’s pages and never reach this site.

Sharing, protection, and choices

We use hosting and database infrastructure, an account-and-regatta email provider, and Stripe for payments. We do not sell personal information, use an email marketing provider, or send traffic measurement to third parties. We may disclose information where law requires it or to protect rights, property, safety, or the service.

Traffic is encrypted with TLS. Passwords are salted and hashed. RegattaPages data is encrypted at rest, and payment card details are handled on Stripe’s own pages.

You may ask to access, correct, or delete personal information. For RegattaPages, email [email protected]; published results from a regatta you sailed are considered case by case. For Offwind data or product support, use [email protected] or Offwind support.

We may update this policy when practices or legal obligations change. A material change for an account holder will be sent by email before it takes effect.