E.D. Norse skull

E.D. — How to use it

Choose a mode, enter your message, then select Encrypt or Decrypt.

New to the app? Start with the example below. You can leave the rotor settings at their defaults.

Before your first message — Licence & Terms

Read the Licence & Terms screen. Accept agrees to the terms and opens E.D.; Exit closes it without accepting. The accepted terms version and date are saved locally.

Open Licence & Terms in the app to read it again. A new terms version prompts again. This does not change your passwords or cipher settings.

1. Try your first message

1. Choose Secure Runes in the Mode menu.

2. Type a long password in Password. Use at least 12 characters.
For this practice only, try: My first rune test 2026!

3. Leave these settings unchanged:
Rotors: I II III
Starting positions: 1 1 1
Ring settings: 1 1 1
Plugboard: leave empty

4. In Message, type: Hello from E.D.!

5. Select Encrypt. Your rune message appears in Result.

6. Select Use as input. This moves the rune message into Message.

7. Select Decrypt. Result should say: Hello from E.D.!

Use your own strong password for real messages. Do not reuse the practice password.

2. Choose the right mode

Secure Runes
Use this for password-protected messages. You need the same password AND settings to decode them.

Rune-124 Puzzle
Use this to explore our three 124-position rotors. It needs matching settings, but no password. It is a puzzle cipher, not modern encryption.

Legacy Enigma
Use this for messages made with the original A–Z Enigma mode. It uses letter settings instead of number settings.

Changing modes restores the default settings. Save your settings before switching.

3. What goes in each field?

Message
Type normal text to encrypt, or enter the entire encrypted message to decrypt.
Rune modes keep uppercase, lowercase, spaces, line breaks and emojis. The limit is 65,536 UTF-8 bytes; emojis may use several bytes each.

Password — Secure Runes only
Enter a unique, long password or passphrase. At least 12 characters are required to encrypt. Spaces and uppercase/lowercase matter.
The app cannot recover a forgotten password. Share it through a separate trusted channel, not alongside the encrypted message.

Rotors
Choose THREE DIFFERENT names from: I, II, III, IV, V.
Use spaces between them. The order is left to right and matters.
Example: V II IV
Do not type: 1 2 3 or I I III

Starting positions — rune modes
Enter THREE numbers, each from 1 to 124, with spaces between them.
Example: 1 62 124
The first number is the left rotor, then the middle, then the right.
Repeated numbers are allowed. Do not use commas or leave a number out.

Ring settings — rune modes
Enter THREE numbers from 1 to 124, using the same format.
Example: 4 8 12
These are separate from starting positions. Both must match the original message's settings.

Plugboard — rune modes
Leave empty for no swaps. Otherwise, enter pairs joined by a hyphen, with spaces between pairs.
Example: 1-124 2-123
Numbers must be from 1 to 124. Each number can appear only once.
Do not type: 1-1 or 1-2 2-3

Legacy Enigma field formats
Rotors: I II III
Starting positions: AAA — exactly three letters A–Z
Ring settings: AAA — exactly three letters A–Z; A means 1, B means 2, through Z meaning 26
Plugboard: AB CD — up to ten pairs; no letter may repeat
Legacy Enigma makes English letters uppercase. Other characters stay unchanged.

4. Decode a message from someone else

1. Ask which mode they used.

2. Enter their ORIGINAL rotor order, starting positions, rings and plugboard.

3. For Secure Runes, enter their exact password too.

4. Paste or type the WHOLE encrypted message into Message, including its header.

5. Select Decrypt.

Each operation resets the rotors. Use the original starting positions; do not try to work out where the rotors ended.

Secure Runes messages begin: EDR1S:
Rune-124 Puzzle messages begin: EDR1P:
Keep these headers. Spaces or line breaks between runes are allowed, but no rune may be changed or omitted.

5. Type runes without copy and paste

1. Choose the mode used by the sender.

2. Open Rune keypad.

3. Select Add header if your message does not already have one.

4. Put the cursor in the visible Message editor inside the keypad, AFTER the header.

5. Select each rune button in the same order as the original message.

