Secure Sharing Guide

Secure Text Sharing Begins Before You Send the Message

Encrypt sensitive information before sharing it, send the encrypted message through one channel, and deliver the password through another. This simple habit greatly reduces the risk of exposing confidential information during everyday communication.

secure text sharing how to share encrypted text encrypted message sharing secure API key sharing split-channel communication
Secure Sharing Guide

Secure Text Sharing

Reduce the risk of exposing sensitive information - Easy to use for personal and business communication - Works with email, chat applications, and collaboration tools

01

Encrypti0n converts sensitive text into encrypted ciphertext before it is shared.

02

AES-256-GCM verifies encrypted messages during decryption, helping detect tampering or corruption.

03

The built-in Password Intelligence tool helps users choose stronger passwords that are more resistant to brute-force attacks.

Built for trust

Designed to keep things secure

Everything is designed to help you complete the task with as little friction as possible.

01

Reduce the risk of exposing sensitive information

Encrypti0n converts sensitive text into encrypted ciphertext before it is shared.

02

Easy to use for personal and business communication

AES-256-GCM verifies encrypted messages during decryption, helping detect tampering or corruption.

03

Works with email, chat applications, and collaboration tools

The built-in Password Intelligence tool helps users choose stronger passwords that are more resistant to brute-force attacks.

Try it out

A secure sharing workflow

Following the same simple routine every time makes secure communication easier and reduces mistakes.

Send

Step 1

Encrypt the message locally before sharing it.

Step 2

Send the encrypted message through email, chat, or another communication platform.

Receive and clean up

Step 3

Deliver the password separately, such as by phone, another messaging app, or in person.

Step 4

After the recipient confirms successful decryption, delete temporary plaintext copies and rotate short-lived credentials if appropriate.

What to expect

Helpful information before you begin

  • Encrypti0n converts sensitive text into encrypted ciphertext before it is shared.
  • AES-256-GCM verifies encrypted messages during decryption, helping detect tampering or corruption.
  • The built-in Password Intelligence tool helps users choose stronger passwords that are more resistant to brute-force attacks.
  • Text encryption is designed for fast workflows, making it practical for sharing passwords, API keys, confidential notes, and other sensitive information.

Good to know

Security and privacy notes

  • Sending both the encrypted message and its password through the same communication channel reduces the security benefits of encryption.
  • Encrypted messages should still follow your organisation's data retention and security policies.
Best next step: Encrypt Text Before Sharing and keep passwords unique, long, and stored safely.

Real-world use cases

Where Secure Text Sharing fits into everyday workflows

Security works best when it supports the task people are already trying to complete.

1

Sharing API keys securely

Encrypt API keys before they enter chat, email, or ticketing systems.

2

Sending passwords to colleagues or clients

Send encrypted text in one channel and the password in another to reduce exposure.

3

Protecting confidential business messages

Encrypt sensitive operational notes before they become permanent chat or email history.

4

Transferring temporary access credentials

Use encrypted handoffs for short-lived credentials, then rotate or delete them when the task is complete.

Learn more

Why use separate communication channels?

Encryption protects the contents of your message, but your security also depends on how you deliver the password. If an attacker gains access to both the encrypted message and its password from the same email, chat, or ticket, the encryption offers little protection. Sending them through different channels creates an additional barrier that is simple to implement and highly effective.

FAQ

Questions people ask before using this

Split-channel communication means sending the encrypted message and its password through different communication channels. If one channel is compromised, the attacker is less likely to obtain everything needed to decrypt the message.

No. Using a unique password for each important message reduces the impact if one password is ever exposed.

Not always. Organisations that manage large numbers of credentials often use dedicated secret management platforms. Encrypti0n works well for secure document sharing, temporary secrets, and everyday encrypted communication.

Only keep encrypted messages for as long as they are needed. Following the principle of least retention reduces unnecessary exposure of sensitive information.

Yes. Encrypting credentials before sharing them significantly reduces the risk of accidental exposure in email, chat platforms, ticketing systems, or shared documents.

Confirm that the recipient successfully decrypted the information, remove temporary plaintext copies when possible, and rotate sensitive credentials if they were intended for temporary use.

Yes. Creating a consistent encrypted sharing process makes secure communication easier to teach, document, and follow across an organisation.