This is cryptographic c-mail, like the Save System Slot 2.

The server cannot see the contents. It also does not accept graphics — text only, no images, no HTML, no attachments.

You get a crypto armor block and you set a PIN number, and the system treats it just like a save game. Lose the block + the PIN, lose the message. Same contract, same crypto, same rule: we have no way to recover it for you.

How C-Mail Works

C-mail is not a mailbox on a server. It is a save file where the “save” happens to be a message. You write it, you lock it with a PIN in this browser, and what leaves this tab is ciphertext. The recipient unlocks it with the same PIN.

01

Write — text only

You write: to, subject, body.
Plain text only. No graphics to smuggle in a tracker.
Server sees: nothing yet.

02

Set a PIN + Get a Block

You set: a PIN number.
You get: a crypto armor block.
Server holds: ciphertext only, if it holds anything at all.

03

Send the Block

You send: the block, anywhere.
Recipient needs: block + PIN.
Price: lose either one, lose the message.

The PIN never leaves your browser. It is never sent to the server, never stored, never hashed on the server. It exists only to derive the key that locks the block. The block is self-contained: salt + IV + ciphertext, wrapped in armor headers so you can copy-paste it into any chat, forum, or note without it breaking.

-----BEGIN ENCRYPTED C-MAIL----- U7d9aK2pQmXv8Z1sL4nB6cR9tY3wE5hJkM... ... 64 chars per line, base64 only ... -----END ENCRYPTED C-MAIL-----

That block is the message. Hand it to someone directly and the server is never involved — that is Slot 1, offline. Let the server hold the ciphertext for pickup and that is Slot 2, online encrypted. Either way the server cannot read it, because the server never had the PIN.

What The Server Sees

Same exposure model as The Retro Save System, Slot 2. If you hand-deliver the block, the server sees nothing at all. If you let the server hold it for pickup, it sees metadata — never contents.

What the server sees Hand-delivered block Server-held (Slot 2)
Message contents (to / subject / body)——
Your PIN——
Graphics / images / HTML— rejected— rejected
Mailbox / pickup ID—✓
Message timing—✓
Request IP / User-Agent—✓
Ciphertext size—✓
Pickup frequency—✓

The server knows the IP of the request — that is standard server logging, documented in the privacy policy. It never stores that IP alongside the message. There is no column joining a message to an IP, or a PIN to a message, or an email address to either. They are separate systems with no shared key. The rate limiter sees IP; c-mail does not.

No Graphics. On Purpose.

C-mail does not accept graphics. Not as a limitation to work around later — as the design.

  • No images. No JPG, PNG, GIF, WebP, SVG, or base64 data:image blobs.
  • No HTML. No <img>, <a>, <iframe>, no rich text, no fonts, no styles.
  • No attachments. No PDFs, no files, no “see attached.” If it is not plain UTF-8 text, it is not c-mail.
  • No tracking pixels. The classic email trick — a 1×1 invisible image that phones home when you open it — cannot exist here because there is nowhere to put it.

Graphics are how email became surveillance and spam delivery. A picture can hide a tracker, a link, a fingerprint, a payload. Text cannot. A 4 KB text message is also cheap to store, cheap to encrypt, and impossible to turn into a live HTML page. The server enforces this the same way it enforces JSON validity on plaintext saves: if the payload is not plain text, the write is rejected.

If you need to send a picture, send a save game. C-mail is for words.

Treated Just Like A Save Game

This is not a metaphor. The implementation is the save system.

  • A message is a save. The “state” being saved is { to, subject, body } instead of { level, hp, inventory }. Same JSON, same bucket model, same caps.
  • A PIN is a code. In saves, you hold a 16-char code. In c-mail, you hold a PIN number. Same role: without it, the block is opaque bytes.
  • A block is a block. Same armor format, same PBKDF2 + AES-GCM layer, same salt + IV + ciphertext packing. Save blocks start with -----BEGIN ENCRYPTED SAVE-----. C-mail blocks start with -----BEGIN ENCRYPTED C-MAIL-----. That header is the only difference.
  • Same lookup. If the server holds it, the lookup key is sha256(slug + ':' + pickup-id), just like saves. Same slug prefix rule: same pickup-id on two different mailboxes produces two different messages — never a collision.
  • Same caps. 4 KB per bucket, 50 KB total. A c-mail message is one bucket. Keep it short. That is the point.
  • Same contract. Lose what you hold, lose the message. No password reset, no “forgot PIN” flow, no support ticket that can recover it — because there is nothing to recover it from.

