Privacy
Last updated May 2026
What stays on your device
Hanase is a local-first app. Everything that drives the experience — installed packs, favorites,
schedule, quiet hours, paused state, the catalog source URL — is stored in standard Apple
on-device storage (UserDefaults and the app's sandboxed Documents directory).
None of it leaves your device unless you explicitly enable iCloud.
What syncs via iCloud
If you're signed into iCloud on your Apple device, a small set of preferences is mirrored across your other devices using Apple's Key-Value Store service:
- The interval between cards, pause state, quiet-hours window
- Which installed packs are enabled
- The catalog source URL
This data is end-to-end encrypted in transit and at rest by Apple. Hanase does not have access to your iCloud account; the sync happens entirely between your devices and Apple's servers.
Purchases
Premium packs are non-consumable in-app purchases through the App Store. Apple handles the transaction and entitlement. Hanase only sees that you own a specific product identifier — never your Apple ID, name, payment method, or billing details. Purchases restore through Apple, not us.
Catalog fetches
When you browse the pack catalog, Hanase makes an HTTPS request to the catalog URL you've configured (the default points to our hosted manifest). When you install a pack, it downloads a JSON file from the URL listed in that manifest. These requests carry only standard HTTP headers — no identifiers, no cookies — and we don't log them in any user-attributable way.
Notifications
Cards are delivered as local notifications scheduled by the iOS, macOS, or watchOS system. They never leave your device. Hanase does not send push notifications through Apple Push Notification service.
Widgets & cross-device snapshots
Widgets read the most recently delivered card from an App Group container on the device
they're running on. When your iPhone and Apple Watch are paired, Hanase uses Apple's
WatchConnectivity framework to mirror the latest card snapshot directly between
them. Nothing routes through a third-party server.
What we don't do
- No analytics SDKs (no Mixpanel, Amplitude, Firebase, PostHog, etc.)
- No crash reporters (we lean on Apple's built-in opt-in crash logs)
- No advertising identifiers
- No third-party fonts loaded at runtime; we bundle our own
- No account, sign-in, or profile
Contact
Questions about this policy: [email protected]