boqpod
Get the app
PRIVATE MESSAGING. YOUR OWN ID.

Stay close.
Keep control.

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.

01 / MESSENGER02 / GSMBOXYOUR ID. YOUR CONNECTION.
ANDROID 1.3 / GOOGLE PIXELANDROID
Google Pixel 9 displaying the real boqpod Android application
boqpod Android 1.3 · Google Pixel 9
NO PHONE NUMBER REQUIRED✳MESSAGES · VOICE · VIDEO✳LOCAL ENCRYPTED HISTORY✳
01THE BOQPOD CONCEPT

One identity.
Two ways to connect.

Use the messenger on its own. Add GSMBox when you want to connect a physical mobile line.

People, connected by an ID.

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 messenger
  1. Your deviceIdentity · keys · history
  2. Encrypted deliveryboqpod service
  3. Their deviceIdentity · keys · history

No SIM or GSMBox required. Both people use boqpod. The service handles delivery and connection metadata.

02MESSAGING, VOICE & VIDEO

One identity. Every conversation.

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.

01

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.

02

Hear the voice. See the person.

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.

03

Your identity starts with you.

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.

03PRIVATE BY CHOICE

More control. In every conversation.

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.

An ID, not a phone number

Create your boqpod identity without a phone number or email. Exchange an ID or scan a QR code to connect.

History on your device

Messages and private keys belong to your local account. The server delivers encrypted messages instead of maintaining a cloud conversation archive.

Your own connection

Incoming messages and calls use boqpod’s connection service. Google’s Firebase Cloud Messaging is not part of delivery.

PANIC PIN01

A different PIN. A local reset.

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.

  • Set up the normal screen-lock PIN and a different Panic PIN in advance.
  • Local messages, account settings and saved keys are cleared from the app.
  • In Security, enter your account password to configure the Panic PIN. Choose a different code from your normal unlock PIN.
What is cleared?

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.

OBSCURE CHATS02

A group with explicit rules.

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.

  • Owner, moderator, writer and reader roles.
  • Invitations and acceptance, with control over who can post.
  • Group name, description and avatar shared with participants.
How group state stays in sync

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.

VOICE & VIDEO03

Hear the voice. See the person.

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.

  • Direct connections or a server bridge, depending on the network.
  • Bridge-only mode avoids exchanging direct IP addresses with the other caller.
  • TCP-only mode for networks that restrict UDP.
Media transport and quality

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.

LOCAL HISTORY04

Your conversations live with you.

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.

  • Encrypted message transport between clients.
  • Temporary delivery queue for messages that have not reached the recipient.
  • Device migration is separate from identity recovery.
Storage, delivery and backups

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 IDENTITY05

Start without handing over a number.

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.

  • No phone number or email required to create an account.
  • Share your boqpod ID or a QR code with a contact.
  • A 25-word recovery phrase lets you recover the same identity.
Keep the recovery phrase private

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.

EVERYDAY MESSAGING06

More than a text bubble.

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.

  • Photos from the camera or gallery, including multiple images.
  • Record and play voice messages inside a conversation.
  • Per-chat notification and vibration settings.
  • Send small files in one-to-one chats when the recipient’s app has confirmed support for file transfers.
Working with your messages

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.

CONTACT VERIFICATION07

Know the key behind the name.

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.

  • Inspect the contact’s public-key fingerprint.
  • Approve a key manually when verification is enabled.
  • Add contacts directly, without uploading an address book.
A deliberate verification step

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.

ON-DEVICE CONTROL08

Choose when your chats unlock.

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.

  • Lock when the screen turns off or after a configured interval.
  • Keep the normal unlock PIN separate from the Panic PIN.
  • Combine app controls with a strong device lock.
What screen protection does

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.

03.1Why boqpod

Choose the architecture that fits you.

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.

Independent of a SIM

Your messenger identity is not tied to a phone number. Changing a SIM does not define who you are in boqpod.

Local history, deliberate recovery

Your conversations stay with your device. Plan an account migration before changing phones; keep the recovery phrase for restoring the identity itself.

No Google push dependency

