Privacy Policy — Eos

Last updated: 30 July 2026

Eos is a golden-hour, sun and moon planner for photographers. It is built to do its work on your phone. There is no Eos account, no Eos server, and no Eos database — we could not build a profile of you if we wanted to.

This policy explains the few things that do leave your device, and why.

What stays on your phone

Everything you create in Eos is stored locally and is never uploaded to us:

• your saved spots and their names
• your shoot journal, including any photographs you attach and the notes you write
• your reminders and alarms
• your settings, including your language and theme

Deleting the app deletes all of it. There is no copy anywhere else.

What leaves your phone, and where it goes

Eos works offline for everything physics can answer — sunrise, sunset, golden and blue hour, moon phase, eclipses. A few features need outside data, and those requests necessarily reveal roughly where you are looking. All of them use HTTPS.

Service	What it receives	What it gives back
Open-Meteo	the coordinates you are planning for	cloud-cover forecast, ground elevation
MapTiler	the map area you are viewing	map tiles
Mapbox	what you type into place search	matching places
Wikimedia Commons	the coordinates you are viewing	nearby photographs
NOAA SWPC	nothing about you	a global aurora forecast
Celestrak	nothing about you	the Space Station’s orbit

These services are independent of us and handle data under their own privacy policies. We do not send them your name, your email, your device identifiers, or your saved spots — only the coordinates needed to answer the question.

If you never grant location access, you can still use Eos by choosing a spot on the map, and the coordinates sent are the ones you picked rather than your own.

Analytics and crash reporting

Eos sends product analytics and crash reports to PostHog, hosted in the European Union. This tells us which features are used and when the app breaks. It includes:

• anonymous events describing what was used, such as “a spot was added from the map” — these carry no coordinates
• crash reports and error diagnostics, including stack traces
• a randomly generated identifier for your installation, and standard device information such as model and operating system version

We do not ask for or store your name or email address, and we do not sell data to anyone.

Eos also records anonymised session replays — a reconstruction of what the screen showed — so we can see where the app confuses people. Photographs in your shoot journal are masked and never appear in a replay. Replays do show the map you were looking at, which is the same location information already described above.

Analytics and session replay are disabled entirely in development builds.

How long we keep things

Anything you create in Eos — spots, journal entries and their photographs, reminders, settings — stays on your device for as long as you keep it. We never receive a copy, so there is nothing on our side to delete. Removing an entry removes it; uninstalling Eos removes all of it at once.

Analytics events, crash reports and session recordings are held by PostHog for a limited period and then deleted automatically. They are tied to a random identifier generated for your installation, not to your name or email, so we normally have no way to connect them to you.

If you want us to delete what is associated with your installation, email the address below and we will remove whatever can be identified.

Permissions

• Location — to compute the sun, moon and horizon where you actually are. Optional; pick a spot on the map instead.
• Camera — for the augmented-reality sky overlay, which draws the sun and moon paths over the live viewfinder. Frames are never recorded or uploaded.
• Photos — only when you attach a picture to a journal entry. The photo you choose is copied into the app’s own storage and stays on your device.
• Notifications and alarms — to deliver the reminders you set. Scheduled and fired locally; nothing is sent through a server.

Children

Eos is not directed at children and does not knowingly collect data from them.

Changes

If this policy changes we will update the date at the top and publish the revision here.

Contact

Questions about this policy or your data: kevin.blondel.bernard@gmail.com