The wrapper

// Same API as RetroSave — the payload is a message. const { block } = await CMail.create({ pin: '4829' }); await CMail.send(block, { to: 'handle', subject: 'hi', body: 'meet at 8?' }); // Recipient side: const msg = await CMail.open(block, '4829'); // { to: 'handle', subject: 'hi', body: 'meet at 8?' }

Encryption happens in the browser first. In server-held mode, each message is encrypted in the browser; the server sees only ciphertext and a pickup id. In hand-delivered mode, no request is made at all.

Try It — C-Mail, Slot 2

The demo below is the real crypto: PBKDF2 key derivation from your PIN, AES-GCM encryption, and a self-contained armor block. Pick a PIN, write a message, click Encrypt. Nothing is sent to any server. Everything happens in this tab.

Try to paste an image tag or a data:image blob into the body — the demo will reject it, just like the server does.

Not for real secrets. A PIN is a short key. Brute force is not the threat if you pick a random PIN and do not reuse it. The threat is someone who finds the block + PIN left in the open. Treat them like a physical key: safe to hand directly to the person you mean, not safe to paste into a public chat. Use a fresh PIN per message.

Write + lock a c-mail

Open a c-mail

What The Server Enforces — and What It Doesn't

The server is not a mail server. It stores bytes and enforces invariants that hold for every message. It never interprets your c-mail.

The server enforces

  • Bound parameters. Every query uses PDO prepared statements. Your payload cannot become SQL.
  • JSON content type + nosniff. Responses are always application/json; charset=utf-8 with X-Content-Type-Options: nosniff. The browser treats the body as JSON data, never as executable HTML.
  • Plain-text only. A c-mail payload must be plain UTF-8 text. HTML tags, image tags, data:image, base64 blobs, and attachments are rejected. This is structural, not cosmetic: plain text cannot also be a valid HTML document or a tracking pixel.
  • Byte caps. 4 KB per message, 50 KB total per pickup. No gigabyte payloads.
  • Rate limiting. In nginx, keyed on the TCP peer, not in PHP and not stored with the message.
  • Isolation. No IP is read in PHP. C-mail has no IP column. Messages and rate-limits share no key.

The server does not

  • Read your message. The payload is ciphertext the server cannot decrypt.
  • Know your PIN. The PIN never leaves the browser. There is nothing to verify, leak, or reset.
  • Validate who you are. No accounts, no logins, no email verification. A pickup-id is not an identity.
  • Know what a message means. To the server, it is bytes in a bucket. The semantics live in the text you wrote.

If You Lose Your PIN

⚠ The contract is the same as saves

Hand-delivered: lose the block or the PIN, lose the message. Server-held: lose the block or the PIN, lose the message — you need both.

In every case, we have no way to recover it. We don't collect an email, a username, or any personal identifier we could use to look it up. That is the entire trade-off — total privacy in exchange for total personal responsibility.

Send a new c-mail with a new PIN. Do not reuse a PIN across messages.

Why Not Just Use Email?

We've weighed it. Regular email means accounts, password storage, email verification, password reset flows, database breaches, phishing risk, spam filters, tracking pixels, HTML rendering bugs, and a permanent server-side record linking every message to a specific human being. For a collection of tiny files and tiny games, that's a massive amount of complexity for almost no benefit.

A PIN + armor block sidesteps all of it. There is no identity to breach. There is no password to reset. There is nothing to phish. And the server never knows who you are — only that somebody stored some ciphertext. At Slot 2 it also sees timing and size; that's the trade for letting the server hold the block, and the exposure table above says so plainly.

C-mail is email stripped back to what it should have been: words, a key, and a block you can hand to someone.