The delivery connection works without FCM or Google Play services. Android must allow background operation for timely incoming communication.

A bridge to your mobile line

GSMBox connects a physical SIM-based line to the boqpod system. The messenger itself remains usable without buying a box.

04GSMBOX

Your mobile line.
Now in boqpod.

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 connects
GSMBOXYOUR MOBILE LINE, CONNECTED
GSMBox01 / 07
Perspective view of GSMBox

GSMBox beside Pixel 9.

Approximate size comparison of GSMBox and Google Pixel 9
Approximate size comparisonGoogle Pixel 9 ↗152.8 × 72 × 8.5 mm

GSMBox · 360°

04.1Your mobile line, connected

Your SIM has a home. You have the app.

Keep 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.

  1. 01

    Mobile network → SIM

    The SIM in GSMBox connects to the operator’s cellular network. The box stays where it has mobile coverage and a reliable internet connection.

  2. 02

    The box bridges the line

    GSMBox connects the mobile line to the boqpod system. Keep it powered and within mobile coverage; its SIM remains in the box.

  3. 03

    Router → internet

    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.

  4. 04

    Your identity → your phone

    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.

04.2MAKE THE CONNECTION

SIM. Router. Your boqpod ID.

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.

GSMBox connected to a router by Ethernet and to a separate power adapter by USB-C
  1. 01

    Ethernet

    Router LAN port ↔ GSMBox RJ45 port.

  2. 02

    USB-C power

    Separate power adapter ↔ GSMBox USB-C port. Plug the adapter into a power outlet.

  3. 03

    SIM slot

    The SIM stays in GSMBox and connects to your mobile operator.

  4. 04

    Router WAN / Internet

    The router provides the internet connection.

01

Connect to your router.

Run an Ethernet cable from GSMBox to a LAN port on the router. The box uses this connection to reach the boqpod service.

02

Insert the SIM. Add power.

Install the SIM and use the power supply specified for your hardware revision. Place the box where the mobile signal is reliable.

03

Link your boqpod ID.

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.

05How it works

What happens when you press send?

The device owns the conversation. The network gets it to the other person.

  1. 01

    Encrypt on your device

    Your local account holds the private keys. The client encrypts the message for its recipient and keeps your history in an encrypted local database.

  2. 02

    Deliver through the service

    The server routes the encrypted message. If the recipient is unavailable, a bounded temporary queue can hold the encrypted payload until delivery or expiry.

  3. 03

    Open on their device

    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.

05.1PRODUCT ARCHITECTURE

Encryption. Storage. Delivery.

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.

SYSTEM OVERVIEW
01Android applicationJava / JNI
↓ ↑
02Native communication layerC / C++
↓ ↑
03Messaging & media transportmsgcomsrv

The Android interface connects to native communication libraries through JNI. Messaging, call signalling and media transport run as distinct parts of the system.

Keys & encryption

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.

Delivery & call transport

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.

Local storage & media codecs

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.

The libraries behind boqpod.

ANDROID · COMPONENTS & LICENCES
LibraryVersionRoleLicence
LibreSSL4.2.1Cryptography & TLSISC / OpenSSL / SSLeay and bundled notices
Opus1.6.1Audio codecBSD-style and bundled notices
libvpx1.17.0VP8 / VP9 videoBSD-3-Clause + patent grant
SQLCipher Android4.11.0Encrypted local databaseSQLCipher Community BSD-style; see vendor notices
AndroidX Core1.17.0Android compatibilityApache-2.0
AndroidX AppCompat1.7.1Application & UI compatibilityApache-2.0
Material Components1.12.0Interface componentsApache-2.0
AndroidX SQLite2.5.0Database interfacesApache-2.0
ICU4J49.1Unicode & internationalisationICU license + Unicode data notices
ZXing Core3.3.3QR & barcode processingApache-2.0
dm77 BarcodeScanner core + ZXing1.9.8Camera barcode scanningApache-2.0
05.2Permissions

Permissions, explained.

boqpod does not require Contacts or SMS permissions. Other Android permissions support specific functions, from recording a voice message to keeping incoming calls reachable.

