This Policy covers NeoX HUB, its web control panel, managed Discord bot features and the NeoX HUB Access OAuth application. “We” means the independent NeoX HUB operator. NeoX HUB is not affiliated with Discord Inc.

Discord separately processes your information under Discord’s Privacy Policy.

Discord sends a temporary OAuth code and access token during sign-in. The token is used once to request /users/@me, is not written to storage and is revoked after the identity check.

Depending on enabled features, bot events may include role selections, voice state, moderation events, ticket content or messages explicitly processed by a command. The OAuth application does not read your private messages.

• authenticate your Discord identity against the owner’s allow-list;
• show the correct bots and sections and enforce permissions;
• perform actions requested by you or a server administrator;
• operate, troubleshoot, secure and prevent abuse of the Service;
• comply with law, Discord requirements and valid safety requests.

We do not sell personal data, run behavioural advertising or use Discord API data to train machine-learning models.

• Discord: authentication and requested bot actions through Discord APIs;
• Cloudflare: reverse proxy, encrypted tunnel and security delivery;
• media providers: only when an authorized user requests third-party search or playback;
• legal and safety: where required by law or necessary to protect users or the Service.

Server owners and administrators can see information produced inside their server according to Discord permissions. Ticket transcripts or bot messages posted to Discord remain subject to the server’s settings and Discord’s systems.

NeoX HUB uses strictly necessary cookies for OAuth and the signed-in session. They are Secure, HttpOnly and SameSite=Lax. We do not use advertising or cross-site tracking cookies.

The OAuth state cookie is one-time and short-lived. A session lasts at most 12 hours and expires after 2 hours of inactivity. Sessions are held in memory and cleared when the service restarts.

• Allow-list and profile: kept locally while access remains approved, then removed by the owner.
• OAuth access token: not stored and revoked after identity verification.
• Session data: in memory until logout, expiry, disablement or restart.
• Configuration: kept while the related bot or feature is in use and removed by the owner.
• Operational logs: kept only as reasonably needed for security and troubleshooting, unless a security incident or law requires longer retention.
• Content posted to Discord: retained under the relevant server settings and Discord controls.

You can revoke NeoX HUB Access from Discord User Settings → Authorized Apps. To delete your NeoX HUB allow-list/profile record, ask the owner who granted access to remove your Discord User ID from the local Users panel. Removal invalidates the next panel request and prevents future sign-in.

You may request correction, disablement or an explanation of permissions. Contact stylr.7 on Discord and include your Discord User ID. Deleting NeoX HUB access does not automatically delete content already posted inside Discord; contact the relevant server administrator for those records.

We use HTTPS, secure and HttpOnly cookies, one-time OAuth state, short-lived sessions, access controls, rate limits and local storage for sensitive configuration. No system guarantees absolute security. If your data is at risk, revoke the application and contact the operator promptly.

The Service is not intended for children under 13 or under the minimum age required by Discord in their country. We do not knowingly approve access for anyone who cannot lawfully use Discord.

We may update this Policy when the Service, data practices, law or Discord requirements change. The date above shows the current version. Material changes will be published at this same public URL.