Privacy Policy
What we keep, and why.
Station Signals shows weather from your own station. To do that it holds a few things about you. This is the whole list.
Last changed November 6, 2026.
The short version. We keep your email, your station's readings and the settings you choose, so the display works. Your Ambient API key is encrypted and never shown again. Your station's exact location never appears on any page. We don't sell your information, we don't show ads and there are no advertising trackers. Ask, and we tell you what we hold or delete it.
- Who we are
- What we collect
- How we use it
- What we don't do
- Who we share with
- Pages and agents
- Cookies
- How long we keep it
- Security
- Your rights
- Children
- Outside the US
- Changes
- Contact
1. Who we are
Station Signals (stationsignals.app) is made by Atom Labs LLC ("we", "us"). We decide what is collected and how it is used, and we are responsible for it. This policy covers the website, the app, published pages and the connection for AI agents.
2. What we collect
What you give us
- Account details: your email and password (stored hashed, never readable). If you sign in with Google, we get your name and email from Google and nothing else.
- Your Ambient Weather API key. It is encrypted before it is stored, with a key kept apart from the database. It is never shown again, not even to you, and it is decrypted only for the moment it takes to read your station.
- Names you type: your household, your station, the place name on the display, sensors, a pet.
- Your settings: slides, templates, routines, alert rules, published pages and the password you set on a page (stored hashed).
- Wait list answers: your name, email, which station and sensors you have, which AI agent you use and any questions you send.
- Messages you send through the contact form or by email.
- Billing, when paid plans open: your card is entered on Stripe's page. We see only the plan, its status and its dates.
What comes from your station
- Readings: temperature, rain, wind, humidity and whatever else your station and sensors report, from the day the station joins.
- Location: your station's coordinates, as Ambient reports them or as you type them. They are used for sunrise, sunset, the moon, the forecast and tides.
- Indoor readings, if your station has an indoor sensor. They are hidden on published pages unless you turn them on.
What is collected automatically
- Server logs: errors and a record of each call we make to Ambient, so we can see why something failed and stay inside Ambient's limits. They never hold your key or your location.
- A one-way hash of your IP address, made with a secret value, when you send the contact form, apply to the wait list or type a page password. It stops spam and password guessing. We can't turn it back into your address.
- Blog view counts: one count per post per browser session. No profile, no identifier and nothing about you is stored with it.
- Alerts: if you turn on phone alerts, the push address your browser gives us.
- AI agents: which agent you connected, when it connected and when it last asked.
3. How we use it
- To run Station Signals for you: read your station, build your display and pages, keep your history and records, send the alerts you ask for and answer your agent.
- To sign you in, keep accounts secure and stop abuse.
- To reply to you and to send service email: password resets, renewal notices and changes to these policies.
- To bill paid plans, when they open.
- To fix problems and decide what to build, using counts of how features are used.
- To meet legal duties.
We send no marketing email unless you ask for it, and every such email lets you stop it in one step.
4. What we don't do
- We do not sell or rent anything about you.
- We don't share it for targeted advertising, and we show no ads.
- There are no advertising or cross-site trackers on these pages.
- We don't use your readings or messages to train AI models.
5. Who we share it with
Only the services that do a job for us, each getting the least it needs and bound to use it only for that job.
| Service | What it gets | Why |
|---|---|---|
| Ambient Weather | Your API key, from our server | To read your station. |
| National Weather Service and Open-Meteo | Your station's coordinates | The forecast for your spot. |
| NOAA Tides and Currents | Your station's coordinates | Tides, when your station is near the coast. |
| Supabase | Everything in section 2 except card details | Runs our database and sign-in. |
| Lovable | Page requests | Hosts the site. |
| Cloudflare | Page requests and IP addresses | Delivers the site and protects it from attacks. |
| Your sign-in, if you use Google | Signs you in. | |
| Resend | Your email address and the message | Sends service email and delivers contact and wait list mail to us. |
| Your browser's push service (Apple, Google or Mozilla) | An encrypted alert it can't read | Delivers phone alerts you turn on. |
| Stripe | Your card and billing details, entered on Stripe's page | Takes payment when paid plans open. Your card never touches our servers. |
We may also share information if the law requires it, to protect someone's safety, to enforce our Terms of Service, or with a business that takes over Station Signals. In that last case this policy keeps applying to what you gave us, and we tell you before anything changes.
6. Your published pages and your AI agent
A published page shows readings, your station's name and the place name you typed. It never shows your coordinates, and it shows indoor readings only if you turn that on. You decide whether it needs a password. An open page can be seen by anyone with the address. Change the password and every screen showing the page asks for the new one.
An agent you connect can read what the display reads: readings, history, the forecast and the names you typed. It never sees your API key, your coordinates or another household, and it can change nothing. What you ask the agent, and what it does with our answers, goes to the agent's maker under their privacy policy, not ours.
A template you share to the gallery shows its name, description and layout to other households. It never carries your readings or your location.
7. Cookies and browser storage
We use one cookie and a few browser storage items. All of them are needed for the site to work. None follows you to other sites.
| Name | Kind | What it does |
|---|---|---|
| kwd-page-… | Cookie | Remembers that a screen typed a page's password. It lasts until the password changes or you clear it. |
| sb-…-auth-token | Local storage | Keeps you signed in. Signing out removes it. |
| Hint flags | Local storage | Remembers that you closed a tip on a display, so it doesn't come back. |
| ss-blog-viewed:… | Session storage | Counts a blog post once per visit. Gone when you close the tab. |
Cloudflare may set its own security cookie to tell people from bots. Because we don't sell or share information for advertising, there is nothing for a Do Not Track or Global Privacy Control signal to turn off, and we treat either as a request not to.
8. How long we keep it
| What | How long |
|---|---|
| Account, settings and station readings | As long as the account is open, so your history and records keep working |
| The full packet your station sends | 7 days (the readings themselves stay) |
| Ambient call log | 30 days |
| Error log | 90 days |
| Page password attempts | 24 hours |
| Push address | Until you turn alerts off |
| Agent connections | Until you disconnect the agent |
| Wait list answers and messages | Until we no longer need them to answer you or run the wait list, or until you ask us to delete them |
| Billing records | As long as tax and accounting law requires |
When you ask us to close your account, we delete it and everything above within 30 days, except what the law makes us keep. Backup copies roll off on their normal schedule.
9. Security
Data travels over HTTPS. API keys are encrypted with a key kept outside the database. Passwords are hashed. Each household can reach only its own data, and that rule is enforced in the database itself, not only in the app. Only the operator of Station Signals can reach household records, for support and to keep the service running. No system is perfectly secure. If a breach affects your information, we tell you as the law requires.
10. Your rights and choices
Wherever you live, you can ask us to:
- tell you what we hold about you and give you a copy, including your station's history;
- correct anything that's wrong;
- delete your account and everything about it;
- stop any use you object to.
Write to team@stationsignals.app from the email on your account. We confirm it's you and answer within 30 days. If we say no, we tell you why, and you can ask us to look again. We never charge for this or treat you differently for asking.
You can also act on your own: change names and settings in the app, delete or replace your API key, turn alerts off, disconnect agents and unpublish pages.
Residents of California and other US states with privacy laws have these rights by law. We don't sell or share personal information as those laws define it, and we don't use sensitive information to infer anything about you. If you are in the European Economic Area or the UK, you can also complain to your data protection authority.
11. Children
A Station Signals display is made for the whole family to look at, and it collects nothing from the people watching it. Accounts are for adults 18 and over. We don't knowingly collect personal information from children under 13. If you think a child has given us information, tell us and we delete it.
12. If you're outside the United States
We run Station Signals from the United States, and your information is processed there and where our providers operate. If you are in the European Economic Area or the UK, our legal basis for each use is: running the service you signed up for (account, station, display, pages, alerts, agents); our legitimate interest in keeping it secure and improving it (logs, IP hashes, usage counts); your consent where we ask for it (alerts); and legal duty (billing records). Where your information leaves your country, we rely on our providers' standard contractual safeguards.
13. Changes to this policy
When this policy changes, the date at the top changes. If a change affects what we collect or who we share it with, we email members at least 30 days before it takes effect.
14. Contact
Questions or requests go to team@stationsignals.app or through the contact page. Station Signals is made by Atom Labs LLC.