Privacy Policy

Version 2026-08-18 · Effective 18 August 2026

Most privacy pages ask you to trust a policy. This one describes an architecture. The app was built so that the most revealing things about you either never exist on our side, or exist only in a blurred form.

It describes the app as actually built, and the version in force is recorded with your in-app settings.

The thing we store on your device

We store one item on your phone and read it back each time you open the app: a cryptographically random token, generated the first time you launch it. It is not derived from anything about you or your handset, and it is the only reason the app can remember your saved places and preferences between sessions.

It is held in your phone's secure credential store and marked so that it is not included in iCloud backup or in phone-to-phone transfer.

One honest limit. If that secure store is ever unavailable, the app falls back to ordinary app storage. That copy is still excluded from your device backup, but it is not encrypted, so on a phone that has been jailbroken or rooted, it could be read. Nothing else about you sits alongside it.

What it is used for:

• Remembering your settings and saved places. Without this the app cannot work
• Understanding which parts of the app get used, so we can improve it; you can switch this off
• Building the anonymous group statistics described below; you can switch this off separately

It stays until you use Delete all my data. On iPhone, deleting the app alone may not remove it: Apple keeps secure-store entries until the app itself clears them, so if you reinstall, the app may pick up where it left off. Delete all my data removes it for good.

We tell you this separately because the law on storing information on your device requires it, independently of everything else on this page.

Who we are

Yellowstone Global Partners Ltd, a company registered in England and Wales under number 17210635, registered office 44 Hartford Avenue, Harrow, Middlesex, HA3 8SY, United Kingdom, trading as Climaweather, is the data controller for everything described here.

Contact us any time at support@climaweather.com. We reply within one month, and we will tell you if we need longer.

There is no account

No sign-up, no email address, no password, no profile. The app does not ask for your name, your email address or your phone number, so we do not have them to lose, sell or hand over.

Your device is identified only by the random token described above.

What we collect

Your answers

Activities, commute times, comfort preferences, the age bands of any children you are getting ready in the morning, school-run times. These tune the forecast to your day. Every one is optional and every one is editable, and skipping them costs you accuracy, not access.

Legal basis: our legitimate interest in providing a personalised forecast. We rely on legitimate interest rather than contract precisely because these answers are optional: data you can skip is not necessary to perform an agreement, and it would be wrong to claim otherwise.

Kept while you use the app; erased after 18 months without any activity we record, or the moment you delete your data.

Where you are

Only with your permission, and blurred on your phone before it is sent anywhere. Your coordinates are snapped to a grid, so what reaches us is a small area rather than a point: a little over two kilometres north to south wherever you are, and narrower east to west the further you live from the equator: a little over two kilometres at the equator, about a kilometre and a half in London, and under half a kilometre in the high Arctic. Our servers do not receive your exact position.

There is one exception, described under Where your data is held: when the map is open your phone contacts Mapbox directly, and Mapbox sees the area of the map you are looking at.

We store the name of the area your coordinate falls in alongside it, so the app can label the place it is showing you.

Your phone works out exactly where you are. Our servers do not. Full-precision coordinates stay on the device: the app uses them to point the map and to name the place you are in, and every forecast request is rounded to the grid before it leaves.

If you set a home town by hand instead, it is stored at the same coarse precision. The coordinates of the places you save and the trips you plan are rounded the same way on your phone before they are sent. The names you give them are not: a destination or label you type is sent as you wrote it.

Legal basis: our legitimate interest in showing you the forecast you opened the app to get. Your phone's location permission controls whether we receive your device's location, and you can withdraw it at any time in your device settings. A home town you type in yourself is sent whether or not location permission is on; you gave it to us directly rather than through the sensor.

A note on the store labels. Apple's listing says data is "linked to you". That reflects the random token we attach so the app can remember your settings; it is linked to your device. It does not mean we know who you are, and we would rather the label over-state the link than under-state it.

What you do in the app

A fixed, closed list of 17 interaction types: which screens you open, which cards you tap, whether you finished setting up. Tied only to the random token. No free text you type is included, and we do not attach your location to them. We cannot add a new kind of event without changing the app, and we will change this page when we do.

Kept for 30 days, then deleted automatically.

Individual records are the raw material for counting, not something we keep to look at later.

In the United Kingdom, the United States, Australia, New Zealand, Hong Kong and Mexico this is on by default. Everywhere else it is off until you turn it on. You can change it at any time in Profile → Privacy & data, and the switch takes effect immediately.

Legal basis: our legitimate interest in knowing which parts of the app work.

Crash reports

When the app crashes or freezes, a technical report goes to Sentry, our error monitoring provider. It carries your device model, your operating system version, where in the code the failure happened, and a one-way digest of your token. Coordinates are stripped from crash reports before they are sent.

Sentry does receive your IP address, because a crash report has to travel from your phone to reach them, and no setting on our side changes that. We have turned on their setting that prevents IP addresses from being stored, so it is used to deliver the report and then discarded rather than kept against it.

