Kairo help guide
Privacy and security
Private by default, not disconnected from reality
Kairo’s core experience works without internet, but it does not claim the app can never use a network. Internet may be used for update checks and optional features you explicitly enable, such as Google Drive backup. Opening a coordinate in Maps or sharing a poster also hands selected data to another app after your action.
Local-first core
Connections, moments, Timeline, Radar, notes, favorites, media links, and Memory Books are stored locally by default.
Rotating presence
Kairo emits short-lived presence identifiers rather than broadcasting your stable profile or name in every Bluetooth packet.
App lock
Require the device credential or biometric before opening Kairo. Android controls whether notification previews remain visible.
Intentional sharing
Data leaves through a feature you choose: backup, poster sharing, opening Maps, diagnostics, or opt-in Around visibility.
Bluetooth identity
Trusted connections exchange private presence material in person. The BLE advertisement contains a compact rotating token under Kairo’s fixed service identifier. A receiver computes expected tokens for its trusted connections and matches locally. Names, notes, memories, coordinates, and photos are not placed in the presence advertisement.
Backup boundaries
Backup archives are encrypted on the device and stored in Google Drive’s private app-data area. Portable history is separated from device trust: the archive can restore memories but cannot impersonate an already trusted phone. The recovery code controls decryption on a new installation.
Control and deletion
- Pause a connection without deleting its Timeline.
- Remove individual media attachments or a Memory Book background.
- Delete individual backup generations or every Kairo Drive backup.
- Disable Around visibility, location tagging, Flare requests, or automatic backup independently.
For exact permissions, data categories, retention, and third-party services, read the Kairo Privacy Policy.