Aerzeit

Compliance

Privacy is the foundation of everything Aerzeit does — structural, not promissory.

Most privacy claims are promissory: "we promise not to track you." They require trusting the publisher, today and after every future ownership change. A structural claim is different — the system has nothing to violate it with. Aerzeit makes two structural claims right now, each checkable in exactly one place.

Empty Privacy Manifest

iOS 17 introduced required-reason APIs — a specific list of commonly-abused calls (UserDefaults, file timestamps, system boot time, disk space, active keyboard) that must be declared in a Privacy Manifest. Aerzeit's manifest carries an array called NSPrivacyAccessedAPITypes. It's empty.

The audit goes further than Apple requires — it also covers three calls that aren't on Apple's required-reason list but transitively read UserDefaults under the hood: Calendar.current, Locale.current, and NSLocalizedString. Aerzeit uses explicit, user-driven equivalents for all three instead.

Compliance-only updates

Aerzeit ships once with feature-complete behavior. Subsequent updates are restricted to iOS-compatibility maintenance only — no new features, no new data collection, no surprise changes.

GDPR data minimization (Article 5(1)(c))

The backend receives only an H3 grid cell index (~3 km resolution) — never raw GPS coordinates, your target temperature, your precipitation threshold, or any identifying value. Cloudflare's network handles transient IP metadata for rate limiting; Aerzeit writes nothing to application logs or databases. The built-in data export (Settings → Export my data) is your GDPR Article 15 access right, implemented from day one.

What we don't do