Effective: 2026-05-16 · Developer: Marion Moranetz
Palm Beach Jeff is local-first. What you create or track stays on your device. It does not collect your personal information, sell your data, share it with advertisers, or transmit it to any server I control. Where data leaves your device it is only to deliver a feature you explicitly invoked (iCloud sync, a share sheet, Apple Health). No identifying analytics.Palm Beach Jeff stores its data locally using iOS's standard UserDefaults, on-device files, or (where the app integrates with it) Apple HealthKit. This data:
If the app offers iCloud sync, data syncs to your iCloud account via Apple CloudKit — I cannot see it. If it integrates with Apple Health, Calendar, Photos, or Files via the standard system pickers, each access is authorized by you at the moment you take that action. If it offers Sign in with Apple, only your Apple ID identifier is used — never your name or email unless you choose to share them, and nothing is stored on a server.
Palm Beach Jeff does not use third-party analytics (Mixpanel, Amplitude, Segment), advertising SDKs (AdMob, Facebook Audience Network, Unity Ads), off-device crash reporters (Sentry, Crashlytics, Bugsnag), or tracking SDKs. If this ever changes, this policy and the app's release notes will say so.
Palm Beach Jeff is not directed at children under 13 and does not knowingly collect data from anyone. If you have a concern, contact me at the address below.
For users under GDPR, CCPA, LGPD, or similar: because no personal data is collected on any server I control, there is no controller-side data to access, port, or erase. Local data is governed by Apple's iOS standards and your control of your device.
Updates get a new "Effective" date here and a note in the next App Store release notes.
Privacy questions or concerns: Marion.m.moranetz@gmail.com