PHANTOM · LIVE OPS · NODE EU-WEST-2
SECURE · TLS 1.3 · SOC 2 — IN PROGRESS
v4.2.1 · MAY 2026
TRUST · SECURITY

Security practices.

Your Minecraft accounts and personal data deserve real protection. Here's exactly what we do.

/ 01

Passwords are bcrypt-hashed

Your Phantom password is run through bcrypt before it touches our database. We store only the hash — not your plaintext password, not a reversible encryption. Even if our database were leaked, your password would be protected.

/ 02

Minecraft auth via Microsoft OAuth only

We never ask for your Minecraft password or session token directly. Authentication goes through Microsoft's own OAuth 2.0 flow — you sign in to Microsoft, and they issue us a scoped access token. Your Microsoft password is never transmitted to or stored by Phantom.

/ 03

OAuth tokens are encrypted at rest

The access and refresh tokens we receive from Microsoft are encrypted with AES-256 before being written to the database, using a key that never exists in the database itself. A database breach alone is not sufficient to recover them.

/ 04

HttpOnly JWT session cookies

Dashboard sessions use HttpOnly, Secure, SameSite=Strict cookies. JavaScript running in the browser cannot read your session token. WebSocket streams use short-lived single-use tickets rather than putting the JWT in the URL.

/ 05

Rate-limited authentication

Login and signup endpoints are rate-limited per IP to slow brute-force attempts. Failed login attempts do not reveal whether the email address is registered.

/ 06

Full audit log

Every login, bot connect, command, and lifecycle event is timestamped and associated with your account. You can review the log from the dashboard at any time. Retention is 7 days on Free, 30 days on Trial/Pro, 1 year on Custom.

Security | Phantom