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

Set up incoming calls ↗
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.

02.2BOQPOD FOR THE WEBBrowser alpha

Your conversations. More room.

Use boqpod at your desk, directly in your browser. Connect your Android phone to continue its conversations, or create an independent browser profile.

01 / 03

Two ways to use boqpod on the web.

01 / CONNECT YOUR PHONE

Your phone’s conversations, on a larger screen.

Pair with Android by QR code. The browser becomes a companion to your phone, with access to its conversations and contacts. Keep the phone reachable over the local network or internet; it can stay locked.

  • Read history and load older messages from your phone.
  • Send text and photos, share files in personal chats and make personal voice or video calls.
  • Continue existing group conversations with text and photos, according to your group permissions.

Use this mode to continue using your phone’s identity. You do not need to enter a recovery phrase.

02 / INDEPENDENT PROFILE

A browser identity of your own.

Create a new ID without a phone number, email address or paired phone. Choose a temporary session, or save an encrypted profile locally with a password.

  • Personal messaging, photos, supported file transfers and voice or video calls.
  • Add people by boqpod ID or invitation, edit your profile and compare key fingerprints.
  • Keep local history in a saved profile and download an encrypted backup.

Restoring an existing ID with its 25-word phrase switches its primary session from the phone to the browser. The phrase restores identity, not earlier conversation history.

Room for the conversation.

Messages & history

Type on a full keyboard, switch between conversations and find contacts by name or ID. In phone mode, older history loads from Android as you need it.

Photos & files

Preview photos and download attachments. Send small files in personal chats when the other client supports them. Files you download stay on your computer.

Voice & video

Make or receive personal calls, mute the microphone, turn off your camera and keep chatting during the call. The phone handles the call connection in companion mode.

Contacts & groups

Add a contact by ID. Phone mode also brings existing groups to the browser, with text and photo sharing where your group role allows it.

02 / 03

Connect your phone in three steps.

Use the QR connection for your Android account. Update the phone to boqpod 1.3.10 or newer for the direct local connection, and keep both devices online while pairing.

  1. Open the web messenger

    Visit msg.boqpod.ch and choose “Connect phone”. Leave the QR code open on your computer.

    Browser → Connect phone
  2. Scan from boqpod on Android

    Open Web sessions in the Android app, choose Scan QR code and scan the code on your computer.

    Settings → Web sessions → Scan QR code
  3. Check the code. Allow access.

    Check the website address shown on your phone and compare the security code on both screens. Choose “Codes match” in the browser, then “The codes match” and “Allow access” on Android only if they agree.

    Compare on both devices → Confirm → Start

Closing or refreshing the connected tab ends that browser connection; pair again with a new QR code. You can also disconnect in the browser or revoke access under Web sessions on your phone.

03 / 03

Your data, in the right place.

The two modes keep data differently. Choose the one that fits how you want to work.

Your Android phone

Identity keys · main history

Your browser tab

Temporary view · session keys

When your phone is connected

Your main identity keys and history stay on Android. The tab holds session keys and the messages or photos you open in memory; it does not create a permanent browser history database. Downloads you explicitly save are separate files.

With an independent profile

Temporary mode keeps keys and history in the tab’s memory. Saved mode encrypts the local browser database with a password you choose. That password is not sent to the server. Keep an encrypted backup before clearing browser data.

Inside the connection

Direct on your network. Encrypted end to end.

With boqpod 1.3.10 or newer on Android, the browser connects directly to your phone over a WebRTC data channel when both devices can reach each other on the local network. DTLS protects the transport, while the existing Noise session authenticates and encrypts the companion data. The connection uses local addresses without external STUN or TURN servers. If a direct path is unavailable, the encrypted WSS relay keeps the session connected.

Session protection

The companion channel uses Noise_NKpsk0 with X25519, ChaCha20-Poly1305 and SHA-256. Phone identity proofs use RSA-PSS/SHA-256. Comparing the displayed security code is part of approving the connection. Disconnect from the browser or revoke the session on Android to remove its access.

Local profile encryption

Saved independent profiles use AES-256-GCM for the browser’s IndexedDB data. A local password of at least 12 characters derives the encryption key using PBKDF2-SHA-256 with 600,000 iterations. Temporary mode does not save that profile database.

Permissions when you use them.

Microphone & camera

Allow the microphone when making or answering a call. Video also needs the camera. Connecting your phone by QR does not require a webcam on your computer.

Local network

Your browser may ask for access to the local network. Allow it to connect directly to your phone. If access is denied or the network isolates devices, the encrypted relay remains available.

