Privacy policy
Last updated 22 September 2026 · is operated by the operator named on the Terms page.
- The planner runs on your device. Where you put the pin is used to compute sun, moon and sky positions locally and is not sent to us unless you save that place to an account.
- You can use the whole free planner without an account. An account (email sign-in) exists so your saved places, lists, preferences and subscription follow you between devices.
- We do not sell personal data, show adverts, or use advertising trackers. Analytics, where enabled, are anonymous feature counts with no session recording.
- Map tiles, forecasts, tides, elevation and other data come from third-party services; those requests carry the coordinates of the area you are looking at (they have to) and your IP address, like any web map.
1. What this covers
This policy covers the web planner and its pages, the public calculator pages, the AR view, and the iOS and Android apps built from the same code. It does not cover the third-party services listed below, each of which has its own policy.
2. Data that stays on your device
- Your pin and the clock — the place and time you plan for, kept in the page address (so a link reproduces your plan) and in the browser's local storage as "where you last were".
- Preferences — units, clock format, map style, theme, panel layout, tips, compass bearings and similar. Stored locally; a few of them sync to your account when you are signed in (see section 4).
- Device location — used only when you press "My location" or open the AR view, only for as long as the browser permission allows, and only to place the pin. It is not transmitted to us.
- Camera and motion sensors — the AR view uses the camera and orientation sensors on the device to draw the sky over the live picture. Frames are never uploaded. The AR calibration and the optional diagnostics recording are kept on the device; a diagnostics file leaves the device only if you choose to share it.
- Photos you import — a geotagged photo is read in the browser to place the pin; the image itself is not uploaded.
- Saved places and lists without an account — kept in the browser's local storage.
3. Data we store when you create an account
| Data | Why | Kept until |
|---|---|---|
| Email address and a sign-in code or link | Signing in; account and billing messages | You delete the account |
| Saved places, lists, notes and logistics (parking, gates, walk times) you add to them | Sync between devices; shared plans and Studio teams you join | You delete them or the account |
| Synced preferences (units, clock, map, theme, tips, compass bearings, eye height…) | The same set-up on every device | You delete the account |
| Subscription status (Pro/Studio, trial dates) | Unlocking paid features on every channel | Account deletion; payment records stay with the payment provider for as long as tax law requires |
| Condition-alert settings and, if you turn them on, a push subscription for this browser or device | Sending the alerts you asked for | You switch them off or delete the account |
| Community spots you contribute | Shown to other users at your choice, with the display name you give | You remove them or delete the account |
Accounts and the data above are stored with Supabase (hosted PostgreSQL and authentication) in the United States (AWS us-east-1). Row-level security limits every record to the account that owns it or the team it is shared with.
4. Payments
We never see or store card numbers. Web subscriptions are handled by Lemon Squeezy as merchant of record; App Store and Google Play purchases by Apple and Google respectively. We receive a confirmation that a subscription exists, its tier and dates, and the email it belongs to.
5. Analytics
Production builds send anonymous, named feature events (for example "terrain traced", "share image made") to PostHog, batched, with a random per-browser id. There is no session recording, no autocapture of clicks or text, and no advertising identifier. When you are signed in, the account id is attached so we can count active subscribers. Development builds send nothing.
6. Third-party services the planner talks to
Each of these receives your IP address and the coordinates of the area or point being looked at, because that is what the request is for. None of them receives your account details.
- Maps — OpenFreeMap (OpenStreetMap data) for the default basemaps; MapTiler for satellite, hybrid and outdoor maps, place search and terrain fallback.
- Elevation — AWS Terrain Tiles (public open data) for horizons, sightlines, shadows and 3D.
- Weather and climate — Open-Meteo (point forecast, model agreement, ERA5 climatology, CAMS air quality).
- Water, snow, night sky — NOAA CO-OPS (tides), USGS (river flow), USDA NRCS (snowpack), NASA GIBS (night-lights imagery), NOAA SWPC (space weather).
- Satellites and comets — CelesTrak and the Minor Planet Center, through our own cached proxy.
- Street-level photos — Mapillary, only when you open that panel.
- Sunset-colour forecast — Skyfire (a partnership service); the forecast is served as pre-rendered map tiles from our storage and needs nothing about you.
- Hosting — Cloudflare Pages serves the site and its API; Cloudflare sees the usual request logs.
7. Cookies and storage
We set no advertising or tracking cookies. The site uses the browser's local storage for preferences, saved places (without an account) and the sign-in session, and a service worker cache so the planner opens offline. Clearing site data removes all of it.
8. Your choices and rights
- Export — saved places and lists export as GPX, KML or CSV from the planner at any time.
- Delete — "Delete account" in the account panel removes the account and everything in section 3 at once, including Studio teams you own; places saved on the device itself stay there; subscription cancellation is separate and done where you bought it.
- Alerts — switch off in the account panel; push permission can also be revoked in the browser or OS.
- Access, correction, portability, objection — email privacy@skyfire.app. If you are in the EU/UK you have the rights under the GDPR / UK GDPR; California residents have the CCPA rights; we honour them for everyone.
9. Children
The service is not directed at children under 13 (or the age of digital consent where you live) and we do not knowingly collect their data.
10. Changes
When this policy changes materially we will post the new version here with a new date and, for account holders, mention it in the app. Earlier versions are kept in the public source history.
11. Contact
Operator · postal address · privacy@skyfire.app