Security / Transparency

Built with defense in depth.

A private portal benefits from careful defaults and external security review. No web application can promise absolute security.

◇

Identity protection

Argon2id password hashing, server-backed sessions, session invalidation and blocked-account handling.

↗

Request integrity

CSRF tokens, same-origin checks, strict response headers and parameterized SQL queries.

⌗

Code security

Secure random invitation and license codes, keyed hashes and atomic one-time redemption.

Important deployment requirements

A safe local build is not a security certification for the public internet.

01
Terminate HTTPS at a hardened reverse proxy

Use a valid TLS certificate, protected secrets and HSTS. The development web server must stay bound to localhost.

02
Add edge protection and monitoring

Configure WAF rules, bot mitigation, DDoS protection, IP rate limiting and actionable alerts.

03
Audit and maintain

Perform penetration testing, dependency scanning, operating-system patching, backups and regular security reviews.

04
Configure Discord permissions carefully

The bot must have Manage Roles and its highest role must be above the role it grants. OAuth should request only necessary scopes.