Privacy policy
Updated: June 1, 2026
Reckue is a peer-to-peer (P2P) messenger. It is built so that your messages and calls travel directly between devices, and so that as little information as possible leaves your device. This page explains, in plain language, what data the app handles, what stays on your device, and what inevitably goes over the network.
No account. No sign-up, email, phone number, or server-side login/password. Your identity is a cryptographic key created on your device.
No tracking. No analytics, ads, third-party trackers, or behavioral profiling.
We don't collect your data. We have no server storing your messages, contacts, or call audio. Messages and calls are end-to-end between participants.
What stays on your device
Everything important is stored locally, in the app's private storage:
- Your identity key, contacts, message history and settings — in a local database encrypted on the device with a key derived from your passphrase (Argon2 + XChaCha20-Poly1305).
- Drafts and app settings.
This data never leaves the device, except as a message you yourself send to a contact. Uninstalling the app removes it.
What inevitably goes over the network
To deliver messages directly between devices, Reckue uses the Iroh networking stack and the public n0 infrastructure (built by Iroh's developers):
- Node discovery (n0 DNS discovery). So a contact can find your device, its identifier and current connection/relay hints are published to n0's discovery service. This is connection metadata, not message content.
- Fallback relay. When two devices can't connect directly (strict NAT/firewalls), traffic goes through n0's relay servers. That traffic is encrypted — relays only forward bytes and can't see the contents.
- Optional name registry. If you choose to claim a @username, that name and the public identifier it points to are stored on Reckue's name server so others can find you by name. This is opt-in; if you don't claim a name, nothing is sent there. The record contains no message content and no private keys.
We don't sell or share this data with third parties for advertising.
What permissions the app requests
- Microphone (RECORD_AUDIO) — only to capture your voice during a call you start or accept. The audio is sent to your contact and is not recorded or stored by us.
- Internet / network state — to connect to participants and the discovery/relay infrastructure described above.
- Notifications (POST_NOTIFICATIONS) — to show the persistent “staying connected” notification and message alerts.
- Foreground service (FOREGROUND_SERVICE / FOREGROUND_SERVICE_DATA_SYNC) and wake lock — to keep the connection alive while the app is in the background so messages arrive on time.
The Google Play build of Reckue does not request permission to install other apps and contains no built-in update mechanism — updates come only through Google Play.
Children
Reckue is not intended for children under 13, and we deliberately do not collect any information from them.
Changes
If this policy changes, the updated version will be published at this same address with a new update date.
Contact
Privacy questions: hardelele@yahoo.com