postea

Postea — Privacy Policy

Effective: May 2026 Last updated: May 2026

TL;DR

Postea has no servers, no accounts, and no analytics. Everything you do in the app stays on your iPhone. The only data that leaves your device is a message that you explicitly choose to send to a friend through the Reach feature, via Apple’s Messages app.

If something here is unclear, email honorius@neogy.dev.

Who is responsible for Postea

Postea is built and maintained by Honorius M. Neogy (neogy.dev) as an independent solo project. There is no company, no co-founder, and no third-party processor.

What data Postea reads on your device

Postea uses these iOS frameworks. Each only runs on your device:

Framework	What it accesses	Why	When
EventKit	Your calendar events (titles, start/end times)	To find genuine gaps between events	When the app is running and you’ve granted Calendar access
CoreMotion	Whether you are stationary, walking, or in transit	To avoid surfacing offerings while you’re moving	Same
CoreLocation	Your approximate location, used to recognize “familiar places” you visit often (home, work)	To weight gap detection by context	Same. Location data is processed on-device and never persisted as a precise coordinate.
Contacts	Names and contact identifiers of people you’ve interacted with recently	To suggest someone for the Reach feature	Same
HealthKit	Writes only — completed Sit sessions are saved as Mindful Minutes	So your meditation time appears alongside other Health data	When you complete a Sit offering
UserDefaults	Your settings (categories, sensitivity, quiet hours, etc.)	To remember your preferences	Always
NSUbiquitousKeyValueStore	Same settings, mirrored to your private iCloud	So your settings sync across your Apple devices	When iCloud is signed in on the device

None of this data is transmitted to me, to any third party, or to any analytics service. It is read on-device, used to make a decision (e.g., “is now a good moment?”), and discarded. The app has no networking code that talks to a backend, because there is no backend.

What data Postea stores on your device

The app stores the following on your iPhone, in its private container:

• A history of which offerings you have seen (so the same one isn’t shown twice in close succession).
• A learned model of when you tend to have idle moments — built from the timing of moments you’ve engaged with.
• A locally-computed list of contacts ranked by recency, used by the Reach feature.

This data:

• Never leaves your device. It is not synced, not backed up to me, not transmitted anywhere.
• Is included in your standard iCloud Backup if you have iCloud Backup enabled, in which case it is encrypted by Apple under your Apple ID and is not accessible to me.
• Is deleted when you delete the app.

What data leaves your device, ever

Two things — both initiated by you:

1. Messages you send via Reach. When you tap “Open Messages” or “Send via Messages,” iOS Messages opens with your composed text. Whatever you choose to send goes through Apple’s Messages, not Postea. Postea cannot read what you send.
2. Settings you have explicitly chosen (categories, quiet hours, etc.) sync to your own iCloud key-value store under your Apple ID. This goes to Apple’s servers, encrypted under Apple’s standard iCloud terms — not to me.

That’s it.

Third parties

Postea has no third-party SDKs, no analytics, no crash reporting services, no advertising, no affiliate links, no trackers. The frameworks listed above are all first-party Apple APIs that run on-device.

Children’s privacy

Postea does not knowingly collect any personal information from anyone, including children. Because the app collects no information at all, children’s privacy is preserved by default. The app is rated 4+.

Account deletion

There are no accounts to delete because there are no accounts. To remove all Postea data from your device, simply delete the app from your iPhone.

To remove the synced settings from iCloud, after deleting the app you can sign into iCloud.com → Account Settings → Apps Using iCloud, and remove Postea’s data. Or simply leave it — it is keyed to your Apple ID and is not accessible to anyone else, including me.

Permissions that Postea requests

When you first run Postea you’ll be asked for the permissions below. Each one is optional. The app remains functional without any of them — it just won’t auto-detect moments, and you’ll need to tap the wordmark to ask for an offering manually.

• Calendar (full access) — to read event start/end times and find gaps
• Motion — to know when you’re stationary
• Notifications — to deliver up to a handful of passive nudges per day, only during waking hours
• Contacts — to suggest someone for the Reach feature
• Location (when in use, optionally always) — to recognize familiar places like home/work
• Health (write only) — to log completed Sit sessions as Mindful Minutes

You can revoke any of these in iOS Settings at any time. Postea will quietly adapt — the features that need that permission will turn off, and everything else will keep working.

Data Apple may receive

Even though Postea does not communicate with my servers, your interaction with the App Store, in-app system permissions, and the iOS Health/iCloud frameworks is governed by Apple’s privacy policy. I have no access to data Apple collects.

Required Reasons API declarations

Per Apple’s privacy manifest requirements, Postea declares its use of the following API:

• NSPrivacyAccessedAPICategoryUserDefaults, reason CA92.1 — to read and write user preferences within the app and the App Group container shared with the Postea widget.

The complete privacy manifest is in Postea/Resources/PrivacyInfo.xcprivacy in this repository.

Changes to this policy

If this policy ever changes, the new version will be posted to this same URL with an updated “Last updated” date. Material changes will be announced in the app’s “What’s New” section on a future release.

Because Postea collects nothing, the realistic scope of any future change is “we now also do not collect X.”

Contact

Privacy questions, takedown requests, or anything that does not fit neatly above:

honorius@neogy.dev neogy.dev

Honorius M. Neogy, sole developer

This site is open source. Improve this page.