Privacy · Controls and limits

Privacy you can explain

Every protection needs a scope, a status, and a limit people can understand.

Explore how exposure changes

This is a concept simulator: it helps explain choices and does not calculate a security score.

Scenarios
Exposure levelModerate exposure

This visualization shows how controls change. It does not represent a security score.

End-to-end encryption
Messages are encrypted on your device and can only be read by the recipient.
Active
Secret Chat
Messages designed to reduce persistence after being read.
Active
Local identity
Your identity stays on your device. No cloud profile or phone number required.
Active
Encrypted backup
Backups are encrypted with a key only you control.
Active
Read receipts
You can choose whether others see when you have read their messages.
Off
Typing indicator
You can choose whether others see when you are typing.
Off
Invisible mode
Appear offline while still using the app. (Planned)
Off
Screenshot block
Prevent screenshots of secret conversations. (In research)
Off

What changes

The exposure level is conceptual and reflects how much information you potentially share. SmileChat is designed for you to control every aspect, not to collect data.

Who sees what
  • Recipient: conversation content.
  • Participants: read receipts hidden.
  • Participants: typing indicator hidden.

Responsible reporting: smilechatsocial@gmail.com

Choice starts with understanding

A privacy label is not enough. You need to know what a feature protects, where it acts, and which choice still depends on you.

SmileChat avoids absolute promises: a protected conversation still depends on device condition, participants, and the surrounding environment.

Inside the conversation

End-to-end encrypted private 1:1 chatsConfirmedSecret Chat v2ConfirmedTemporary messagesWeb BetaOne-use linksPlannedLive Typing with presence controlIn developmentEncrypted calls between peoplePlanned

End-to-end encryption is confirmed for private 1:1 chats. Secret Chat adds controls for sensitive moments; temporary messages can be explored locally.

One-use links and encrypted calls are planned. Live Typing remains in development when it involves presence between people.

Identity and recovery

Local identityConfirmedContacts, invites, and checkingConfirmedEncrypted backup and recoveryConfirmed

Local identity, contact checking, and encrypted-backup recovery are confirmed in the product.

Final documentation must explain how the backup is protected, what happens when a device changes, and which signals should be checked outside the application.

When someone has the device

Access PINPlannedBiometric accessPlannedDuress PINVisionDecoy profilesVisionProtected local dataIn developmentLocal clearingWeb Beta

A PIN and biometric access are planned. Protected local data remains in development, while clearing the local view can be tried in the Web Beta.

A duress PIN and decoy profiles belong to Vision. They are not presented as guaranteed defenses against physical access or specialist analysis.

Content, metadata, and limits

Protecting content is not the same as removing all information needed to connect, deliver, or prevent abuse. The final application policy must describe that data precisely.

A screenshot, an unlocked screen, malicious software, or another person’s decision can expose what appears on a device.

Reporting a problem with care

If you find a genuine issue, keep only the evidence needed, do not access other people’s data, and avoid actions that interrupt the service.

Use the official email with [SECURITY] in the subject. The channel promises neither a reward nor a specific response time.

SmileChat newsletter

Follow SmileChat's development

Leave your email to request SmileChat updates when delivery becomes active.

You are in controlYou can withdraw your request at any time from this same block. The controller’s legal identity is pending confirmation.

Withdraw a request