This is on by default and you can turn it off in Profile → Privacy & data.

Two honest limits, and we would rather state them than have you discover them.

First, turning it off stops the app sending new reports straight away, but the crash reporter we bundle also watches at a lower level, below the app's own code, and a report from that layer can still reach us.

Second, a report about a crash that already happened may still arrive when the app next starts. Your phone writes it at the moment of the crash, before it can ask us anything, and sends it on the next launch.

Legal basis: our legitimate interest in an app we can fix.

Retention: 30 days.

The address your device connects from

We cannot avoid seeing your IP address; it is how the internet delivers the reply. We use it for two things.

First, to count requests, so that no single source can overload the service or exhaust the shared daily weather allowance everyone depends on.

Second, to work out which country you are in when you set or change a privacy choice, because the rules that decide what is on by default differ by country. We look the address up on our own servers, against a country database stored inside our software. The lookup never leaves our systems, it returns a country and nothing finer, and it is cross-checked against your device's region setting. If the two disagree, or if either cannot be read, sharing stays off.

The address itself is used for that check and then dropped. It is not kept in your record, only the resulting country is, and it is not used to work out where you are for the forecast.

Our server logs. In normal running, your IP address is not written to them. If we raise the level of detail while investigating a fault, it can appear, and it can also appear in the record of an unexpected error. Where it does, it is held by our hosting provider, which ages logs out on its own schedule, and then deleted.

Country data attribution. IP Geolocation by DB-IP

Legal basis: our legitimate interest in keeping the service available and controlling the cost of running it for free.

App update checks

No update check runs today. The app is built to be able to fetch a corrected version without waiting on a store review, but no update channel is configured, so nothing is requested and nothing is sent. If that changes, this section and the provider list below change with it.

Legal basis: our legitimate interest in an app we can fix quickly. This is part of the app working correctly rather than something we measure you with, so it is not covered by the analytics switch.

When you write to us

If you email support@climaweather.com we hold your message and your email address for as long as it takes to deal with it, and for up to twelve months afterwards so we can recognise a follow-up. We do not ask for your identity and we do not connect what you write to your app data. If you type your own name, or someone else's, into a trip or a saved place, that travels with it: the coordinates are rounded, the words you chose are not.

Legal basis: our legitimate interest in answering you.

Notifications: nothing is collected here

If you allow notifications, your phone schedules the alerts itself. The forecast comes from us; the decision to show you a notification, and the showing of it, happen on your device. No push token is issued to us, we store none, and nothing is sent from our servers to your phone. Turn notifications off in Profile → Notifications or in your device settings and the scheduling stops.

What we do not collect

We want to be specific, because "we don't sell your data" is easy to say.

We do not collect your name, email address, phone number, date of birth, contacts, photos, microphone or browsing history.

We do not ask about your health, ethnicity, religion, politics or sexuality. We deliberately removed a question about how easily your skin burns, because the answer would have revealed something about your ethnicity.

Sharing, and the switch that controls it

We do not sell or share personal information as defined by the California Consumer Privacy Act.

The only thing that can ever leave our systems for a commercial partner is group statistics: trends like "walking is popular in rainy climates". Three rules govern every published figure:

1. No group smaller than 50 people is published. If 49 people share a characteristic, that row does not exist in the output
2. Every count is rounded to the nearest ten
3. Nothing identifying is in the file: no token, no coordinate, no free text, and nothing about anyone's family

Who receives them. Nobody outside Climaweather receives them. We build them to understand how the app is used. If that ever changes, we will say so on this page first, and name the categories of recipient before anything leaves us.

We publish a binding commitment not to attempt to re-identify anyone from this data, and no recipient would receive anything without first contractually committing to the same.

The switch is called Contribute to anonymous group trends, under Profile → Privacy & data. Turning it off removes you from every future statistics build, immediately. If you are offline when you change a setting, your choice applies on your phone at once and reaches our servers the next time the app connects.

Where it is on by default. The United Kingdom, the United States, Australia, New Zealand, Hong Kong and Mexico. We work out which country you are in from your connection, cross-checked against your device's region setting, and if those two disagree, sharing stays off.

Everywhere else it is off until you turn it on. Where it is off by default, your contribution rests on your consent, you can withdraw it with the same switch, and withdrawing removes you from every future build.

The question we ask about which climate you are used to cannot turn sharing on. It exists to calibrate what "cold" means to you, because Scotland's cold is not Egypt's, and it is one of the groupings the published statistics are broken down by. It is a one-way veto: it can make your settings stricter and it can never make them looser.

If we publish a browser version, it will honour the Global Privacy Control signal.

Legal basis, where it is on by default: our legitimate interest in understanding, at group level, how weather shapes what people do, so the app can be improved. We have written the balancing assessment down and you can ask us for it. Where it is off by default, the basis is your consent.

Your rights, built into the app

Download my data. Profile → Privacy & data → Download my data gives you everything in our database about your device, immediately, on the device holding the token. Because there is no account, the token itself is how we verify the request is really yours.

