Privacy Policy

Apollo generates a random device identifier when you first open the app. Apollo does not ask for your name, email address, or Apple ID, but shared content and partner relationships are linked to that device identifier so updates can reach the right person.

Goal titles, check-in history, streaks, settings, your partner's name and icon, and related progress data are stored on your device. The compact iCloud snapshot can recover partner connections, current goals, preferences and reflections but excludes detailed history and conversations. You can export a full personal recovery file and choose where to save it.

If notifications are enabled, iOS issues a push token that Apollo registers with its relay server. The token is used only to deliver partner nudges to your device.

Apollo uses a lightweight relay server to connect paired devices. The relay stores which devices belong to a pairing, along with device IDs, pairing codes, nudges, optional messages, optional goal titles, and synced goal lists for synchronization and delivery. Apollo does not access your phone's address book; the stored relationships are the partners you connect with inside Apollo.

Relay data is used to route messages between paired devices. Apollo does not sell, profile, or analyze this data for advertising.

Apollo does not require an account name or email address and does not access location, health or biometric sensors. Apple handles subscription payments. Goal titles and messages are content you choose to enter; avoid including sensitive information you do not want shared with your partner or processed by the relay.

Apollo does not use advertising networks, third-party analytics platforms, or crash reporting SDKs. Private milestone counters stay on your device unless you deliberately share a content-free pilot summary.

Personal records remain on your device until you delete them. Use Backup & data in Apollo to delete local records or the automatic iCloud snapshot. A later backup may recreate the snapshot. Delete recovery files you saved separately using Files. Shared relay data follows the separate retention described above.

Relay events are stored for synchronization and delivery, rather than deleted immediately after receipt. Retention depends on the relay configuration and activity; do not treat it as ephemeral or end-to-end encrypted storage.