Contact FairlySoon#
For privacy questions or requests about your information, contact FairlySoon at hello@fairlysoon.com.
Your plans stay on your device#
Route planning and weather analysis run in your browser. Saved routes, points, boat settings and preferences use browser storage, including localStorage and IndexedDB. They are not automatically uploaded or synced between devices. Clearing site data can remove these plans and settings.
Your browser requests forecast tiles and place-search results from our services. Those requests can reveal the area you are viewing or searching even though your saved route library stays on your device.
Location#
If you use the location control, your browser may ask permission to share your device location to position the map. If that is unavailable, we may use an approximate area derived from your IP address by Cloudflare. The location endpoint does not store or log that location. You can decline device-location permission and continue using the map manually. Subsequent map and forecast requests may reveal the area being viewed.
Feedback and messages#
Feedback submitted through Feedback in the planning map’s three-line menu is sent to our GitHub issue tracker. It includes your message, any reply email you provide and optional technical details you can review and exclude. These details include browser information, screen size, build number, GitHub commit hash, theme, time and WebGPU availability; the automatic report excludes URL query strings, saved routes and device coordinates.
Anything you type or attach yourself may disclose more. Do not include credentials, invitation links or private voyage details. Email correspondence is used to respond to your enquiry. For private access or security requests, email hello@fairlysoon.com.
Hosting, fonts and analytics#
Cloudflare hosts and protects our services and stores server-side records. It processes network information such as IP addresses, request details and operational logs to deliver and secure the service. Cloudflare Email Sending processes recipient addresses and email content for delivery.
We also use existing server-request logs to understand overall traffic and improve FairlySoon: page loads, approximate country, counts of place-search requests and server errors. A distinct-IP count gives an approximate indication of reach; it is not a count of identifiable people. Our private traffic dashboard receives aggregate counts, not individual IP addresses or visit histories. This measurement adds no browser tracking script, analytics cookies or stored browser identifiers. The underlying operational logs can still contain IP addresses and request information. It does not reveal route calculations or other actions that stay entirely on your device.
The planner loads the Inter font from Google Fonts, so your browser sends font requests to Google. GitHub processes feedback submitted through the feedback form.
The planner uses Traks, hosted in our Cloudflare account, to measure visits and actions such as finding sailing windows, selecting departures and changing forecast layers. It starts automatically without an analytics cookie or a persistent browser tracking identifier. A temporary, in-memory identifier groups actions within an open page; reloading starts a new visit. We do not send route coordinates or names, saved points, boat names, emails, invitation tokens or feedback text to analytics. Page addresses exclude query strings and fragments; referrals include only the referring website.
The collector processes IP addresses and browser information to estimate daily visitors, device/browser categories and approximate country, region and city. Traks stores a site-specific visitor hash that changes each day rather than the raw IP address. Its live view can include approximate city coordinates derived from the network, not your device GPS or planned route. These estimates do not identify a unique person or track returning visitors across days.
Recent events feed the live dashboard; longer-term event history is stored in our Cloudflare R2 data warehouse to show traffic growth and feature use over time. Access to analytics is restricted to administrators. Standalone documentation pages use only the server-request measurement described above. Google Analytics is no longer loaded. Older Google analytics cookies and the previous consent preference are cleared when the planner initializes; you can also remove them by clearing site data.
We use providers as needed to operate FairlySoon and may disclose information where required by law or needed to protect the service and its users. Providers may process information outside your country. Their privacy information is available from Cloudflare, Google and GitHub.
Retention and your choices#
We keep server-side information for as long as needed to operate the service, handle earlier invitation requests, respond to feedback and meet security or legal needs. Invitation credentials are no longer needed for public access; deletion from records and backups may take additional time.
You can clear site data, revoke device-location permission or contact us to request access to, correction of or deletion of information we hold about you, including removal from the waitlist. We may need to verify your request. Depending on where you live, you may also have rights to object, restrict processing, receive a copy of your data or complain to your local data-protection authority.
Clearing browser data does not delete server-side invitation records, and deleting those records does not clear data on your devices. Tell us which you need help with. Local plans have no cloud backup at present.
Changes#
We will update this page when our handling of information changes. Any future cloud-sync feature will explain what is uploaded before you enable it.