SunSide tells you which side of the plane will be sunny or shaded on your flight. This page covers both the SunSide web app (this site) and the SunSide browser extension — they share the same backend and the same data practices, described below.

Web app

When you enter a flight number and date (or arrive via a shared link), that flight number and date are sent to SunSide's own backend API to compute the sun-position result. No account or sign-in exists, and no cookies or tracking identifiers are attached to that request.

Your recent searches are kept only in your browser's own localStorage, so SunSide can show them back to you on your next visit — this never leaves your device and SunSide's backend never sees it.

The map view loads map tiles directly from OpenStreetMap's tile servers — like any embedded map, that request goes straight from your browser to OpenStreetMap's infrastructure (not through SunSide's backend), so it necessarily exposes your IP address to them the same way loading any other embedded map on any website would.

SunSide uses Vercel Analytics for basic, privacy-friendly traffic metrics (page views, referrers) — it does not use cookies and does not track you across sites.

Browser extension

The SunSide extension detects the flight number and date you're already looking at on an airline or travel-agency booking site and checks it against sun-position data.

What the extension reads

On the specific airline and travel-agency websites listed on the extension page, a content script reads the flight number, date, and departure/arrival airport codes that are already visibly displayed on the page you're viewing. On a handful of these sites, it also inspects that site's own first-party network responses (its own API calls back to its own domain — never third-party ads, analytics, or tracking requests) to find the same information when it isn't otherwise available as plain page text.

The extension never reads passenger names, payment or card details, login credentials, addresses, or any other personal or booking information beyond the flight number, date, and airport codes.

On pages where a flight is detected, the extension also shows a small floating badge on the page itself as a visible shortcut to your result — it displays only the same flight number/date already described above and can be dismissed at any time; it reads or sends nothing beyond what's already covered in this policy.

What gets stored, and where

Detected flight number/date pairs are kept in the browser's local, per-tab chrome.storage.session — never synced to a Google account, never accessible to other extensions or websites, and automatically cleared when the tab closes or the browser restarts.

What leaves your device

Nothing is sent anywhere automatically. When you open the extension popup and it shows a result, only the flight number and date are sent to SunSide's own backend API to compute the sun-position result — the same two values already visible on the page you were on. No account, no cookies, no tracking identifiers are attached to that request.

If you open the popup's Map tab, your browser separately loads map tiles directly from OpenStreetMap's tile servers, the same way the web app's map does.

Permissions

• storage — to hold the detected flight number/date locally, as described above.
• Content-script access to the supported airline/travel-agency domains — to detect flight information directly from the page you're already viewing, so you don't have to re-type it.

What SunSide never does

Neither the web app nor the extension sells, rents, or shares data with third parties, uses data for advertising or creditworthiness purposes, or includes any third-party analytics or tracking SDKs beyond the privacy-friendly traffic metrics noted above.

Changes to this policy

If this policy changes, the "Last updated" date above will change accordingly.

Contact

Questions about this policy or SunSide's data practices: neliia.marchuk@gmail.com