Privacy Policy
SendTemps collects nothing about you.
That is the short version and it is the whole version. What follows says it precisely, because a policy that is vague where it could be exact is not worth reading.
Applies to the SendTemps Android app and sendtemps.org · Last updated 4 October 2026
What the app collects
Nothing. There is no account and no sign-in. It never asks for your name, your email or your phone number. It has no analytics, no crash reporting, no advertising SDK and no advertising identifier. It does not read your contacts, your photos, your files or your calendar, and it cannot: it asks for one Android permission, and that permission is internet. (Android's own libraries add one more, for the app's internal use: no other app can hold it, it asks you nothing and it reaches nothing.)
If you installed SendTemps from Google Play, Android itself may send Google a report when an app crashes or freezes, under your phone's own usage and diagnostics setting. Google shows those reports to me - the phone model, the Android version and the place in the code that failed - and nothing that says who you are. That is Android's, not the app's: SendTemps adds nothing to it and sends nothing of its own.
It never asks for location. When you want a forecast for a place, you type the place. The app does not know where you are and does not try to find out.
The compass button on YOUR WALL reads the phone's own compass, only while that page is on the screen. Android asks no permission for it, and the reading goes nowhere: it sets the wall's aspect, on the phone, and that is all.
What leaves your phone, and where it goes
To show you a forecast, the app has to ask somebody for one. Those requests are the only thing that leaves your device. They go to these services:
- api.weather.gov — forecasts, and the watches and warnings in ALERTS. US National Weather Service.
- radar.weather.gov — radar imagery, requested only when you open radar.
- api.open-meteo.com — forecasts beyond the NWS range, and outside the US.
- geocoding-api.open-meteo.com — turning a city you typed into coordinates.
- air-quality-api.open-meteo.com — air quality, from the CAMS model.
- archive-api.open-meteo.com — past weather, for ON THIS DAY.
- www.ncei.noaa.gov — historical records. NOAA.
- services.swpc.noaa.gov — space weather. NOAA.
A request carries the coordinates of the place you asked about and, like any request on the internet, your device's IP address. Those services can therefore see that somebody at your IP address asked about a particular place at a particular time. That is inherent to asking a server a question, it is not something SendTemps adds, and it is the honest limit of what "nothing leaves the phone" can mean. These are public agencies and an open forecast API, not advertising companies, and each has its own privacy policy governing what they do with it.
The app sends them no identifier of any kind — no account, no device ID, no cookie. Requests are bundled so there are as few as the job needs, and radar is only fetched when you ask for it. Every request is HTTPS; the app refuses plaintext and refuses to follow a redirect down to it.
CRAG MAP draws its map on the phone, from outlines and shaded relief that come with the app: opening it asks no server for anything. Its OPEN IN MAPS button hands a crag's coordinates to the maps app on your phone, as a link would, and only when you tap it - or, on a phone with no maps app, opens the place on openstreetmap.org in your browser; either then works under its own privacy policy.
The address in the app's ABOUT, and MOVE PIN and ADD A CRAG on CRAG MAP, open the mail app on your phone with a message to jeff@sendtemps.org started: its subject filled in and, from the map, the coordinates you chose and anything you wrote. Nothing is sent unless you send it, and what you send is read by one person and used only to answer you and fix what you found. On a phone with no mail app, the map's report goes to your clipboard instead.
What stays on your phone
Your cities, your walls, your trails, your temperature bands, your saved days and your settings are stored on the device and nowhere else. They are not synced, not uploaded, and not backed up — the app opts out of Android's backup and device-transfer system deliberately, so this data does not travel to Google's servers or to a new phone.
Deleting it: uninstall the app and it is gone with it. There is nothing held anywhere else to request the deletion of, because nothing was collected in the first place.
This website
sendtemps.org sets no cookies and runs no scripts, so there is nothing stored in your browser and no analytics of any kind. The web server keeps an access log, as servers do — but the client address, the port and every request header, the user-agent included, are stripped before the line is written. What remains is a time, a path and a status code. It can tell how many times the app has been downloaded. It cannot tell anything at all about who downloaded it.
Sharing and selling
There is nothing to share and nothing to sell, and none of it is done. No data is transferred to advertisers, data brokers or anyone else. There is no advertising in the app and there never will be.
Children
SendTemps is a weather app for climbers and is not directed at children. It collects no personal information from anyone, of any age.
Changes
If this policy changes, the date at the top changes with it, and anything that materially affects what is collected will be said plainly on the front page rather than buried here.
Who to ask
SendTemps is made by one person, Jeff, under the name Crustware, in Kentucky, USA. Questions about this policy or about anything the app does: jeff@sendtemps.org.