Can you keep a secret?

Setup and Config

This page includes tools to setup and maintain your own configuration.

On this Page
Use this page to setup your doc, update settings, and view important warnings and config info.
Supported Unicode Character Sets
Add new sets easily with bulk-import.
Character Sets
Character Missing after Decrypt?
Use this tool to add to character map.
Add Character
Important Warnings and Helpful Tips
Performance tips, and important warnings.
View Tips

🔠 Supported Unicode Character Sets
Need to support additional languages? Some languages use accented characters that are uncommon in English. Make sure you include those characters ahead of time to avoid decryption issues.

To encrypt/decrypt text, we need to first transform each character into a number so that we can perform cipher operations on it. The table handles this conversion for us. If a character isn’t available in that table, it will be dropped from your text during encryption.
This table provides sets of characters (called “blocks”) as laid out by the . The Latin Basic blocks have been imported along with the Uppercase & Lowercase block from Latin-1 Supplement. Depending on the languages you wish to support, you may with to add additional blocks.
💡 To import a set, click Add This Block. Please review for important related info
Warning before you update:
Any updates to will likely cause encrypted secrets to decrypt incorrectly. It’s advisable to only use this tool ahead of launch.

Unicode Script
Latin Basic
Latin-1 Supplement
Latin Extended-A

🔍 Missing Characters?
Character missing when you decrypt your Secret?
If you notice that a character in your text is missing when you decrypt your secret, that means it’s missing from the table. When a character cannot be found in this table, it’s simply removed from your text before encryption. You can fix this by adding that character to the system.
If there are existing secrets that are currently encrypted, adding new characters will cause some characters to decrypt incorrectly.
Import new characters
You can add multiple characters if you’d like, just separate them with commas.
👆 Type new characters here

Warning before you update:
Any updates to will likely cause encrypted secrets to decrypt incorrectly. It’s advisable to only use this tool ahead of launch.
There are no rows in this table

🏃‍♂️ Performance Notes
If you notice things have slowed down a bit, this may be helpful advice.
Of course, as more rows are added to the Char Mapping table, the time to Encrypt/Decrypt will increase. I haven’t benchmarked this. You could look at this as a positive thing (the basis of good encryption is that the operation to encrypt/decrypt takes enough time to dissuade brute force attacks), however this could have a negative impact on the user experience of the system.
At the end of the day, I’ll leave that decision up to you :)
Default Character Sets:
The three Unicode Latin Basic character sets:
Punctuation & Symbols
Uppercase & Lowercase
The “new line” character (equivalent of pressing Enter on your keyboard.
A couple strange characters here and there which caused issues in testing - things like “curly quotes” when copying out of Microsoft Office products, and “em/en dashes”.
Finally, I included a set of Uppercase & Lowercase characters from Latin-1 Supplement. (see notes alongside 👉)
I primarily included the Latin-1 Supplement block to help prevent corruption that could happen when users add or remove individual characters or entire character sets to the Character Mapping after items have already been encoded.

During encryption, some characters end up “out of range” because the sum of their index and the corresponding character in the key’s index exceeds the available characters in the table. To map them to a character (in order to generate the ciphertext), we loop back to the beginning of the table. When the Count() of the available characters changes, these out of range characters end up decrypting to the wrong characters and we get corrupted text. This Latin-1 Supplement block therefore serves as a kind of “buffer” to help reduce the likelihood of this happening often when changes are made to the character mapping table.

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
) instead.