Your SMS are sent from your own mobile.See how it works
PLATFORMAPI-first architectureSecure device pairingDelivery visibilityMulti-device controlVersioned documentation

CONFIDENTIAL MODE · END-TO-END ENCRYPTEDNo SIM card required

Private conversations, encrypted before they leave your phone.

Confidential Mode gives trusted contacts a dedicated mobile space for private exchanges. Add a person in seconds with their Public GUID, confidential username or QR code, organize contacts into your own groups, and exchange content that the server stores only in encrypted form until successful delivery.

No card is required for the 7-day trial. Messages are retrieved only while the app is open and the confidential account is authenticated.

No SIM card requiredA private or public Wi-Fi connection is enough. A data-only SIM or eSIM also works.
private.joeReady
Can we speak privately?
K7R9M2X4Q8Trusted contact
Message received
ENCRYPTED CONTENTPUBLIC GUIDEPHEMERAL DELIVERY
01

Encrypted on the sender’s phone

Message content is encrypted locally and can be decrypted only with the recipient device’s private key.

02

Simple trusted contacts

Find a person by Public GUID or username, or scan their QR code without sharing account credentials.

03

Ephemeral server delivery

The encrypted message is removed from the active message table as soon as the recipient device decrypts and accepts it.

PRIVATE BY DESIGN

Private by design—without a SIM card or phone number.

Confidential Mode replaces phone-number identity with a Public GUID and a verified mobile session. The result is a focused exchange where message content stays encrypted from the sender’s device to the recipient’s device.

No SIM card required

Connect through Wi-Fi or mobile data. A data-only SIM or eSIM is optional.

No phone number requested

No active number, SMS plan or phone-number verification is used to identify a confidential contact.

No personal identity requested for contacts

No real name, phone number or address-book access is required to find and add a confidential contact.

End-to-end encrypted messages

Message content is encrypted before transmission and decrypted only on the intended recipient device.

Verified access session

Short-lived authenticated sessions, device binding and protected mobile access are required to open the confidential space.

No readable server history

SMSMobileAPI stores only the encrypted envelope while delivery is pending, then removes it after successful delivery.

Public GUIDQ7M4K9R2
Verified sessionDEVICE KEY
NO SIMNO PHONE NUMBERNO READABLE CONTENT
Content is encrypted on one authorized device and opened only on the intended recipient device.

VIDEO PRESENTATION

See Confidential Mode in action.

Discover how to connect the confidential app, add a trusted contact with a Public GUID or QR code, organize your list and exchange protected messages.

SMSMobileAPIOfficial SMSMobileAPI Confidential Mode presentation

PRIVACY BY DESIGN

Confidentiality is built into every stage of the exchange.

The protected experience begins with authenticated mobile access, continues with encryption on the sender’s device and ends with immediate removal of the encrypted payload after successful delivery.

01

On-device encryption

The clear message is transformed into an authenticated encrypted envelope before it is sent to SMSMobileAPI.

02

Protected mobile access

Biometrics, automatic locking and protected screens reduce exposure when the phone leaves your hands.

03

Minimal message persistence

The server keeps only the encrypted payload needed for delivery and removes it after the recipient device decrypts it.

HOW IT WORKS

From installation to a protected exchange in four simple steps.

No technical configuration is required. Each person installs the official app, authenticates their confidential account and chooses exactly who may appear in their trusted contact list.

  1. 1

    Install the official app

    Download SMSMobileAPI from Google Play or the Apple App Store and keep the phone protected and up to date.

  2. 2

    Connect the confidential account

    Enter the Account ID and Account Licence displayed in the dashboard. These are mobile connection credentials, not API keys.

  3. 3

    Add a trusted contact

    Enter their Public GUID or exact username, or scan the QR code shown in their app. The trusted contact link is created for both people.

  4. 4

    Exchange protected messages

    Open the contact, write your message and send it. Replies carry the encrypted conversation without creating a readable server history.

PUBLIC GUID IDENTITY

A Public GUID makes adding the right contact simple and unambiguous.

Every confidential account receives a unique Public GUID. Share it freely with a trusted person or display its QR code: it identifies your profile without revealing your password, Account Licence or API key.

Public GUID

A unique public identifier used to find the exact confidential profile. It is an identifier, never a password or secret key.

QR code

Display your Public GUID as a QR code and let the other person scan it to create the contact link without typing.

Confidential username

A memorable name helps trusted contacts recognize you after the GUID or QR code has identified the correct account.

IDENTITY WITHOUT A PHONE NUMBER

A phone number is a route—not reliable proof of identity.

Traditional messaging often treats possession of a phone number as identity. Numbers can be reassigned, caller IDs can be spoofed and SIM-swap attacks can transfer control. Confidential Mode does not use a phone number as the account identity, so these number-based impersonation paths do not provide access to the confidential session.

Traditional number-based identity

  • A number can be reassigned to another person
  • Caller ID or sender identity can be spoofed in some channels
  • A SIM-swap attack targets control of the mobile number

Confidential Mode identity

  • Contacts are addressed by Public GUID or verified QR code
  • The account is not identified by a SIM or phone number
  • Access requires the account credentials, registered device key and a valid authenticated session

A Public GUID should still be confirmed through a second trusted channel before a highly sensitive exchange.

CONTACTS AND GROUPS

Organize trusted contacts without complicating private communication.

Create the structure that suits you directly from the mobile app. Contact groups affect only your own organization and never expose message content.

Add in seconds

Search for an exact username or Public GUID, or scan the contact’s QR code. No phone number or API key is required.

