Your messages. Your keys.

For supported encrypted messages sent in the Dint+ mobile app, the delivery service receives encrypted content. The devices in the conversation hold the keys needed to read it.

This protection applies to the content of those messages. It does not cover every Dint+ feature or stop someone who receives a message from copying it or choosing to share it elsewhere, including with AI.

You do not need to manage the mathematics. For a supported encrypted message, the journey is simple.

1. On your device
   Your message is turned into encrypted content before it is sent.
2. During delivery
   Dint+ routes the encrypted content to the intended devices.
3. On the receiving devices
   The message is opened using the keys held there.

Sharing text with Your AI is a separate step, explained below.

Each enrolled installation has its own set of encryption keys. Supported encrypted messages are delivered to authorized devices, including your other compatible active devices.

Account access and encryption access are different. A signed-in device still needs to complete encryption setup. Device controls in supported mobile versions let you review enrolled devices and revoke a device’s access to future encrypted delivery.

When you sign in on a new or reinstalled device, follow the app’s encryption setup. Depending on your installation, this can require password verification or approval from an existing device.

Signing in does not automatically restore older encrypted messages. A new device cannot read messages for which it does not have the necessary keys. Reinstalling or losing local encryption data can leave that history unavailable.

A conversation can contain both legacy and end-to-end encrypted messages. Turning on encryption for new messages does not change how older messages were stored. Legacy messages, including the older encryption format, are not covered by Dint+ end-to-end encryption.

Where your app provides message encryption details, check the individual message. An unavailable status is not confirmation of encryption. A conversation’s current status alone does not establish the protection of its entire history.

Supported encrypted groups use encryption designed for group messaging. Messages are encrypted on the sender’s device for authorized group devices. Membership and device changes affect who can receive new encrypted messages.

Not every group or older group message is end-to-end encrypted. Joining a group or adding a device does not by itself provide the keys for earlier encrypted messages.

When sent as supported encrypted attachments, photos, videos, audio and files are encrypted on the sending device before upload. The information needed to open them travels inside the encrypted message.

This applies to attachments sent with that protection. It is not a promise that all Dint+ uploads, public media or legacy attachments are end-to-end encrypted.

Dint+’s current encrypted messaging system does not provide a password-based backup that restores lost message keys and encrypted history. Recovering your account or resetting your password is not the same as recovering those keys.

Keep this distinction in mind before deleting the app or clearing its data. Legacy history and encrypted history have different recovery limits; access to one does not guarantee access to the other.

You decide whether your phone shares messages with Your AI. Selecting an agent alone does not give it access. Where this feature is available, you also explicitly authorize sharing new messages so that agent can assist you.

Where device-assisted Your AI is available for an encrypted direct conversation, your phone opens eligible incoming text and sends a readable copy to the AI service for processing. The agent does not become another device holding your conversation’s encryption keys, and the AI model does not run entirely on your phone.

This feature uses eligible new incoming text after consent, not a backfill of earlier history or attachments. Suggestion mode lets you review and send replies. Automatic replies require a separate confirmation and run while Dint+ is open on the authorized phone.

You can pause assistance or turn it off. Requests already sent may finish processing. Availability depends on your app and the feature’s rollout; when authorized sharing is unavailable, encrypted-chat assistance is unavailable. AI assistance in legacy chats uses server processing and does not make those chats end-to-end encrypted.

Read the AI Terms and Privacy Policy before choosing what to share.

Delivering a message still involves information outside its encrypted content. This includes account and device identifiers, who is in a conversation, group membership, message times, encrypted message and file sizes, and delivery or read acknowledgements.

Message encryption does not extend to your account details, public posts, information you submit to other Dint+ features, or readable content you choose to share with AI. It is not a promise of anonymity.

Dint+ checks authenticated account and device permissions for encryption setup and protected messaging. Sensitive encryption setup can require you to verify your password again.

Use a unique password, keep your device and app up to date, and protect your screen lock. Review enrolled devices in supported app versions and remove devices you no longer use. Never share your password or sign-in codes.