Privacy
SkyEar turns a microphone a security camera already has into an acoustic sensor for aircraft. That means audio, locations and email addresses, so here is exactly what is held and by whom. Last updated 20 September 2026.
If you only look at the map
Nothing is asked of you and nothing is stored about you. There is no analytics script, no advertising, no tracking pixel and no cookie banner, because there is nothing to consent to — the site sets no cookie until you sign in.
Two third parties see your IP address because your browser fetches from them directly: CARTO and OpenStreetMap, for map tiles. Live aircraft positions come from adsb.lol, but your browser never contacts them — the server fetches once and serves everyone the same cached copy, so adsb.lol never sees visitors at all.
If you sign in
Signing in stores one thing: your email address. It exists to send you a one-time link and to own the sensors you add. There is no password, so there is nothing to leak. The session is a cookie that identifies you to the database and nothing else.
Email is sent through Resend, which sees the address and the message. Accounts and sensor data live in Supabase, hosted in the EU (Frankfurt). The site runs on Vercel.
If you run a sensor
Audio never leaves your machine. The camera password never leaves your machine.
The agent runs on your own hardware, connects to your own camera on your own network, and uploads only what it concluded: the time a sound started, how long it lasted, how loud it was, a summary of its frequencies, and which aircraft was overhead if ADS-B explains it. Recordings stay on the machine that made them. Camera addresses and passwords are never sent anywhere, and the project is built so there is no server-side place to put them.
Location is deliberately imprecise. The agent rounds your sensor's position to three decimal places — about 110 metres — before it is uploaded, so the exact spot is never transmitted or stored. The public map coarsens it again, snapping to a grid of roughly one kilometre. Nobody, including the project, can read your address off the map.
Sensor labels are yours to choose and are shown publicly, so name a sensor after a neighbourhood rather than a person or a street number.
Audio clips are uploaded only if you turn that on, per clip, and never automatically.
Recording sound where other people live
A microphone outdoors picks up more than aircraft. The agent is built to keep that local: detections are summaries, not recordings, and clips stay on your disk unless you deliberately send one.
Running a microphone still carries obligations that are yours, not the project's. Point it at the sky rather than a neighbour's window, and do not share clips of people speaking.
How long it is kept
Detections and the aircraft they were matched against are kept indefinitely. They are the measurement the project exists to build — what a sensor heard, and what it missed — and they carry no identifying content.
Your email address is kept until you ask for the account to be removed. Pairing codes expire after fifteen minutes and are single-use.
Your data, and how to get it back or removed
Under the GDPR you can ask for a copy of what is held about you, ask for it to be corrected, ask for it to be deleted, or object to it being held at all. Write to privacy@skyear.lt and say which. Deleting an account removes the address and retires its sensors; past detections stay, without anything linking them to you.
If you think this has been handled badly, you can complain to the Lithuanian State Data Protection Inspectorate (Valstybinė duomenų apsaugos inspekcija, vdai.lrv.lt).
Changes
This page changes when the software does. It is versioned in the repository alongside the code it describes, so the wording and the behaviour move together.