Policies
Bot privacy policy
This policy explains what VPG Central uses and stores for league invitations, verified team access, VPG information, availability, lineups and private owner-directed moderation.
01 / Scope
Who this policy covers
VPG Central is operated by the Virtual Pro Gaming (VPG) bot administrators. It works in Discord servers where the bot has been added and configured. This page covers the bot, its commands, invitations, administrator panel and separate private VPG emergency controls. It does not cover the rest of noirnetwork.org, which has a separate website policy.
02 / Information
Data we use
Discord identity & access
User and server IDs, usernames, display names, server nicknames, role memberships, and relevant role and channel IDs. These let the bot identify the right manager, member, league, and server.
Actions & records
League configuration, command and button actions, invitations and responses, assignments, delivery details, and operational audit records. These support access management and troubleshooting.
Verified team access
Where enabled, team names and identifiers, the verified Main Manager’s Discord ID, team role and private-channel IDs, access requests and reviewer IDs, expiry and message-cleanup details, and team action audit records.
Availability posts
Matchday dates, public team and fixture details, optional notification-role IDs and embed titles or descriptions, the creator’s Discord ID, server, channel and message IDs, and each respondent’s Discord ID, display name, selected response and response timestamp. Older custom-event records may also contain event titles, optional times and descriptions. These records keep availability graphics up to date and allow recovery after restarts.
Lineups
Server-specific access settings, allowed role and member IDs, the creator’s Discord ID, server, channel and message IDs, the selected public VPG team and formation, assigned Discord member IDs and display names, player confirmation and backup responses, saved display settings, and any explicitly selected lineup role and tracked role memberships. These records keep lineup graphics current and allow recovery after restarts. Lineups are separate from availability posts.
Team-tool staff and reminders
Availability and lineups share a server-specific staff allowlist configured by Administrators. The bot checks server member counts to limit where these tools are enabled. Optional reminders record the selected VPG matchday, scheduled deadlines, eligible recipient IDs, delivery state and message IDs to avoid repeated notifications. Availability reminder eligibility uses the selected team-role membership and current responses; lineup reminders use the assigned XI and confirmation responses.
Admin-panel security
Administrator session and login-security records, including hashed identifiers used to limit failed sign-in attempts. The panel uses a session cookie after sign-in; the admin password is not stored as plaintext by the bot.
Private emergency moderation
Where enabled for the official VPG server, operator and target Discord IDs, channel, role and selected message IDs, message creation times, reviewed reasons, permission and nickname states, timeout choices, action counts/statuses, timestamps, intent and continuation receipts, and moderation audit records. Saved channel permission preimages allow a guarded restore. Channel history is fetched to identify messages for an authorized cleanup; message text and attachments are not copied into these moderation records.
Emergency-panel sign-in
Separate single-use link and session records identify the eligible Discord owner and server, store token hashes and expiry times, and use a secure session cookie and CSRF protection. Plaintext link and session bearer values are not stored in the database. The shared administrator-panel password does not grant this access.
Optional server subscriptions use Stripe-hosted Checkout. The bot stores the server and billing owner’s Discord IDs, relevant Stripe resource IDs, billing state, timestamps, and access audit records. It does not receive or store payment card details. See the subscription privacy policy for those records and subscription terms for price, renewal and cancellation.
The co-manager service does not need to read the content of ordinary Discord channel conversations.
03 / Purpose
What the bot does with it
The bot checks which leagues a member can manage, recognizes existing co-managers where possible, creates and processes invitations, displays current access, and adds or removes configured Discord roles. It may adjust a server nickname when the relevant feature is enabled and the bot has permission. Admins use the panel to configure leagues, roles, and notification channels.
The optional team-access system lets staff verify Main Managers, creates team roles and private channels, and lets team managers approve or directly manage Co-Manager and Player access. Members can remove their own Co-Manager or Player access. Where enabled, it updates server nicknames using the team and Discord display name. It does not change VPG registration or link Discord accounts to VPG accounts.
Staff can explicitly post availability for a team’s chosen matchday after reviewing a private preview. The preview can include an optional title or description and up to ten roles to notify; leaving these empty adds no custom heading or role notification. The bot records Available, Unsure or Unavailable reactions, updates the response graphics, checks team fixtures for additions, removals and rescheduling, and closes voting at the end of the selected UK date. All games for the chosen day stay on one schedule graphic; responses appear separately, with private pages for longer lists, subject to safe upload limits. Availability does not assign Discord roles.
Server Administrators configure who may create and manage lineups. Authorized staff choose a public VPG team, formation and server members, review the graphic and explicitly publish it. Players respond only for themselves. The bot updates names, positions, confirmation states and an optional backup list inside the existing graphic. Staff may explicitly enable a temporary or existing lineup role for selected players, subject to Discord permissions and tracked cleanup. Lineups do not link VPG accounts or change availability responses.
The separate VPG emergency panel lets the current eligible server or bot application owner review and confirm moderation actions: channel locks and saved-permission restores, member-role removals, nickname changes, explicit timeouts and one account’s selected messages in a channel. Ownership, current server access, permissions and role hierarchy are checked again before changes. A reason and typed confirmation are required for normal panel actions. Separately authorized, fixed incident cleanups may resume their recorded scope from durable checkpoints until their stated deadline; they are not a continuing general monitoring service.
In eligible smaller servers, staff can enable automatic reminders for an availability or lineup post. These mention only eligible members who have not replied, normally 24 hours and 2 hours before the first actionable match. Any availability response, or a lineup Confirm, Back Out or Backup, suppresses that member’s reminder. Reminders do not send DMs, mention entire roles or use @everyone. Changing a lineup to a different matchday clears that old date’s replies only when staff explicitly save the change.
04 / Visibility
Messages and who can see them
Invitation and status messages may be delivered by Discord DM. If a DM cannot be delivered, the bot may post an invitation in the fallback channel selected by that server’s administrators and mention the people involved. Anyone with access to that channel can see the message and its league and participant details. Discord roles and server nicknames are visible according to that server’s settings.
Do not use a public fallback channel if those details should stay limited to a smaller group. Server administrators control that channel’s permissions.
Team-access requests use the configured private staff or team-manager channel rather than automatic DMs. Relevant reviewers and requesters are mentioned. Server administrators can still access private channels through Discord’s permissions.
Availability is posted in the channel where staff confirm publication. Anyone who can view that message can see its custom heading, match details and response names. Staff may choose up to ten roles to notify when the post is first published. The bot does not send those notifications again when fixtures or responses update, and it does not send availability DMs. Without selected roles, no availability notification is sent. Server administrators control who can access the channel.
Lineup graphics are visible to members with access to their channel, including player names, assigned positions, confirmation states and any displayed backups. Private editing and response controls remain bound to the person using them; administrators control the channel’s visibility and shared team-tool staff allowlist. Publishing and updating the graphic does not automatically ping players or send DMs. Explicitly enabled reminder messages are visible in the post’s channel and mention their eligible recipients individually.
Emergency previews, selected account details, saved permission snapshots and action history are private to eligible owners. The page does not publish a moderation report or retained message bodies to a channel. Changes to Discord roles, nicknames, timeouts and channel permissions remain visible according to Discord’s own server and audit-log settings. Message deletion is permanent; the bot does not keep a body/attachment archive from which to restore deleted messages. Operators should not paste private message text or credentials into saved reasons.
06 / Retention
How long records remain
Configuration and assignment records are kept while needed to run the bot. An invitation normally expires after 24 hours, but its record, response, and related audit details may remain so administrators can investigate access changes, failures, or abuse. There is no fixed automatic deletion period for those records.
For the separate team-access system, unanswered requests expire after 24 hours. Completed request messages are scheduled for removal after five minutes and expired notices after three hours. Completed team request records and team action audit entries are normally deleted after 90 days; unresolved message-deletion failures are retained for retry. Team settings and verified manager records remain while needed to operate team access.
Availability posts and remaining responses, including older custom-event records, have no fixed automatic deletion period. Closing voting or deleting the Discord post does not automatically erase its database record. During active voting, removing your selected reaction withdraws your saved response when the bot processes or reconciles that change. For a closed post or other deletion request, contact the bot administrators using the address below.
Lineup access settings, posts and responses have no fixed automatic deletion period. Closing a lineup or deleting its Discord message stops tracking but does not erase its saved record. Players can change their own response while the lineup is open; for correction or deletion of other saved data, contact the bot administrators below.
Admin sessions expire; expired or revoked session records are normally removed after seven days, and login-throttle records after two days. Access to the admin panel is restricted and sessions are protected. No online service can guarantee absolute security.
Emergency sign-in links expire after five minutes and work once; emergency sessions expire after thirty minutes. Normal action previews expire after ten minutes. Expiry immediately limits authorization but does not itself mean a stored record has been erased: pruning removes expired links/sessions and unused expired previews when run. Completed, partial and failed emergency actions, reasons, saved channel locks, moderation audits and fixed-incident checkpoints have no fixed automatic erasure period in this implementation. An incident deadline stops further campaign changes; it does not delete its journal or permission preimages.
07 / Your choices
Access, correction, or deletion
You may decline an invitation or ask a server administrator to remove co-manager access. For questions about information held by the bot, or to request access, correction, or deletion, email legal@noirnetwork.org. Include your Discord user ID and the relevant server ID so we can identify the right records. Please do not include passwords or other sensitive information in your email or a public channel.
We may need to verify that the request concerns your account. Some records may need to remain while they are necessary for active access management, security, or legal obligations. If privacy law gives you additional rights, you can raise them through the same address.
Email a privacy request08 / Updates
Changes to this policy
We may update this page when the bot or its data practices change. The date at the top shows when this version was published.