NEXUS WEBINDEPENDENT CREATORS + SHARED CREW

SECURE CHANNEL // SECURITY POSITION

TRUST
NEEDS
PROOF.

Using encryption is a foundation, not a finished security claim. This page separates what the clients do now from what must still be deployed, tested, and independently reviewed.

NON-NEGOTIABLE RULES

WHAT WE WILL NOT FAKE.

  1. We do not invent a custom encryption algorithm for chat content.
  2. We do not build an owner or administrator backdoor for decrypting private messages.
  3. We do not log passwords, access tokens, recovery secrets, encryption keys, or private-message bodies.
  4. We do not call server-visible metadata anonymous.
  5. We do not publish automatic updates that pass without a valid signature and package hash.
  6. We do not place the Matrix homeserver database on shared cPanel hosting.

BEFORE A PUBLIC SECURITY CLAIM

THE WORK
STILL OWED.

DEVICE TRUST

SAS/QR verification, recovery-key setup and restore, device listing, and remote revocation.

INFRASTRUCTURE

Real homeserver integration, rate-limit and abuse testing, monitoring, encrypted backups, and restore drills.

RELEASE CHAIN

Offline signing-key handling, signed update manifests, package hash enforcement, and Windows code signing.

INDEPENDENT REVIEW

Authentication, recovery, client storage, updater, server configuration, and penetration testing by somebody outside the implementation work.