NEXORA CUPS / LOCAL RECOVERY BUILD

Privacy policy

Last updated: 6 November 2026

This page describes the recovered local build in this folder. It is not the former production service. Epic display-name requests are reviewed manually; the service does not sign in to Epic or verify account ownership.

Information handled

  • Discord sign-in: Discord provides your account identifier, username/profile information, and servers you can manage. The app uses that information to show your account and available servers.
  • Server settings: Verification-panel text, rules packs, slash command names, selected Discord channels, and selected roles are stored in the local .nexora-data.json file. Rules images uploaded through the dashboard are stored under the local uploads/rules folder.
  • Support and staff applications: Support options create private Discord channels. Staff applicants submit their name, availability, experience, preferred role, and reason for applying; these answers are posted in the private application channel and stored locally with its ticket record. The channel is visible to the applicant, configured staff role, and server members with management permissions.
  • Channel locks: When an authorized staff member locks configured channels, the app stores the previous permission overrides for the affected permissions so they can be restored on unlock.
  • Temporary voice channels: When a member joins the configured lobby, the bot creates a voice channel for them and stores the channel and owner IDs to manage its owner commands and delete it when empty. The bot observes Discord voice-state changes while connected.
  • Bot customization: The selected server's bot nickname is stored in Discord. The optional bot avatar and banner settings update the bot's global profile and affect every server where the bot appears.
  • Discord messages: When an administrator chooses to post, the bot sends the configured panel or message to the selected Discord channel. Discord then stores that message under Discord's own policies.
  • Epic display-name review: If you use the verification button, the bot creates a single-use link that expires after 15 minutes and DMs it to you. The submitted Epic display name, your Discord user ID/name, submission time, and request status are stored. If configured, the request is also posted in the selected admin review channel with Verify and Decline buttons. The reviewing administrator's Discord ID and decision time are stored.
  • Scrim eligibility: Only players whose Epic display-name request has been approved can join locally managed scrim signups. Their approved Epic name is included in the signup roster.
  • Credentials: The form never asks for or collects Epic passwords, login codes, or security codes. An administrator's review confirms only the submitted display name, not ownership of an Epic account.

Where information is stored

In this local setup, sign-in sessions and their Discord account/server data are held in the local server's memory and are cleared when that server stops. Panel settings, ticket records and staff application answers, channel-lock permission snapshots, temporary voice channel and owner IDs, hashed one-time verification tokens, Epic display names, and request status are stored in the local .nexora-data.json file until removed by the operator. No Nexora cloud database is configured in this recovered build.

The local site is intended to be opened on the same computer at http://localhost:8787. If you deploy or expose it elsewhere, hosting, security, retention, and privacy responsibilities change; review those arrangements before inviting other users.

Sharing and third parties

Discord processes OAuth sign-in and bot activity under its own privacy policy and terms. The site also loads web fonts from Google Fonts. The local build does not intentionally sell personal information or include analytics.

Retention and your choices

Sign out to clear the browser's session cookie. Stop the local app to clear in-memory sessions. The operator can remove stored verification requests and settings from .nexora-data.json. Messages and DMs already sent must be managed in Discord.

Contact

For questions about this local copy, contact the person who operates the Nexora Discord server where the bot is installed.