Permission or accessWhat it is used forWhat to expect
Contacts & SMSNeither permission is requested.Add people by boqpod ID or QR code. No SMS account verification.
MicrophoneVoice messages and voice or video calls.Requested when you use audio features.
CameraVideo calls, QR scanning and taking photos.Requested when you use a camera feature.
Photos, files & storageChoose photos or a file to send, or export a received file with Save.Received files are stored in the encrypted database. Saving creates an additional exported copy. Android’s access prompts depend on the version.
Notifications & background operationKeep the server connection available for incoming messages and call invitations, with a visible service notification.Allow notifications and background operation separately. The microphone and camera serve audio/video features, not the idle messaging connection.
Location & BluetoothAndroid 1.3.3 requests neither permission.GSMBox configuration uses the separate GsmBoxConfig utility, which has its own permissions.
Other Android integrationNetwork access, phone state, account and sync integration, call services and display-over-other-apps access.These system permissions support Android integration; they do not grant access to your Contacts or SMS.

These permissions describe Android 1.3.3. You can decline microphone, camera or media access and leave the corresponding feature unused. Background and notification settings are separate controls.

05.3DELIVERY WITHOUT GOOGLE PUSH

Stay reachable with the screen off.

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.

01

Keep your connection open

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.

02

A quiet connection indicator

The “Boqpod Service” notification indicates that the connection service is running. It is deliberately silent; message and call alerts are handled separately.

03

Enable background delivery

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 ↗
START WITH YOUR OWN ID

Three steps to your first conversation.

You and your contact each need boqpod. Create your identity first; an internet connection is needed when you exchange messages or make calls.

  1. 01

    Create your identity

    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.

  2. 02

    Exchange IDs

    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.

  3. 03

    Start the conversation

    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.

06ANDROID DOWNLOAD

Your next
conversation.

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.

boqpod / AndroidANDROID 1.3.3 · RELEASED
boqpod 1.3.3
build 110 / 14.3 MiB · 15005431 bytes / Android 5.0+ / 2026-11-18
Architecture: arm64-v8a

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 APK
SHA-256
470e5ee71bec62a0ceb3fb4d1b5fbda8ac64f0df42ebec2e06be37cc6a65caf3
How to verify the download

Compute 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.apk

A matching checksum confirms file integrity, not the security of the application.

Install over the existing application. Do not uninstall boqpod before updating.

boqpod 1.3.3

build 110 / 25.3 MiB · 26486968 bytes

Architecture: arm64-v8a / armeabi-v7a / x86_64

SHA-256d23ef30a3cc51ecd4fe1b26ecdb69dd5dd32168a51b941931be1f34b8eea8cab
RELEASE NOTES

What’s new in 1.3.3

Android-side improvements for companion pairing and call recovery. Companion features require a compatible browser client and relay service.

What changed

  • Clearer pairing guidance: open the client in your own browser, check its site address and compare the security codes. The approval screen rejects gestures when another window obscures it and resets the code-comparison step.
  • Initial pairing uses a secure WebSocket (WSS) relay. A local-network connection is preferred only after the session has been approved and the new connection authenticated and confirmed.
  • When switching companion media to the local network, the existing connection stays active until the new link is authenticated and acknowledged. Failed or expired connection attempts leave relay fallback available.
  • After a companion connection drops, the same authorized call can recover within 10 seconds while preserving microphone mute and paused video. Recovery is unavailable after the call ends, access is revoked or the recovery window expires.
  • Delayed data and cleanup from an older media connection no longer interfere with a recovered call.
  • Failed or replayed pairing attempts stop the companion foreground service when no live session remains.

Keep your account and history

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.

Questions

The details that matter.

Do I need a GSMBox to use the messenger?

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.

Can I recover my messages with the 25 words?

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.

Does Panic PIN erase the other person’s copy?

No. Panic PIN resets boqpod locally on this device. Other participants’ devices, exported files and external backups are unaffected.

Are Obscure chats disappearing or anonymous chats?

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.

Why might messages arrive only when I open the app?

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.

Which Android version can I download?

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.

Does my contact need boqpod too?

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.

Why can’t I send a file in every chat?

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.