Back to Blog
Update July 30, 2026 8 min read

Why Your Messages Aren't Encrypted (And Why We Think That's Right)

Every messaging platform's marketing says the same two words: end-to-end. So here is an update post you don't see often. NuPalz player messages are not end-to-end encrypted — they used to be, and in January 2026 we deliberately turned it off. Not quietly, either: the decision is written into the code itself, and our legal pages have said so all along. This post is the long version of why, because a choice this unusual deserves better than a line in a changelog — and because if you disagree with the trade we made, you should get to disagree with the real one, not a rumor of it.

What Actually Happened

NuPalz shipped genuine end-to-end encryption for player-to-player messages in an earlier version of the messaging system. It worked the way E2EE is supposed to: messages were encrypted on your device and decrypted on the recipient's, and the server in between carried ciphertext it could not read. Then we removed it — on purpose, in one deliberate change, with the reasoning documented where every future developer would see it. The encryption library that ships to your browser today is a compatibility stub, and its own header is blunter than most announcements:

js/nupalz-e2ee.js — v3.0.0, January 2026 “E2EE HAS BEEN DISABLED to enable full message moderation for child safety. All messages are now stored and transmitted as plaintext.”

One clarification on that comment's wording, because “plaintext” means something specific to engineers and something scarier to everyone else. It means the application no longer encrypts messages end-to-end — the server can read what you send. It does not mean your messages travel across the internet exposed: all NuPalz traffic, messages included, moves over HTTPS/TLS like the rest of the modern web, so someone on your café's Wi-Fi still sees nothing. What changed is who holds a readable copy. Before: only you and your recipient. Now: you, your recipient, and the platform.

Why We Did It

NuPalz is a creature-collecting game with open registration and players of all ages, including kids. That single fact drives the whole decision, because it puts two good things in direct conflict:

You cannot have both. That is not a NuPalz limitation; it is what end-to-end means. With E2EE, when a player reported a message, the server had no way to see what was actually said — our old report endpoint literally had to ask the reporter's device to submit its own decrypted copy, which meant a report was unverifiable by design. Moderating harassment, scams, or an adult saying something to a child that no adult should say — all of it depended on trusting whatever the reporting client chose to send. On a platform for adults, that trade can be defensible. On a platform where a twelve-year-old can receive a message from a stranger, we decided it wasn't.

So the rule we chose is the same one behind the forums: Nutopia's shared spaces are human-readable by design, because spaces that minors can enter get moderated for real, not theatrically. The forums make that obvious — posts are public. Messages just extend the same principle to the one-to-one case, where the stakes are higher precisely because nobody else is watching.

What It Costs You — Stated Plainly

An honest trade has a cost column, and here it is without softening. Because messages are readable by the platform:

And to be equally clear about what we are not claiming: this is not an argument that end-to-end encryption is bad. For journalists, for organizers, for private adult conversation, E2EE is one of the best things software does, and plenty of platforms are right to offer it. Our claim is narrower — it is the wrong default for this platform, with this audience, where the ability to verify a child's report outweighs the operator-proof privacy of a trading chat about Berry Barn prices.

What You Get Back

The benefit side of the ledger is the report button actually working. Report a message — the options are spam, harassment, inappropriate content, scam, or other — and a human reviews the real content, not a client-supplied claim about it. Combined with the moderation stance our privacy policy and Terms describe, that gives Nutopia's messages the same property its forums have: bad behavior is findable, verifiable, and actionable. For a game whose newest trainers are often its youngest, we think that is the right side of the trade to be on.

One scope note: this post is about player-to-player messages. Conversations with your palz are a different system with their own write-up — how companion chat works covers where those words go.

The Part We're Oddly Proud Of

Most platforms that quietly lack E2EE simply never mention it and let the marketing haze do the work. We'd rather be the platform whose code comments tell you the truth — the stub that replaced our encryption library announces what happened in its second line, our legal pages have disclosed message review since before this post existed, and nothing anywhere on NuPalz has ever claimed your messages were encrypted end-to-end. No retraction was needed to publish this article. That is the standard we try to hold: the uncomfortable version, in writing, before you ask.

If the trade we made changes how you use messages, that is the article working as intended. Say less in DMs, trade openly, report freely — and if you want the fully private version of a conversation, have it somewhere built for that, with our blessing.

Previous: Why Fire Fears Water All Articles