Why use the CodeBooks Application?

Keeping Things Secure!

Why CodeBooks Still Matter (and Why We Built a Better One)

For as long as humans have been communicating, we’ve also been trying to hide what we’re communicating. Every era has had its own flavor of secrecy:

  • The old school: one-time pads, classic CodeBooks, shift ciphers, offsets, clever pen-and-paper tricks

  • The new school: XOR-based systems, public/private key cryptography, and every modern crypto library under the sun

  • And of course, today’s world of “encrypted” apps like Signal (we approve!), Session, Wickr, Viber, and… well… WhatsApp (please don’t use WhatsApp)

But here’s the catch:

📌 Most instant-messaging encryption depends on software someone else controls.

And “secure” doesn’t always mean actually secure.
History has shown — repeatedly — that backdoors, metadata leaks, flawed implementations, and corporate ownership can and do compromise “secure” messaging platforms. Especially WhatsApp.

Why We Returned to CodeBooks

After decades of watching encryption trends rise, fall, and sometimes explode spectacularly, one method has consistently stood strong:

The CodeBook.

It’s simple.
It’s elegant.
And, most importantly: if your CodeBook isn’t compromised, your communications aren’t compromised.

The only real historical failure point has been the human element — someone on the inside handing over the CodeBook.

So we asked ourselves:

What would a modern, secure, flexible, tamper-resistant CodeBook system look like today?

And then we built it.

Introducing The CodeBook System — Powered by SCSC

At Secure Computer Solutions Company (SCSC), we created a modern twist on the classic CodeBook concept.
Our system brings CodeBooks into the modern era with:

  • Unlimited CodeBooks for unlimited teams

  • Total privacy (your CodeBooks are invisible to other users)

  • Strict separation between Manager Licenses and Client/User Licenses

  • Cross-platform support: Linux, macOS, Windows, Android, and soon iOS

  • Zero cloud processing — everything happens on your device

✔ Manager License

Create CodeBooks, export them, manage teams, control access.

✔ Client/User License

Encrypt, decrypt, send, receive — all without ever touching a centralized server.

How It Works (The Fun Part)

Once your team shares a CodeBook:

  1. A user opens the CodeBook application
    (Manager or Client/User License — both work for messaging.)

  2. They write a message inside the built-in editor.

  3. They choose which CodeBook to encrypt with.

  4. CodeBook System performs:

    • First layer: CodeBook-based encryption

    • Second layer: SCSC’s proprietary encryption pass

    • Output is saved as:
      YYYYMMDDHHMM.emsg

  5. The recipient reverses the process (entirely on their own device) and reads the clear text.

💡 No servers.

No cloud storage.
No metadata scraping.
No middlemen.
No “trust us, it’s encrypted” nonsense.

Just strong, local, verifiable encryption.

Why This Matters

Because with a double layer of encryption, split across two independent cryptographic systems, offline by design, and with no central service to attack, the ability for outside parties to decrypt your messages becomes — practically speaking — non-existent.

Bad actors can’t attack what they can’t access.