DresSecureComms

byChar0n · Communication

Verified safeOpen sourceExclusive

Download APK

—

No reviews reviews

downloads

7.0

android

AI summary

FOSS, de-Googled all-in-one secure communications app for SMS, calls, and contacts with no Google services or trackers. Features AES-256-GCM encrypted messaging, biometric app lock, metadata wipe for photos, URL threat scanning, and geo spoofing. Version 1.8.

Generated by AI. May contain inaccuracies.

About this app

DresSecureComms is a FOSS, de-Googled, all-in-one secure communications app. It works fully offline for SMS and calls, with no Google services and no trackers.

Release builds of this app have triggered false positives. These false positives are driven by the app's legitimate profile: it is a default SMS and dialer app that sends SMS, reads the clipboard for the scanner, and queries location for the Geo Spoofer. The source is public and every sensitive permission is justified in this description and the privacy policy. False-positive reports have been submitted to the flagging vendors. IzzyOnDroid has helped the DresOS team and have said »I must admit my "POC" was neither perfect nor complete, but at least gives very strong indication that those "malware scanner results" cannot be trusted blindly«. Also turns out some security vendors feel unable to proceed with whitelisting unless the application is on the Google play store.

Check here for the email we received whilst trying to whitelist DresSecureComms

Features:

Messages: a private offline SMS client. Send and receive normal texts, or turn on encryption per message. Encrypted messages use AES-256-GCM and only work between two people who both use this app and share the same key (set by hand in Settings). Calls: dial any number or call a saved contact over your normal carrier line. Contacts: an encrypted local vault, stored with the Android Keystore. Add contacts by hand or import them from the device. Threat Scan: check a URL against VirusTotal using your own free API key. Metadata Wipe: strip GPS and EXIF data from a photo before you share it. Geo Spoofer: set a mock GPS location, or have the app pick a random one. App Lock: biometric or device PIN. End Notes:

We need your help to battle Google and its restrictions so if you use any of our projects, services or apps and it works for you then please tell a freind to tell a freind about us and whilst you're at it email these security vendors to tell them to stop relying on Google as it truly hurts peoples work like ours.

open source offline sms privacy security de-googled

What's new

v1.8.2Aug 4, 2026

Fixed
Messages from one particular contact still arriving in the notification and never appearing in the conversation. The 1.8.1 fix treated this as the app needing to match phone numbers itself and stitch several conversations back together, and that was the wrong diagnosis. Android already decides which conversation a message belongs to, in the system messaging database, using its own rules for what counts as the same number. The app was second guessing that with its own matching and then searching for messages across whichever conversations it thought were related, and it also stopped searching after a fixed number of records, so a contact with a long history could fall outside the search entirely while everyone else looked fine. The app now asks Android which conversation a message belongs to and reads that conversation directly, the same way the system messaging app does. No number matching of its own, no stitching, and no limit on how far back it will look. The conversation list is now read from Android's own conversation index rather than assembled by trawling every message on the device. It is faster on a large message history and it can no longer miss a conversation. Incoming messages are no longer stored at all if the app is not currently the default messaging app, which prevents a half stored message that shows in the notification and nowhere else.
Added
A conversation diagnostic. Press and hold a conversation and choose "Why are messages missing" to get a plain text report showing which conversation Android assigned the messages to, which one the app is reading, what the number looks like as actually stored, and the last few incoming messages the app handled. It can be copied and sent to security@dresos.org. If the problem happens again this tells us exactly where the mismatch is instead of leaving us guessing.