6. Close the keypad, restore the password/settings, then select Decrypt.

Rune buttons insert at the cursor. If text is selected, the rune replaces it.
Delete removes selected text or the character before the cursor.
Add header does not replace an existing header. Close keeps your message intact.

You must enter every rune accurately. The keypad cannot reconstruct missing parts of a message.

Keyboard shortcuts for rune entry

Keyboard shortcuts only insert the existing rune characters. They do not change encryption, keys, passwords or message formats. Knowing this public mapping does not provide the secret password.

1. Select the sender's rune mode and restore their password/settings.

2. Put the encrypted message in Message, or start with an empty Message. Select Add header before typing runes. Keep EDR1S: or EDR1P: literal.

3. Turn ON Rune keyboard mode. Click or tap Message and place the cursor AFTER the header.

4. Type the matching QWERTYUI / ASDFGHJK keys one at a time. Shift and Caps Lock give the same runes. A selection entirely in the rune body is replaced; the header is not translated.

KeyRuneKeyRune
QᚠAᚺ
WᚢSᚾ
EᚦDᛁ
RᚨFᛃ
TᚱGᛇ
YᚲHᛈ
UᚷJᛉ
IᚹKᛊ

5. On Android, use your normal phone keyboard or a physical/Bluetooth keyboard. In Rune keypad, select Phone keyboard to show the phone keyboard while keeping Message visible. The rune buttons also show their key labels.

6. Turn OFF Rune keyboard mode before typing normal plaintext. This mode applies only to Message; passwords and settings stay normal. It starts OFF after launch or screen recreation and turns OFF when changing cipher mode. Legacy Enigma does not use these shortcuts.

Pasted rune messages and their complete headers are kept unchanged. On PC, normal clipboard shortcuts still work in Message. On Android, use the text field's standard Paste action. Spaces, line breaks, backspace, delete and cursor movement retain their usual behavior. Unmapped letters are not runes and can cause an invalid-message error.

If your phone keyboard uses swipe typing, word suggestions or unusual composition, type individual letters or use the labelled rune buttons instead. Different phone keyboards may behave differently; check the runes before decrypting.

6. Understand the other buttons

Copy result
Copies a successful result to your device clipboard, ready to paste elsewhere.

Use as input
Moves a successful result into Message. It does not change your settings.

Randomize settings
Changes rotor order, positions, rings and plugboard. It does NOT change your password or message.

There are TWO confirmations:
1. Confirm that you have saved any settings you still need.
2. Review the proposed settings, then approve them.

Cancel either prompt to keep everything unchanged. After approving, save the new settings and run Encrypt or Decrypt again.

Changelog
Shows what changed in each version.

Privacy policy
Explains local processing, saved settings, support emails and deletion.

7. Where are my settings saved?

Android
The app remembers non-password settings after a successful conversion or approved randomization.
Passwords are NOT saved. Re-enter your password after rotating the screen or restarting the app.
An update from the old app may start in Legacy Enigma; choose Secure Runes to use password encryption.

PC / Windows
Settings and passwords last only while the app is open. Restarting restores defaults.
The Windows EXE and Python version work the same way. A new Python download does not update an old EXE; rebuild it with the supplied BAT file.

Keep your password and the original settings somewhere safe before closing, switching modes or randomizing. There is no recovery service.

8. If something goes wrong

Wrong password/settings or altered message
Check the mode, password spelling and all four settings. Check that you copied or typed every rune and kept the header.
Secure Runes deliberately refuses to show plaintext if authentication fails.

Invalid positions or rings
Use three numbers from 1 to 124 with spaces: 1 1 1.
For Legacy Enigma, use three letters instead: AAA.

Invalid plugboard
Check the hyphens and spaces. Do not reuse a number or letter.
To disable swaps, clear the field completely; do not type “none”.

Missing header
Choose the correct rune mode, then use Rune keypad → Add header.
Do not add a rune header to an old Legacy Enigma message.

Encrypting the same text gives different runes
This is expected in Secure Runes. Each encryption uses fresh random data.

