Feature
Your relationship graph stays yours.
On your device, with a lock if you want it.
Threat model: on-device default, Apple sync optional.
Optional Face ID / passcode app lock, subscription-gated features where applicable, optional iCloud (CloudKit) sync with Apple’s stack, and exports so you always retain a copy.
Optional app lock and iCloud sync via Apple. Export your data so you always have a copy.
Primary store is local. Optional CloudKit sync uses the user’s Apple ID and container entitlements. App lock wraps UI with biometrics/passcode. Exports (JSON, Markdown, etc.) are user-initiated file writes.
Privacy, lock, and sync — screenshot coming soon
Privacy, lock, and sync — screenshot coming soon
Privacy, lock, and sync — screenshot coming soon
Why it matters Why it matters Data model & behavior
- App lock for sensitive devices
- Local-first storage; optional iCloud (CloudKit) sync across your Apple devices
- JSON and Markdown (and other) exports depending on version
- No ad tracking on this marketing site’s form beyond what you configure
- Face ID / passcode lock
- Local-first; optional CloudKit
- Exports (JSON, Markdown, etc. by version)
- No Calero account server for core data
- CloudKit sync via container entitlements; SwiftData merge
- StoreKit gating for premium surfaces where applicable
How teams use it In practice Implementation notes
Calero is built for people who treat personal and professional relationships as sensitive—not as feed content.
CloudKit uses your Apple ID and Apple’s privacy model—not a separate Calero account database on the public web.
Review the in-app subscription screen for current entitlements (annual from $19.99 USD in the US store; regional pricing applies).
Built for sensitive relationship data, not public feeds.
CloudKit uses Apple’s stack—not a separate Calero login on the web.
Subscription details are shown in the app.
Marketing forms are separate from the app’s data plane.
Review in-app subscription copy for current entitlements.