Keep the tab open

The web app does not provide web push or incoming-call alerts after its tab is closed. Browser and system background limits can also interrupt a session.

The web messenger is in alpha. Group calls, built-in voice-note recording and playback, full-text history search and ordinary file sharing in groups are not currently available.

Open a new window for your conversations.

Connect your Android account or start with an independent ID.

Open web messenger
msg.boqpod.ch

Swipe or scroll to inspect the screen at full size.

The actual boqpod browser workspace displayed on a laptop

An independent profile with conversation search, contact controls and temporary-session settings.

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
WebRTC Android150.7871.04Encrypted local data channel between Android and the web messengerBSD-3-Clause and bundled third-party notices
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.6 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.6. 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

Incoming calls. Even when your phone is locked.

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.

Three settings help boqpod stay connected, alert you and show the call on your lock screen. Set them once on your Android phone.

  1. Allow call notifications

    On Android 13 or later, allow notifications when prompted. Then check the app’s notification settings and enable the “Boqpod Calls” category, including pop-up display where available. Call sound follows your phone’s ringtone volume and sound mode.

    In Android settings

    Settings → Apps → boqpod → Notifications → Boqpod Calls

    Allow notifications on the lock screen too. On Pixel, look under Settings → Notifications → Notifications on lock screen. The separate “Boqpod Service” indicator is deliberately silent; it is not the call alert.

  2. Allow the incoming call screen

    On Android 14 or later, boqpod has a shortcut to Android’s full-screen permission. Open this row in the app:

    In boqpod

    Settings → Messages & Calls → Calls → Incoming call screen

    Tap the row, enable full-screen notifications for boqpod in the Android screen that opens, then return to the app. The row should show “Allowed”.

    You can also find it under Android Settings → Apps → Special app access → Full-screen notifications. Android versions before 14 do not have this separate permission switch.

  3. Keep the connection running

    boqpod does not use Google push. It keeps its own connection for incoming messages and calls, so Android must allow it to run in the background.

    In Android settings

    Settings → Apps → boqpod → App battery usage → Allow background usage

    Allow background usage and choose “Unrestricted” if offered. Alternatively, in boqpod open Settings → Set unrestricted battery usage, if shown, and approve the Android battery-optimization exemption for this app.

    Restricting or stopping boqpod can delay messages or cause missed calls. Keeping the connection available may use more battery.

What appears when someone calls?

Phone locked · full-screen allowed

Android can show the incoming call above the lock screen with answer and decline controls. This does not unlock your phone or remove its PIN protection.

Phone unlocked

Android normally shows a call banner with controls, so you can keep using your current app.

Full-screen access off

The call uses a notification with answer and decline controls instead. Make sure call alerts and lock-screen notifications are visible.

The call still does not appear?
  • Check that “Boqpod Calls” and lock-screen notifications are enabled. For an audible ring, check ringtone volume, silent mode and Do Not Disturb or other active modes. Adjust the mode’s allowed apps if you want boqpod to ring.

  • Check your internet connection and background battery setting. Open boqpod again if you force-stopped it. On Android 14 or later, return to “Incoming call screen” and check that it says “Allowed”.

Menu names vary by Android version, system language and phone manufacturer. Notification visibility, full-screen access and background battery use are separate settings.

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

Set up incoming calls ↗
boqpod / AndroidANDROID 1.3.10 · RELEASED
boqpod 1.3.10
build 117 / 20.2 MiB · 21211164 bytes / Android 5.0+ / 2026-11-19
Architecture: arm64-v8a

Signed Android release · build 117 · ARM64 for Google Pixel and other ARM64 devices. Adds encrypted WebRTC LAN connections for the web messenger.

Download ARM64 APK
SHA-256
e72e109dfb88a40f59743340b6094987c8468f5d8709ade7151db8b36bfafd76
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.10-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.10

build 117 / 41.8 MiB · 43821712 bytes

Architecture: arm64-v8a / armeabi-v7a / x86_64

SHA-2563d9bfd9cd58ebf182783c9a8b76682633193dae1a3ad73f064d4a1ca90b64024
RELEASE NOTES

What’s new in 1.3.10

A direct, encrypted connection between Android and your browser, with automatic relay fallback.

What changed

  • Connects the web messenger directly to Android over a WebRTC data channel on the local network.
  • Protects the local transport with DTLS and retains Noise encryption, device authentication and QR approval.
  • Keeps the encrypted WSS relay available when a direct connection cannot be established.
  • Uses the new transport for companion messages, file transfers and personal voice or video calls.

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.6, build 113, 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.