Authentication Methods
Discord OAuth2 (Recommended)
Botify uses a full browser-based OAuth2 flow:- Browser opens
discord.com/oauth2/authorizewith Botify’s client ID - You authorize scopes:
identify+guilds.members.read - Botify verifies you have the “Client” role in the official Botify Discord server
- Your Discord User ID is stored locally and synced to MongoDB
License Key System
Keys follow the format:BOTIFY-XXXXX-XXXXX-XXXXX-XXXXX
- Keys are stored in the
botify_licensesMongoDB collection - Keys are HWID-bound on first activation — tied to your hardware fingerprint
- Activating on a different PC requires a manual HWID reset via Botify support
Local Data Security
DPAPI Encryption
When Encrypt Account Data is enabled in Settings → Security:account_store.jsonis encrypted using Windows Data Protection API (DPAPI)- Encryption is tied to your Windows user account — only the same user on the same machine can decrypt
- Switching Windows users or reinstalling Windows requires re-adding accounts
DPAPI encryption is optional and disabled by default. Enable it if you share your PC with other users.
Cookie Storage Security
.ROBLOSECURITY cookies are stored in MongoDB with a unique index on (owner_id, pc_name, username):
- Prevents any Botify node from reading another user’s cookies
- Cookies are scoped per-user and per-PC — multi-PC setups remain isolated
Command Authentication
Every Botify node generates a 32-byte random token (command_token) on first run. All remote commands must include this token:
auth_token are silently rejected — no error is returned to prevent enumeration attacks.
Administrator Elevation
Botify auto-elevates to Administrator on startup. This is required for:Enterprise Access
Enterprise Cluster mode is unlocked by either:- An
enterpriseplan license key inbotify_licenses, OR - Specific Discord User IDs or roles configured as staff in the Botify system