The construction / Explained

One encrypted file.
Two possible messages.

Choose a fake credential for your agent while your software keeps the real key. One encrypted file can open either message, so trusted software can keep the real control file while an agent or shared workspace holds only the decoy.

Try it with test messages ↗Read the security design ↗

Why this matters for an agent product.

Your software can keep the real control file while the agent gets only a decoy or reference. That gives your team a way to keep real credentials out of the conversation, provided the agent cannot reach the real key through another path.

The encryption tools are free. Paid plans add monitored decoys, alerts and activity history. First, use the browser tool with test messages to see both answers for yourself.

HOW ONE FILE HOLDS TWO MESSAGES

Choose which message opens.

You set two passwords and always need both. They stay the same whichever message opens.

STEP 01 / SAME INGREDIENTSStart with the encrypted file

Use the same two passwords together.

STEP 02 / CHOOSE A FILEChoose which answer to open

A separate file, called a control file, selects the message.

STEP 03 / OPEN A MESSAGERead the selected message

The real message, or the harmless alternative you chose.

FIG. / SELECTOR

Conceptual view of browser and SDK encryption. Keep the real control file separate from material you are prepared to reveal.

01 / The selector

Same encrypted file.
Same two passwords.

The passwords do not choose real or decoy (a believable fake secret or message). The two control files are created using the same password pair.

Change the control file, not the passwords.

Use the real control file to read your original message (plaintext). Use the decoy control file to read the alternative you chose.

Both passwords are always required together. Keep access to the real control file separate from the material you are willing to reveal.

Web + SDK / Interactive illustration
ONE CIPHERTEXT / SAME PASSWORD PAIRciphertext + password 1 + password 2
+ the control file you choose
Real messageSelected by the real control file.

Illustration only. The password pair stays the same when switching control files.

02 / For your engineers

The design is open to inspection.

Both passwords create one encryption key. The separate control file determines which message opens. The technical specification below explains how.

02

Encrypt

The readable message is combined with the control file before encryption. This lets the same encrypted file support the real message and your chosen alternative.

Read the formal detail ↗
03

Select

Open the file with both passwords and a control file. Wrong inputs return random-looking output, not an error or your chosen decoy. Check both intended outputs with test data before relying on your setup.

Understand the limits ↗
03 / Two different layers

Your chosen decoy is not a wrong guess.

Choose a decoy to reveal deliberately. Use Honey Mode to make wrong guesses return a fake in a supported format.

01

Your deliberate decoy

Choose the plaintext the decoy control file reveals. This is separate from the behaviour of a wrong password/control combination.

Create a decoy ↗
02

Honey Mode

For supported formats, a wrong password/control combination returns a fake with the right shape instead of garbage. The same wrong inputs give the same fake. This does not itself send alerts.

Explore Honey Mode ↗
04 / Limits and scope

Understand the deployment boundary.

A control file selects the message that opens. Context and external evidence can still distinguish plaintexts, and the construction does not prevent legal compulsion. Review evidence and current status.

Using the Telegram bot or seed-protection wizard?

Only those tools pair each control file with its own password: real password + real control file, or decoy password + decoy control file. This page’s browser and core SDK examples always use the same two passwords together. Keep the instructions for these two workflows separate.

Compare processing boundaries ↗