Everyday messages. Local history.
Send text, photos and voice messages, then search your encrypted local history. Share small files in one-to-one chats when the recipient supports transfers. Set roles and permissions in Obscure groups.
A secure messenger for text, voice and video. Create an ID without a phone number and keep your history encrypted on your device. Add an optional GSMBox to connect a SIM-based mobile line.

Use the messenger on its own. Add GSMBox when you want to connect a physical mobile line.
Create a boqpod identity without a phone number. Exchange IDs, then message or make a voice or video call over the internet. Your history and private account keys stay with your local account.
Explore the messengerNo SIM or GSMBox required. Both people use boqpod. The service handles delivery and connection metadata.
Leave a SIM in GSMBox, connected to mobile coverage and your router. Link the box to your boqpod ID to receive the line’s incoming calls and SMS in the app over the internet.
Meet GSMBoxGSMBox is optional hardware. The mobile-network part of a call remains an ordinary cellular connection.
Connect by boqpod ID or QR code. Talk one-to-one, share a photo or bring people together in an Obscure group. Your identity is independent of your SIM, and your conversation history stays encrypted on your device.
Send text, photos and voice messages, then search your encrypted local history. Share small files in one-to-one chats when the recipient supports transfers. Set roles and permissions in Obscure groups.
Make one-to-one voice and video calls. Switch cameras, mute your microphone or use speakerphone. Direct connections, a server bridge and TCP-only transport give you options for different networks.
Add contacts by ID or QR code. No phone number, email or address-book upload required. A private 25-word recovery phrase restores your identity; moving your conversation history is a separate step.
boqpod brings messaging, voice and video together around an identity you create yourself. Your conversation history stays in a local encrypted database. You decide who to connect with, how calls travel and when to clear your data.
Create your boqpod identity without a phone number or email. Exchange an ID or scan a QR code to connect.
Messages and private keys belong to your local account. The server delivers encrypted messages instead of maintaining a cloud conversation archive.
Incoming messages and calls use boqpod’s connection service. Google’s Firebase Cloud Messaging is not part of delivery.
Set up a separate Panic PIN for a situation where someone pressures you to unlock boqpod. Entering it on the app lock screen starts a local reset: the app deletes its databases and clears its stored data.
The reset removes this app’s local messages, contacts, settings and saved keys. Copies on other people’s devices, exports and external backups remain. It does not guarantee forensic erasure of flash storage. Your recovery phrase can restore the identity, but not the deleted conversation history.
Bring a family, team or circle of contacts into a group and decide who can join and who can post. Obscure is boqpod’s group protocol: each participant’s app keeps the membership and permissions in sync, and each recipient gets a separately encrypted message.
A founding record defines the group. Signed membership records carry participants’ roles and rights. The apps compare their group state and exchange updates when it differs; the group information travels inside each recipient’s encrypted messages. The delivery service still handles routing information, so Obscure does not make participation anonymous.
Move from a one-to-one conversation to a voice or video call. Switch cameras, use speakerphone or mute your microphone from the call screen.
Call media uses SRTP with AES-256 counter-mode encryption and HMAC-SHA1 authentication. Video quality is configurable and depends on the camera, device and available connection. Bridge mode still uses a server that can see connection metadata. Voice and video calls are one-to-one; group calls are not supported.
Your phone keeps the conversation history in an encrypted database, alongside the account’s private keys. Opening boqpod on another device does not download a cloud copy of your conversations: keeping the history requires a separate transfer.
SQLCipher encrypts the local databases. The server can temporarily hold undelivered encrypted messages in memory until acknowledgement or expiry. Protect your device and any backups or transfers you make. Deleting a local message removes your copy; the recipient’s copy remains on their device.
Your boqpod ID belongs to the identity you create, independently of a SIM card. Create it on the device, even offline, then connect to the service to communicate. No phone number, email or SMS verification code is required.
The phrase encodes your identity key. Anyone who obtains it can recover that identity, so keep it somewhere only you control. Identity recovery is not a message backup. Use the separate device-migration workflow when you need to move an account and its conversation history.
Send text, photos and voice messages in personal conversations and Obscure groups. Send small files in one-to-one chats when the recipient’s app supports them. Search your messages, resume a saved draft and choose notification settings for each chat.
Copy or share text and photos, delete individual messages or clear your local history. Photos are resized and compressed; recorded voice messages use AMR-NB and live calls use Opus. File transfers check integrity with SHA-256 and keep received files in the encrypted message database. Choose Save to export a separate copy. BQF1/BQC1 containers can hold up to 1,047,467 bytes including metadata, so this is not the original file’s size limit. Deletion affects your local copy.
A name helps you recognise a contact; a public-key fingerprint lets you compare the key behind that name. Enable manual verification, compare fingerprints in person or through a trusted channel, then approve the contact’s key.
Manual verification is optional and is not enabled by default. Compare the fingerprint with the person directly or through a channel you already trust. Verifying through the same unverified conversation does not establish an independent check.
Lock access to boqpod with an app PIN and choose when the interface locks again. Android’s secure-window protection blocks ordinary system screenshots and screen recording of the app.
The app requests Android’s secure-window protection. Its behaviour depends on the operating system, and it cannot stop someone photographing the screen with another camera. The app PIN controls access to the interface; it is not a replacement for full-device protection.
An identity independent of your SIM, a history kept on your device and a delivery connection run by boqpod. Here is what those choices mean day to day.
Your messenger identity is not tied to a phone number. Changing a SIM does not define who you are in boqpod.
Your conversations stay with your device. Plan an account migration before changing phones; keep the recovery phrase for restoring the identity itself.
The delivery connection works without FCM or Google Play services. Android must allow background operation for timely incoming communication.
GSMBox connects a physical SIM-based line to the boqpod system. The messenger itself remains usable without buying a box.
GSMBox is an optional bridge for your SIM-based mobile line. Leave the SIM in the box and receive its incoming calls and SMS in boqpod. Keep the box connected to mobile coverage, power and the internet.
See how it connectsKeep a mobile line connected at home or in the office, while you use boqpod elsewhere. The SIM stays in GSMBox at a spot with mobile coverage and a reliable internet connection. Incoming calls and SMS from that line reach your boqpod identity.
The SIM in GSMBox connects to the operator’s cellular network. The box stays where it has mobile coverage and a reliable internet connection.
GSMBox connects the mobile line to the boqpod system. Keep it powered and within mobile coverage; its SIM remains in the box.
The Ethernet model connects to a LAN port on your router. The router supplies internet access; the box uses the power supply specified for its hardware revision.
Use the separate GsmBoxConfig utility over Bluetooth to set the target boqpod ID and network configuration. The display shows mobile signal, network and server-connection status.
App-to-app communication and calls through a mobile operator are different paths. The GSMBox cellular leg is an ordinary mobile-network connection; it does not turn a conventional mobile call into end-to-end encrypted boqpod messaging.
Connect the Ethernet model to your home or office router, power it up and link your boqpod ID. The box stays with the SIM; you use the app wherever you have internet access.
Router LAN port ↔ GSMBox RJ45 port.
Separate power adapter ↔ GSMBox USB-C port. Plug the adapter into a power outlet.
The SIM stays in GSMBox and connects to your mobile operator.
The router provides the internet connection.
Run an Ethernet cable from GSMBox to a LAN port on the router. The box uses this connection to reach the boqpod service.
Install the SIM and use the power supply specified for your hardware revision. Place the box where the mobile signal is reliable.
Use the separate GsmBoxConfig utility over Bluetooth to set the target boqpod ID and LAN settings. The display shows mobile signal, network and server status.
The device owns the conversation. The network gets it to the other person.
Your local account holds the private keys. The client encrypts the message for its recipient and keeps your history in an encrypted local database.
The server routes the encrypted message. If the recipient is unavailable, a bounded temporary queue can hold the encrypted payload until delivery or expiry.
The recipient’s client decrypts the message and stores its own local copy. Obscure group messages follow this path separately for every participant.
Encryption protects message content. The service still handles routing and connection metadata. GSMBox calls include a separate ordinary cellular leg.
Keys on your device. Encrypted messages in transit. Flexible call transport. These are the components that connect the Android app to the people you talk to.
The Android interface connects to native communication libraries through JNI. Messaging, call signalling and media transport run as distinct parts of the system.
A secp256k1 key identifies the account. Message encryption combines RSA-4096 with PKCS#1 v1.5 padding and AES-256-CBC. Call media uses SRTP with AES-256 counter mode and HMAC-SHA1 authentication. Private account keys are held locally; contacts can compare public-key fingerprints.
The C++ msgcomsrv service handles message delivery, call signalling and UDP/TCP relays. Messages are encrypted for their recipients. Undelivered ciphertext can wait in a bounded in-memory queue until acknowledgement or expiry. Calls can use a direct path or a server bridge; bridge-only mode avoids exchanging direct IP addresses with the other caller.
SQLCipher encrypts the local message and account databases. Opus encodes live-call audio; libvpx provides VP9 video. Recorded voice messages use AMR-NB. LibreSSL supports cryptography and TLS. Android 1.3 requires Android 5.0 or newer.
| Library | Version | Role | Licence |
|---|---|---|---|
| LibreSSL | 4.2.1 | Cryptography & TLS | ISC / OpenSSL / SSLeay and bundled notices |
| Opus | 1.6.1 | Audio codec | BSD-style and bundled notices |
| libvpx | 1.17.0 | VP8 / VP9 video | BSD-3-Clause + patent grant |
| SQLCipher Android | 4.11.0 | Encrypted local database | SQLCipher Community BSD-style; see vendor notices |
| AndroidX Core | 1.17.0 | Android compatibility | Apache-2.0 |
| AndroidX AppCompat | 1.7.1 | Application & UI compatibility | Apache-2.0 |
| Material Components | 1.12.0 | Interface components | Apache-2.0 |
| AndroidX SQLite | 2.5.0 | Database interfaces | Apache-2.0 |
| ICU4J | 49.1 | Unicode & internationalisation | ICU license + Unicode data notices |
| ZXing Core | 3.3.3 | QR & barcode processing | Apache-2.0 |
| dm77 BarcodeScanner core + ZXing | 1.9.8 | Camera barcode scanning | Apache-2.0 |
boqpod receives messages and calls over its own connection to your configured server. Delivery works without Firebase Cloud Messaging (FCM) or Google Play services. Allow background operation so Android can keep that connection running.
Android battery-saving modes can suspend background network activity. Allowing background operation helps boqpod keep its server connection available when the screen is off. If Android restricts or stops the app, messages can arrive late and incoming calls can be missed.
The “Boqpod Service” notification indicates that the connection service is running. It is deliberately silent; message and call alerts are handled separately.
When boqpod shows “Allow background run”, choose Enable and approve the Android battery-optimization exemption. You can also find the battery option in boqpod settings. Depending on the phone, Android may call this “Unrestricted” battery use. On Android 13 and later, approve the notification permission. Messages and calls have their own notification channels, separate from the silent “Boqpod Service” connection indicator.
Background operation and alerts are your choice. Restricting the connection can delay messages or cause missed calls; disabling notifications hides alerts. A persistent connection can use additional battery. Setting names vary by Android version and manufacturer.
Android Developers · Doze & App Standby ↗You and your contact each need boqpod. Create your identity first; an internet connection is needed when you exchange messages or make calls.
Choose an account password and create your boqpod ID without a phone number or email, even offline. Save the 25-word recovery phrase somewhere private.
Share your public boqpod ID or QR code, then add your contact’s ID. The recovery phrase is private: it is never what you share to start a chat.
Send a message or start a voice or video call. Allow microphone or camera access when you use those features, and background operation to stay reachable with the screen off.
Changing phones? The 25 words recover your identity. Use account migration to move your conversation history as well.
boqpod 1.3.3 is available for Android 5.0 and newer. Choose ARM64 for Google Pixel, or Universal for other supported architectures. Install over your existing app to keep its data.
Signed Android release · build 110 · ARM64 for Google Pixel and other ARM64 devices. Includes app lock, Panic PIN local reset and screen protection.
Download ARM64 APK470e5ee71bec62a0ceb3fb4d1b5fbda8ac64f0df42ebec2e06be37cc6a65caf3Compute the SHA-256 hash of the downloaded file and compare all 64 characters with the checksum above.
shasum -a 256 boqpod-1.3.3-arm64.apkA matching checksum confirms file integrity, not the security of the application.
boqpod 1.3.3
Architecture: arm64-v8a / armeabi-v7a / x86_64
d23ef30a3cc51ecd4fe1b26ecdb69dd5dd32168a51b941931be1f34b8eea8cabAndroid-side improvements for companion pairing and call recovery. Companion features require a compatible browser client and relay service.
Install over the existing application. Do not uninstall boqpod before updating.
Moving your history to another device? Update boqpod on both devices before starting the transfer.
No. A boqpod identity, internet access and another boqpod user are enough for messaging and app-to-app calls. GSMBox adds a separate connection to a physical mobile line.
The recovery phrase restores the identity, not your deleted conversation database. Account and history migration is a separate workflow. Keep the phrase private and plan a transfer before replacing a device.
No. Panic PIN resets boqpod locally on this device. Other participants’ devices, exported files and external backups are unaffected.
Obscure is boqpod’s group protocol with synchronized membership and permissions. It is not a promise of anonymous participation, a message-expiry timer or remote deletion of everyone’s history.
Android may be suspending the background connection. Allow background operation, check the battery setting and enable notification permission. Phone manufacturers can apply additional power-saving restrictions.
Download boqpod 1.3.3, build 110, for Android 5.0 or newer. ARM64 is suitable for Google Pixel; Universal includes arm64-v8a, armeabi-v7a and x86_64. Each file has its own SHA-256 checksum.
Yes, for app-to-app messages and calls. Exchange boqpod IDs or scan a QR code to connect. A boqpod ID is not a telephone number; GSMBox is the separate link to a physical mobile line.
Small-file sending is available in personal one-to-one chats after the recipient’s app confirms support. Group chats still support text, photos and voice messages. A received file stays in the encrypted message database; use Save when you want a separate exported copy.