Privacy Policy

Privacy by construction

Your device converts your location into an approximate grid cell — roughly 7 km across — before anything is sent. That cell is the one thing Aerzeit's server ever receives about a location, and it is used only to fetch the local forecast. Your exact coordinates never leave your device, and your filter settings never leave it at all. The cell is never linked to your name, device, or account. No tracking, no analytics, no ads — ever.

What Aerzeit collects

Aerzeit's server keeps exactly two values — neither is linked to you:

In the terms app stores use, this is an approximate location, collected only to make the app work, and never shared or sold.

What Aerzeit does NOT collect:

Why we collect it

One purpose only: to fetch the 48-hour weather forecast for your grid cell from the Aerzeit backend. The grid cell is the minimum unit of data needed to answer the question "what is the weather near me?" — nothing more is collected because nothing more is needed.

How long we keep it

Server (grid cell + last-request time): deleted automatically once nobody has requested a forecast for that cell for 30 days. If you stop using the app, your requests stop, and the cell's record is deleted 30 days after the last request from anyone in that cell.

On-device data (your settings, saved locations, notification history): stored in the app's private storage on your phone. Deleted when you delete a location or uninstall Aerzeit.

Sub-processors

Aerzeit uses these providers. None of them receives anything that identifies you:

Your rights

Regardless of where you're located, you have the following rights over your data:

To exercise any right, email support@aerzeit.app.

Data controller

Aerzeit is operated by an individual based in the United States, not a registered company. If you are located in the EU or UK and have a data protection concern this policy doesn't address, please contact us directly at the address above — we will respond and address it, even though we do not currently have a formally designated EU representative under GDPR Article 27.