A mutual contact link

When a contact is added, both people can see each other in their trusted lists. Removing the relationship removes it for both sides.

Create named groups

Create, rename or delete groups such as Family, Management or Project Alpha from a dedicated configuration screen.

Assign contacts freely

Tap a contact’s username or GUID to place that person in a group, move them or leave them ungrouped.

SECURITY BY DESIGN

Security controls continue beyond message encryption.

Confidential Mode limits where content can appear, how long the server retains it and who can open the protected mobile interface.

01

Strong hybrid encryption

Each message uses AES-256-GCM for its content and RSA-OAEP 3072-bit protection for the recipient’s message key.

02

Private key on the device

The recipient’s private key remains in the protected device keystore and is never uploaded with the message.

03

Biometric access

Biometric unlocking and automatic locking protect the confidential interface when the app is reopened.

04

No background retrieval

Confidential messages are fetched only while the app is open and the user is authenticated.

05

Protected display

Sensitive screens block ordinary screenshots and message text is never placed inside an Android notification.

06

Deletion on delivery

Once the recipient device successfully decrypts the message, its encrypted payload and queue entry are removed immediately.

WHEN YOU CHANGE PHONES

Changing phones does not create a cloud copy of your conversations.

A new installation creates a new device key and authenticated session. SMSMobileAPI does not restore a readable message history to the new phone. Pending envelopes encrypted for the former installation cannot be migrated and are removed when the device key is replaced.

  1. 1

    Former phone

    Its private key remains tied to that installation; SMSMobileAPI cannot export it as a readable conversation archive.

  2. 2

    Secure replacement

    The account explicitly authorizes the new installation and invalidates the other confidential sessions.

  3. 3

    New phone

    A new device key protects future exchanges. Previous messages are not downloaded from an SMSMobileAPI cloud history.

OLD DEVICELocal keyNO CLOUD HISTORY
NEW DEVICEVerified sessionFUTURE MESSAGES
Old encrypted envelopes are not migrated to the replacement key.

SECURITY TRANSPARENCY

End-to-end confidentiality, explained precisely.

The sender’s phone encrypts the content before transmission. The server receives an encrypted envelope, and the recipient’s phone performs the decryption locally. The clear message is never written to the SMSMobileAPI message database.

✓

What protects your content

  • Encryption occurs locally before the message leaves the sender’s phone
  • Only the recipient device holds the private key required for decryption
  • The server stores only an encrypted envelope while delivery is pending
  • The encrypted payload is deleted immediately after successful decryption and delivery
  • Replies re-encrypt the conversation for the next recipient device
!

What remains visible or must be understood

  • The Public GUID and confidential username identify a profile; they are not secrets
  • Technical metadata such as sender, recipient, time and delivery state remains visible to the service
  • Contact relationships, group names and presence information are account metadata, not encrypted message content
  • Contact keys do not yet offer a user-verifiable safety number or cryptographic fingerprint
  • A delivered message cannot be recovered from the server if the app closes before you finish reading it

Important: Before sending highly sensitive information, confirm the contact’s Public GUID or QR code through a second trusted channel. Regulated use still requires your own legal and security assessment.

WHEN TO USE IT

A focused mode for exchanges that should stay outside ordinary business automation.

Executive coordination

Create a narrower mobile space for direct exchanges that should not enter CRM or automation workflows.

Private personal exchange

Communicate with a known person through a dedicated contact identity rather than exposing an API key.

Sensitive operational updates

Keep a small, authorized mobile group apart from standard messaging logs and integrations.

Temporary confidential project

Activate the mode for a defined period, then return the account to its normal operating environment.

CONTACT PRESENCE

Presence information helps you choose the right moment.

The confidential contact list can show a simple recent-activity indicator without turning it into a public social profile.

Available

Green: connected less than 5 minutes ago.

Recently available

Orange: connected between 5 and 30 minutes ago.

Not recently available

Red: last connection was more than 30 minutes ago.

7 DAYS FREE · NO CARD

Try the complete confidential environment for 7 days.

The free trial starts on the first activation of Confidential Mode. No card is requested. Before or after the trial ends, choose the access period directly from the secure dashboard checkout.

CLEAR ANSWERS

Confidential Mode FAQ

Understand the identity, access and security model before you activate it.

How do I add a contact?+

Enter the person’s exact confidential username or Public GUID, or scan the QR code displayed next to their Public GUID in the mobile app.

Is the Public GUID a password?+

No. It is a public identifier designed to find the correct profile. Never share your Account Licence or account credentials as a contact identifier.

Can I organize my contacts?+

Yes. Create, rename and delete your own groups, then tap a contact’s username or GUID to assign or move that person.

When is a message deleted from the server?+

The encrypted payload is deleted as soon as the recipient device downloads and successfully decrypts it. A content-free technical receipt may remain to prevent duplicates.

Can SMSMobileAPI read the message content?+

The message database receives only the encrypted envelope. Decryption uses the recipient device’s private key, which is not uploaded with the message.

Does the 7-day trial require a payment card?+

No. The trial begins on first activation and does not require a card. A paid period is required after the trial expires.

Is Confidential Mode automatically suitable for every regulated activity?+

No. Organizations handling medical, legal, financial, government or other regulated information must perform their own legal, security and compliance assessment.

A NARROWER SPACE. EXPLICIT CONTROL.

Build your trusted contact space and start exchanging protected messages.

Create your confidential identity, share your Public GUID or QR code, organize trusted contacts into groups and begin with a 7-day trial without a payment card.