Forgotten password or settings
The app cannot recover them. Restore your own saved copy of the original credentials.

9. Important limits

Secure Runes uses AES-256-GCM and Argon2id. The settings also participate in authentication; more rotor positions do not replace a strong password.
Rune pairs are a modern display format inspired by Norse writing, not a historical alphabet of 124 runes.

Puzzle and Legacy modes are for learning. E.D. has not had an independent security audit and cannot protect a compromised device or another app's clipboard handling.

10. What E.D. does

E.D. is an offline text-conversion tool. Secure Runes encrypts text using a password and matching settings; decrypt it later with those original credentials. Rune-124 Puzzle and Legacy Enigma are educational modes for puzzles and gaming clues, not for private information. Rune appearance alone does not provide security.

E.D. is not a chat service, password manager, cloud backup or file-encryption tool. It does not send messages or deliberately keep a message history. Copy result lets you move text into a file or another app. You decide where it goes.

11. Keep a separate credential record

For Secure Runes, save the exact password, mode, rotor order, ORIGINAL starting positions, rings and plugboard. The EDR1S: header identifies the format; it does not recover your password or restore your settings.

Prefer a reputable password manager with protected notes. Use a long random password or a passphrase made from randomly selected words. E.D. requires at least 12 characters for encryption; aim for 16 or more. Do not reuse an email, gaming or banking password.

If you prefer a paper “little black book,” keep it in a locked drawer or safe, separate from devices, USB drives and encrypted-message printouts. Anyone who finds the book can read it. Do not carry it alongside your messages, photograph it into an ordinary cloud album, or show it in screenshots or streams. Keep a protected backup so loss does not lock you out permanently.

Use a neutral reference such as NOTE-001 to match a credential record to its encrypted file. Avoid sensitive details in filenames. Save original settings before switching modes or approving Randomize settings.

Blank record — complete privately:
Reference: NOTE-001
Created: [date]
App version: [version]
Mode: Secure Runes
Password/passphrase: [store privately]
Rotors, left to right: [three names]
Original starting positions: [three numbers]
Ring settings: [three numbers]
Plugboard: [exact pairs, or empty]
Encrypted file location: [location]

Treat the completed record as a secret. Do not place it in the encrypted message, public chat or support email. Do not encrypt your only credential copy with the password it contains.

12. Store notes or logs for yourself

1. Choose Secure Runes. Save your password and matching original settings separately.

2. Enter one note or log entry and select Encrypt. Select Copy result and paste the ENTIRE result, including EDR1S: and every rune, into a plain-text file saved as UTF-8. Example: NOTE-001.txt. E.D. does not save the file for you.

3. Back up the encrypted file in another protected location. Cloud storage is your choice and follows that service's policies. Filenames, dates and file sizes can reveal information even when the contents are encrypted. Keep credentials separate from ciphertext storage.

4. Before relying on the saved copy, reopen it, restore its original credentials and decrypt it. Verify the recovered text matches, including after moving to another device. Screenshots are not a substitute for a complete text backup.

5. Lock your device and close plaintext views when finished. Clear clipboard history where supported. Plaintext may remain in the original editor, screenshots, notifications, backups or other apps; E.D. does not erase those copies.

For a journal, save each encrypted output as a separately labelled entry and record which credentials it uses. Do not combine several encrypted outputs and decrypt them as one message. Split long logs into entries within the 65,536 UTF-8 byte plaintext limit. An encrypted message is not a tamper-proof audit log or proof of authorship.

13. Share messages with someone else

1. Agree on Secure Runes and compatible app versions. Use a dedicated password for that person or sharing purpose, not an account password.

2. Verify the recipient's identity. Exchange the password and exact settings in person or through a separate trusted end-to-end encrypted channel. Do not include them in the same email, chat thread, attachment, shared folder or screenshot as the ciphertext. A second message in the same conversation is not a separate channel.

3. Send the complete encrypted text, including its header, using your chosen service or as a UTF-8 text attachment. That service may retain copies and metadata. E.D. does not send it for you.

