Data controller
The controller of the data collected by the Astronow.pl website and the mobile apps
"AstroNow" and "Transit Detector" is Kamil Zaras, who runs this project as a non-commercial
hobby. For anything related to your personal data, contact me at
kamilzaras95@gmail.com.
What data we collect
1. Browsing the website (cookies and similar technologies)
When you open the website, we ask for your consent to cookies. If you agree, we use:
- Microsoft Clarity for anonymous analysis of how the site is used (clicks,
scrolling), which helps me improve it.
- PostHog (servers in the European Union) for visit statistics, session
recordings (clicks, scrolling and how the page looked; anything typed into form fields is
masked) and error reports for the website and the web transit detector. It helps me
understand how the site is used and fix problems.
- Meta Pixel, a marketing tool from Meta (Facebook/Instagram).
- Google Tag Manager, a technical container that manages the tools above.
It does not collect data itself, but it can load additional analytics scripts.
You can decline in the cookie banner, in which case Clarity, PostHog and Meta Pixel do not
collect any data (PostHog is not loaded at all). You can change your decision at any time by clearing your browser data for this
site (the banner will appear again).
2. Sighting reports (aurora and noctilucent cloud maps)
Reporting a sighting, whether through the form on the website or in the mobile app, works
without an account. We store:
- the location (latitude/longitude),
- optionally: the city name, a comment and a photo,
- the intensity of the sighting and its height above the horizon,
- a hashed IP address (irreversibly hashed with SHA-256), used only to limit the number
of reports per day and to prevent abuse. We never store your IP address in readable form.
Reports are publicly visible on the map (on the website and in the app) for a limited time
(usually a few to several hours), but they remain in the database permanently unless they
are removed by moderation or at your request.
3. The "AstroNow" mobile app
The app does not require an account or any personal details (name, email). We collect:
- Device location (with your permission, which we ask for on first launch),
used to calculate the noctilucent cloud visibility window above your horizon and to show
reports near you. Without permission, we use an approximate location (the centre of Poland).
- A push notification token (Firebase Cloud Messaging, a Google service), so
we can alert you when someone nearby reports a sighting or when aurora conditions improve.
Together with the token, we store your preferences (whether you want alerts, quiet hours)
and the approximate location of the device.
- Usage statistics and analytics: the app uses Google Analytics (Firebase)
and Microsoft Clarity to see which screens and features you use, how long sessions last
and how you move around the app (Clarity also records anonymous sessions and screen
interactions). Device/installation identifiers and an approximate location (based on IP
address) are collected, but not your name, email or any other data that directly
identifies you.
The push token is linked only to a device, not to you as a person. We don't know who you
are, only that some device wants to receive notifications for a given area.
4. Transit Detector (website and the Transit Detector mobile app)
Both the browser version (with your browser location permission) and the "Transit Detector"
mobile app (using your phone's GPS) use your location to calculate the position of the Sun
and the Moon above your horizon and to detect aircraft passing in front of them. A few
important differences from the rest of the service:
- To find aircraft, your location is sent directly to the external service
airplanes.live (an air traffic data provider), bypassing our server. We do not
store this location.
- To know how high above sea level you are, the app sends your coordinates to our server
(astronow.pl/api/elevation), which looks up the terrain elevation in the public
OpenTopoData service. We keep the result for up to 90 days together with
the coordinates rounded to about 100 m, so we don't have to ask again. This cache is not
linked to your device or IP address.
- Settings (search radius, aircraft type filters, alert thresholds, radar theme, units) and
the history of completed transits are stored only locally, in your browser
(localStorage) or in the app's storage on your phone. They are not sent to our server and
we have no access to them.
- Transit notifications in the mobile app are generated and shown locally on your device,
without our server or any third-party push service.
- If you use the community gallery (submitting a photo of a "caught"
aircraft), that submission, unlike live transit detection, is sent to our
server: the location (latitude/longitude), the country code, optionally the city
and a comment, the photo, the nickname you choose and an anonymous device identifier (no
account, no name or email). The submission, photo, nickname, country and any comments or
reactions are publicly visible in the app's gallery. We store a hashed IP
address only to enforce a daily limit on submissions and comments.
- When you report someone else's photo or comment for moderation, the reason
you give, your anonymous device identifier and your IP address are sent to the moderator
(by email) to assess the report and prevent abuse of the reporting feature.
- The country code is determined on your phone from the photo's location using Android's
geocoding service (on most phones this is provided by Google Play services, so the
coordinates are sent to Google), or, if that is unavailable, from the country of your
mobile network.
- When you browse the gallery with the "Near me" filter, the app sends your location to our
server only to pick photos taken nearby. We do not store it.
- Usage statistics and crashes: the mobile app uses Google Analytics
(Firebase) to see which tabs and features you use, and Firebase Crashlytics, which
automatically sends us a report (phone model, Android version, error details) when the app
crashes. We also use Microsoft Clarity, which records anonymous sessions and screen
interactions (taps, scrolling) and creates heatmaps, so we can see how the interface is
actually used.
- PostHog (servers in the European Union): in the Transit Detector mobile
app it records sessions (the app's screen, taps, moving between tabs), collects usage
events, technical data (phone model, Android and app version, language, time zone), your IP
address and the approximate location derived from it, logs and error reports. This data is
linked to an anonymous installation identifier (the same one used in the gallery).
Text you type into fields (comments, nickname, city, report reason) is masked in
recordings. Recordings do not include other apps or the rest of your phone.
- None of these tools collect your name, email or any other data that directly identifies
you.
Who we share data with
Data goes only to the providers of services I use, and only as far as their function requires:
- Google / Firebase: push notifications, usage statistics (Google Analytics),
crash reports (Crashlytics) and, in the Transit Detector, determining the country of a
gallery photo,
- Microsoft (Clarity): traffic analysis on the website (with your consent)
and in the mobile apps,
- PostHog (PostHog Inc., data stored in the EU): usage statistics, session
recordings and error reports on the website (with your consent) and in the Transit Detector app,
- Meta (Pixel): marketing on the website, with your consent,
- airplanes.live: only in the Transit Detector; your location is sent
there directly from your browser/app, bypassing our server,
- OpenTopoData: only in the Transit Detector; our server sends it the
coordinates of your observation point to look up the terrain elevation (without your IP
address or any device identifier),
- the hosting provider of the server that runs the website and the database.
I do not sell your data or share it with anyone for commercial purposes.
How long we keep data
This is a small hobby project and there is no automated clean-up of old data yet. Sighting
reports, photos and push tokens are kept indefinitely, until they are removed manually by
moderation or at your request (see below). Cached terrain elevations expire after 90 days.
We are working on improving this.
Your rights
Under the GDPR, you have the right to:
- access your data,
- have inaccurate data corrected,
- have your data deleted (the "right to be forgotten"),
- restrict or object to processing,
- lodge a complaint with a data protection authority: in Poland, the President of the
Personal Data Protection Office (UODO), or the authority in your country of residence.
To delete your submission, withdraw consent for location or notifications (you can also do
this yourself in the app's settings and in your phone's permission settings), or ask anything
about your data, write to
kamilzaras95@gmail.com.
Changes to this policy
This policy may change as the website and apps develop. Check the "last updated" date at the
top of the page. We will try to announce significant changes clearly. If the English and
Polish versions ever differ, the Polish version prevails.