I've Been Building a Messenger Wrong. Here's What Changed.

Description and use

Halonyx rethinks privacy by treating encryption as a floor, adding default settings that protect behavioral data and limiting metadata collection.

Problem

Designing a secure messaging system that protects privacy beyond encryption, accounting for behavioral impacts of interface features and data‑driven profiling.

Outcome

Halonyx achieves a higher standard of privacy by treating encryption as a floor, not a ceiling, and by designing interface defaults and data handling to prevent behavioral surveillance and data‑driven profiling.

Workflow

• 1. Identify each feature and ask two questions: can it be implemented? what behavior will it encourage?
• 2. Apply privacy‑by‑default defaults (e.g., read receipts off, symmetric hiding).
• 3. Separate data into tiers (Provided, Derived, Inferred) and avoid storing inferred data.
• 4. Use sealed‑sender delivery to hide sender identity from the server.
• 5. Store message blobs only until delivery and delete thereafter.
• 6. Perform AI processing locally and discard temporary data.
• 7. Declare retention policies per space and make changes visible to members.
• 8. Publish a list of refused capabilities (no productivity scoring, no silent admin access).

Evidence

The usual defence of privacy is a defence of secrets, which is why "I have nothing to hide" feels like a reasonable reply.

Source

Read receipts off by default, configurable per conversation, and symmetric - hiding yours also hides theirs.

Source

Halonyx uses the Signal Protocol - X3DH for key agreement, Double Ratchet for per-message keys.

Source

Define the need → Select minimum context → Process → Discard what was temporary

Source

It will not compute productivity, sentiment, or personality scores from message data.

Source