Boop

Privacy Policy

Effective

This policy explains how Boop, the Android and iOS messaging and calling app developed by Oriel Haim, handles information. Boop uses Nostr for identity, message delivery, and call setup, and WebRTC for direct calls.

Information Boop handles

Local storage and cryptographic identity

Boop generates a Nostr key pair on your device unless you import an existing identity. There is no registration with the developer and no email address, phone number, or account password required. Your public key is the address you share by text or QR code. Boop uses your private key to sign events and decrypt messages and holds it in the operating system’s secure storage.

Digital SIM lets you export a passphrase-encrypted copy of your private key using NIP-49. Your device creates the backup and you choose where to save or share it. The backup contains the key only. Imported keys are processed on your device. Keep your key and backup passphrase safe. The developer cannot recover them.

Boop uses a local SQLite database for contacts you add by public address, chat and call records, relay settings, language and appearance preferences, and privacy choices such as blocks, approvals, and camera consent. Call history can include participants’ public keys, timestamps, duration, and outcome. Boop’s address book is separate from your device’s system contacts.

Messages and decentralized delivery

Boop sends one-to-one text messages and supported reactions using NIP-17. NIP-44 encrypts the content end to end, and NIP-59 puts it in a gift-wrapped event whose outer signing key is temporary. The recipient decrypts it locally. Boop can also send a separately encrypted copy to your own inbox so your identity can recover retained messages. Your device stores decrypted history in its local database. Recovery depends on what the relays still hold.

Independent Nostr relays carry and may store encrypted messages. The default inbox relays are nos.lol and relay.primal.net, and purplepag.es is a default relay-list discovery service. You can change the configured relays. Boop looks up the recipient’s published inbox list and may send to relays they selected. Public inbox listings associate Nostr addresses with relay URLs. Inbox operators may also learn your public key when you authenticate. Operators can observe connection IP addresses, traffic timing, event sizes, and outer event fields such as recipient keys and timestamps.

Open Later adds a separate time lock before sending the encrypted message. To open it, Boop requests and verifies a public Quicknet beacon from drand using api.drand.sh, api2.drand.sh, api3.drand.sh, or drand.cloudflare.com. These requests can disclose your IP address, request time, and requested public round. They carry no message text, ciphertext, or identity keys.

Chats support text and emoji. The app does not transfer file attachments, photos, or voice notes in messages.

Voice and video calls

Boop sends encrypted invitations and connection setup over Nostr inbox relays. Setup can include network addresses and connection details inside the encrypted signaling. Authenticated participants exchange encrypted audio and optional video directly over WebRTC, including in multiparty calls. Other participants may learn your network addresses. Boop does not record or store call audio or video.

WebRTC uses public STUN servers operated by Google and Cloudflare to discover usable network addresses. These services can see your public IP address, port, and request timing. Boop configures no TURN media relay or centralized conference server. The call may fail when a direct connection is unavailable.

Device permissions

You can manage microphone, camera, and applicable Bluetooth permissions in your device settings. Denying permission disables the related capability.

Third-party services and sharing

Relay, STUN, and drand operators process the network data described above to deliver messages and signaling, establish connections, or serve public beacons. Those operators control their own logs and retention.

Optional chat translation processes visible incoming text on the device with Google ML Kit. Boop stores the translation locally and does not send message text or translations to Google. The SDK can contact Google for model downloads and updates and may send usage and performance metrics. See the Google ML Kit terms and privacy information.

If you choose to share an address, copy a message, or save or share an encrypted key backup, the destination you choose may keep its own copy. This website uses no tracking scripts or analytics cookies. The hosting provider may process request information such as IP addresses and requested pages to serve and protect the site.

Security and encryption

Boop verifies Nostr signatures and authenticates call peers before sending them media. Message encryption protects content in transit and while stored as ciphertext by relays. Communications are readable by their intended recipients, who may keep or share them. A compromised device or private key can expose your data. App Lock limits access through the app interface. It does not encrypt the local chat database.

Retention and deletion

Boop keeps local history and settings for use on the device. Deleting a message in Boop removes its local content and retains a minimal deletion record so relay replay does not restore it. You can clear cached translations separately. Importing a different identity through Digital SIM with confirmation resets identity-owned chats, contacts, calls, and privacy data on that device and retires the previous key from the app. On Android, clearing Boop’s app storage removes its local app data. Save any key backup you intend to keep before removing the local identity.

These actions affect the device only. Independently stored encrypted relay events, public relay listings, recipients’ copies, operating-system backups, and exports may remain. Boop cannot require independent services to remove their copies or guarantee secure erasure of local storage.

Children’s privacy

Boop is a general-purpose communication app. It is not specifically designed for children.

Changes to this policy

When this policy changes, the updated text and effective date will appear at boop.orielhaim.com/privacy.

Contact

Boop is developed by Oriel Haim.