Delete everything. Profile → Privacy & data → Delete all my data erases your record from our database and wipes the app's storage on your phone, including the token. It happens immediately.

Deleting removes your record and everything attached to it: the events, your preferences, your consent choices and your trips all go with it, in one operation.

Some things deliberately survive, and rather than say "we delete everything" and be almost right, here is the full list.

There is no backup copy for your data to linger in. Our database is not backed up, so deletion is not waiting on a backup cycle to catch up.

Correct anything. Every answer you have given is editable in the app.

Take it elsewhere. The download is a structured, machine-readable file you can hand to another service.

Object to sharing, or to analytics. The switches above are the objection mechanism and they take effect immediately.

Withdraw consent. Where we rely on your consent you can withdraw it at any time with the same switch. Withdrawing does not affect anything done before you withdrew.

No automated decisions. We do not make any decision about you by automated means alone that has a legal or similarly significant effect.

Asking us to stop. You can turn off sharing and usage data at any time in Privacy & data, and both take effect immediately. You can change or delete your answers, and you can delete your record. If you want us to stop using your information in some other way while you raise a concern, email support@climaweather.com and we will respond within one month.

One thing we cannot do. If you have already deleted your data, or you write from an email address we have never seen, we have no way to find you; there is no account to look you up by. That is the direct consequence of not collecting your identity, and the law expressly allows for it.

Ask us to restrict what we do with your information. If you think what we hold is wrong, or you have objected and we are still considering it, you can ask us to limit what we do with it while that is sorted out. These situations are rare, and there is no switch for this: each one needs looking at by hand, so email support@climaweather.com and we will deal with it within one month.

Complain to us. If you are unhappy with how we have handled your data, you can complain to us directly at support@climaweather.com. We will acknowledge your complaint within 30 days of receiving it, and we will respond properly as soon as we can after that. You do not have to come to us first. You can go straight to the Information Commissioner's Office at any time, whether or not you have raised it with us.

Complain to the ICO. The Information Commissioner's Office is the UK regulator for this, at ico.org.uk.

How long we keep things

One honest caveat. These periods are enforced by jobs running inside our service. If the service is down for a long stretch, deletion pauses until it returns.

Children

Climaweather is for people aged 13 and over. We do not ask your age and we have no way to check it. If you think someone younger is using the app, contact us at support@climaweather.com.

Some answers are about other people in your household, usually children: an age band, or the time of a school run. We keep them in the coarsest form that works: a band, never a date of birth. They are excluded from every statistics build.

We collect them from you rather than from the child. If you would rather we did not hold them, remove them in the app and they are gone.

Where your data is held, and when it leaves the UK

For providers outside the UK, we rely either on that company's certification under the UK Extension to the EU–US Data Privacy Framework, or on the International Data Transfer Agreement, a contract that binds them to UK standards wherever the data sits.

Where each provider sits, and what covers it: our database is in London, and the company we contract with is based in Singapore; that transfer runs on a standard UK contract clause set. Our servers are in Amsterdam, in a country the UK recognises as providing equivalent protection, so no extra mechanism is needed for the location. The companies behind our servers and our crash reporting are US-registered, and those relationships rely on a UK-recognised transfer framework. Our crash reports are stored in Germany.

One exposure we cannot solve with a contract, so we are telling you instead. Our map provider is contacted by your phone directly rather than through our servers. That means Mapbox sees your real IP address and the part of the map you are looking at, and our rounding cannot protect something we never touch.

You can ask us for a copy of any of these safeguards.

Service providers

Companies that process data for us, each under a data processing agreement, on our instructions:

Rate limiting is done in our own server's memory. No other company is involved and nothing is stored.

Companies your device contacts directly, where we are not the intermediary:

No keys in your pocket

Weather data and our own APIs are reached through our backend, where the credentials that must stay secret live: the app does not carry them. The map is the exception: your phone talks to Mapbox directly using a public map token, which is designed to be visible in an app and can only draw maps.

Weather lookups carry no device identifier at all: only a rounded coordinate.

This website

This site sets no cookies and there is nothing here to consent to, which is why there is no banner. The only thing it remembers is your light-or-dark choice, stored on your device.

If the business changes hands

If Climaweather is ever sold or transferred to another company, your data would pass to them as part of the service. We would tell you on this page before it took effect, and the new owner would be bound by this policy until they gave you notice of their own.

Changes to this policy

Every version is dated and numbered at the top, and the version in force is recorded with your in-app settings. When the terms of service change materially, we tell you in the app before the change takes effect. When this privacy policy changes, we show you a notice in the app: the notice does not block you, so a change may already be in force when you first see it.

Questions

Yellowstone Global Partners Ltd
44 Hartford Avenue, Harrow, Middlesex, HA3 8SY, United Kingdom
Company number 17210635
support@climaweather.com
Supervisory authority: Information Commissioner's Office, ico.org.uk