4. Use a neutral reference to match credentials to the message. Test with harmless sample text first. The recipient restores the mode, password and original settings, pastes the full ciphertext and selects Decrypt.

Anyone with the ciphertext and complete credentials can decrypt, copy or forward it. Encryption does not prevent an intended recipient from sharing plaintext. A shared password does not prove which person created a message.

14. Change credentials and keep old messages readable

Keep old credential records while you still need their messages. Randomize settings does not update previously saved ciphertext. If credentials are exposed, use new ones for future messages.

To replace an archive, decrypt it with the original credentials, encrypt again with new credentials and verify the new saved copy before removing your old copy. New credentials cannot revoke copies already held by someone with the old credentials.

Use Secure Runes for password-protected notes; Puzzle and Legacy modes are for learning. Norm Null Studio cannot recover lost passwords, settings or missing ciphertext. There has been no independent security audit. A compromised device or unsafe clipboard can expose plaintext.

15. Help and privacy

Norm Null Studio
App support and privacy: support@normnullstudio.com
Business: Norm@normnullstudio.com
Website: https://normnullstudio.com

Do not send passwords, secret keys or sensitive unencrypted messages to support.

Rune font licence
Copyright 2022 The Noto Project Authors (https://github.com/notofonts/runic)

This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is copied below, and is also available with a FAQ at:
https://scripts.sil.org/OFL


-----------------------------------------------------------
SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
-----------------------------------------------------------

PREAMBLE
The goals of the Open Font License (OFL) are to stimulate worldwide
development of collaborative font projects, to support the font creation
efforts of academic and linguistic communities, and to provide a free and
open framework in which fonts may be shared and improved in partnership
with others.

The OFL allows the licensed fonts to be used, studied, modified and
redistributed freely as long as they are not sold by themselves. The
fonts, including any derivative works, can be bundled, embedded, 
redistributed and/or sold with any software provided that any reserved
names are not used by derivative works. The fonts and derivatives,
however, cannot be released under any other type of license. The
requirement for fonts to remain under this license does not apply
to any document created using the fonts or their derivatives.

DEFINITIONS
"Font Software" refers to the set of files released by the Copyright
Holder(s) under this license and clearly marked as such. This may
include source files, build scripts and documentation.

"Reserved Font Name" refers to any names specified as such after the
copyright statement(s).

"Original Version" refers to the collection of Font Software components as
distributed by the Copyright Holder(s).

"Modified Version" refers to any derivative made by adding to, deleting,
or substituting -- in part or in whole -- any of the components of the
Original Version, by changing formats or by porting the Font Software to a
new environment.

"Author" refers to any designer, engineer, programmer, technical
writer or other person who contributed to the Font Software.

PERMISSION & CONDITIONS
Permission is hereby granted, free of charge, to any person obtaining
a copy of the Font Software, to use, study, copy, merge, embed, modify,
redistribute, and sell modified and unmodified copies of the Font
Software, subject to the following conditions:

1) Neither the Font Software nor any of its individual components,
in Original or Modified Versions, may be sold by itself.

2) Original or Modified Versions of the Font Software may be bundled,
redistributed and/or sold with any software, provided that each copy
contains the above copyright notice and this license. These can be
included either as stand-alone text files, human-readable headers or
in the appropriate machine-readable metadata fields within text or
binary files as long as those fields can be easily viewed by the user.

3) No Modified Version of the Font Software may use the Reserved Font
Name(s) unless explicit written permission is granted by the corresponding
Copyright Holder. This restriction only applies to the primary font name as
presented to the users.

4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
Software shall not be used to promote, endorse or advertise any
Modified Version, except to acknowledge the contribution(s) of the
Copyright Holder(s) and the Author(s) or with their explicit written
permission.

5) The Font Software, modified or unmodified, in part or in whole,
must be distributed entirely under this license, and must not be
distributed under any other license. The requirement for fonts to
remain under this license does not apply to any document created
using the Font Software.

TERMINATION
This license becomes null and void if any of the above conditions are
not met.

DISCLAIMER
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
OTHER DEALINGS IN THE FONT SOFTWARE.