Privacy policy
Last updated 17 October 2026
//EYERUS shows public data on a map. It needs very little about you to do that, so it keeps very little: a username, a password hash, and the things you choose to save.
The short version. No email address, no real name, no ads, no analytics, no tracking pixels, and nothing is sold or shared. We never store your device’s location. You can download everything we hold about you, or delete it all, whenever you like.
Who runs this site
//EYERUS is operated by Aeroacer Inc., in the United States. Questions about this policy or your data go to estweakbox@gmail.com.
What we store
| Data | Why | How long |
|---|---|---|
| Username | To identify your account. Pick one that isn’t your real name if you like. | Until you delete your account |
| Password hash | To check your password. We store a salted scrypt hash, never the password itself. | Until you delete your account |
| Recovery codes | Ten one-time codes that let you set a new password if you forget yours. We store a salted scrypt hash of each code, never the code. A code is deleted once it’s used. | Until used, replaced, or you delete your account |
| Sign-in safety | How many wrong passwords were tried on your account in the last hour, and any lock that’s in place because of them. | Cleared when you next sign in |
| Sessions | To keep you signed in. For each device: a hash of a random token, when it was signed in and last used, its IP address and its browser’s user agent. Settings lists your devices (with the end of each address hidden) so you can spot one you don’t recognise and sign it out. | Ends after 3 days without use, 30 days at most, or when you sign out |
| Saved items | The cameras, aircraft, vessels, calls and places you star, with a label and map position. | Until you remove them or delete your account |
| Settings | Which layers and filters you use, your basemap, and the last map view, so the map opens the way you left it. | Until you delete your account |
| Watch zones | The places you ask to be alerted about: the name you give each one, its map position and radius, the kinds of alerts you picked, the nearest town and the place’s time zone, and your browser’s time zone (so a time at a place in another time zone is labelled, like 6:00 PM CDT). | Until you remove them or delete your account |
| Alerts | The latest 100 alerts for your watch zones: what happened, where, when and whether you’ve read it. Also a list of the events you’ve already been alerted about, so none is sent twice. | Alerts: until newer ones replace them, you clear them, or 60 days. The list of events: from a few hours to 90 days, depending on the event |
| Browser notifications | If you turn notifications on in a browser: the push address that browser gives us (on its maker’s push service: Google, Mozilla, Microsoft or Apple), the browser’s encryption key and secret for that address, which browser it is, and which sign-in it was turned on from. Used only to send you your watch-zone alerts. | Until you turn notifications off, sign out on that browser, the push service says the address has expired, or you delete your account |
| Free Pro preview | Until you’ve had a paid plan, the IDs of the cameras you open and of the camera pictures you see on the camera wall or in “cameras nearby” (never when), so the same camera never counts twice toward your free cameras, and when your free preview started. | Until you delete your account |
| Plan | If you buy Pro or open its checkout page: your plan, whether it’s monthly or yearly, any switch between them waiting for the end of your paid period, its status, when it renews or ends, whether it’s set to cancel, whether you’ve had a paid plan before, a Stripe customer reference, and the last Stripe checkout page you opened (so an unused one can be closed). Never your card number. | Until you delete your account |
Apart from the free-preview list above, we don’t store your searches, which cameras you watch, which calls you open, or your scanner listening. To stop password guessing and abuse, the server keeps short-lived counters by IP address in memory; they reset within an hour and are never written to disk. Our own logs record errors only, without map areas or search terms. Our host, Railway, may keep basic request logs (the time, the IP address and the page asked for) for a short while to run the service.
Your location
“What’s near me” asks your browser for your position. The app then centres the map on you and asks our server for the plate readers, cameras and news around that spot. Those requests are signed in like everything else in the app, but the server doesn’t log them or save the area to your account.
To find local news, our server rounds that spot to about 1 km and asks the US Census Bureau’s geocoder which town it’s in. The Census Bureau sees our server, not you.
Your position is never saved to your account. Like any map, the app asks the server for data in the area on screen, and that area isn’t logged either. After you use “What’s near me”, the app also stops saving your map view while you’re looking near that spot, so your home area isn’t saved to your settings or kept in this browser.
Watch zones and spots you save from “What’s here” are different: they are places you pick and choose to keep, so they are stored with your account (see the table above) until you remove them.
Cookies and browser storage
We use one cookie, __Host-eyerus_sid, which keeps you signed in. It is strictly necessary, can’t be read by scripts, and is sent only to this site over a secure connection. When you follow a link to //EYERUS from another site, your browser sends it so you arrive signed in. It isn’t sent with requests other sites make in the background, and nothing on your account can be changed or read from another site. Because it’s the only cookie and it’s essential, there is no cookie banner.
The app also keeps a few small items in your browser:
- In session storage, which is cleared when you close the tab: whether you’ve seen the intro animation, and a cached list of scanner radio systems so the map loads faster.
- If you turn on notifications, your browser installs a small script from this site (a service worker) that shows the alerts we send. It doesn’t store or cache anything and doesn’t see the pages you visit.
- In local storage, which stays until you clear it: the map view you last left (cleared when you sign out), whether the side panel is collapsed or the map is in 3D, whether you last picked monthly or yearly Pro, which free-preview notices this browser has already shown (labelled with your username), and, if you turned notifications on, your username and this browser’s push address, so they aren’t passed on to someone else who signs in here (cleared when you sign out or turn them off; if someone else signs in here first, the notifications turned on by the earlier account are switched off in this browser).
Services your browser talks to
To draw the map and play media, your browser loads some things straight from other services. They see your IP address and browser details, like any website you visit, and their own privacy policies apply. We don’t send them anything about your account.
- Map tiles from CARTO (or OpenFreeMap if CARTO is unavailable), satellite imagery from Esri, the live satellite layer from NASA, and 3D terrain from Amazon Web Services
- Fonts from Google Fonts; map and video libraries from unpkg and jsDelivr
- Live camera video from the state transportation agency that runs each camera
- California (Caltrans) camera pictures and time-lapse frames, straight from Caltrans
- Featured live cameras and NASA’s space station video, from YouTube (in its privacy-enhanced mode) and HDOnTap
- Scanner audio from OpenMHz, and weather radar tiles from the Iowa Environmental Mesonet
- Aircraft photos, straight from Planespotters.net when you open an aircraft
- The vehicle-counting model from Google Cloud Storage, which then runs entirely on your device
Every other camera picture is fetched by our server and passed to you, so the camera’s operator doesn’t see your address for those. News headlines, source links and aircraft photos open the other site when you click them; following one is between you and them.
Services our server talks to
Our server gathers the public data on the map from the agencies listed on the sources page. A few lookups happen because of something you did. They come from our server, not your browser, and carry nothing that identifies you:
- The US Census Bureau geocoder, with a rough point (about 1 km), to name the town for local news
- Google News, with a search such as a town name and “police”, for headlines
- adsb.lol’s route service, with a flight’s call sign, when you look at its route
- Stripe, when you buy or manage Pro (see Payments)
- The National Weather Service and NOAA, with the map position of each watch zone and saved spot (rounded to about 10 m), for the forecasts and tide times in your Pro briefing, and once for each new or moved zone to name its nearest town and time zone
- Your browser’s push service (Google, Mozilla, Microsoft or Apple), if you turned notifications on. Each alert is encrypted so that only your browser can read it: the push service sees that a message went to your browser’s push address, when, and how big it was, but not what it says.
Vehicle counting
The vehicle counter runs in your browser on the public camera image you’re already looking at. It counts cars, trucks, buses and motorcycles. It doesn’t read plates, recognise faces or identify anyone, and its results aren’t sent to us.
Payments
If you buy Pro, Stripe handles the payment. You give your email and card details to Stripe directly; we never see your card number. We send Stripe only an internal account number and the time your account was made, so the payment can be matched to your account, and we keep the plan details listed above. Stripe’s privacy policy applies to the payment itself.
Your choices and rights
- See your data. Account menu, “Download my data”, gives you everything we store about you as a JSON file, including your sessions, the free-preview camera list, your plan details, your watch zones and alerts, and which browsers get notifications. Only the password and recovery-code hashes, and the browsers’ push addresses and keys, are left out.
- Delete your data. Settings, “Delete account”, permanently removes your account, sessions, recovery codes, saved items, watch zones, alerts, notification subscriptions, settings and free-preview list straight away, and ends any Pro subscription. Stripe keeps its own record of past payments, as the law requires.
- Correct it. Change your settings and saved items in the app; for anything else, contact us.
- Stop alerts. Remove a watch zone from its details panel, clear your alert history in Settings, or turn notifications off for a browser there. Signing out on a browser also stops its notifications.
- End sessions. Settings lists every device that’s signed in. Sign out any one of them, or all of them at once.
- Get back in. Forgot your password? Use one of your recovery codes on the sign-in page to set a new one; that signs out every other device. If you’ve lost your codes too, contact us at estweakbox@gmail.com.
Depending on where you live (for example California, under the CCPA and CPRA, or the EU and UK, under the GDPR), you have rights to access, delete and correct your personal information and to not be discriminated against for using them. We honour those rights for everyone. We don’t sell or share personal information as those laws define it, and we don’t use it for targeted advertising. Our legal basis for processing is providing the service you asked for (contract) and keeping it secure (legitimate interest).
How we protect it
Passwords and recovery codes are hashed with scrypt; session tokens are stored only as hashes; every change needs a per-session security token, and requests that other sites start are refused; sign-in attempts are rate limited, and an account locks for 15 minutes after repeated wrong passwords; our server only fetches camera pictures from public internet addresses; the site is served over HTTPS with a strict content security policy. No system is perfectly secure; if you find a problem, please tell us at estweakbox@gmail.com.
Children
//EYERUS isn’t meant for children under 13, and we don’t knowingly keep accounts for them. If you believe a child has made an account, contact us and we’ll delete it.
Changes
If this policy changes, we’ll update it here and change the date at the top. If a change affects how we use data you’ve already given us, we’ll tell you in the app first.