Operational records are used to make the bot and dashboard work, not to build ad profiles.
VERTEX Privacy Policy
Privacy without the fog.
VERTEX stores the operational data it needs to run Discord server tools: moderation, tickets, configuration, protection, music state, giveaways, logs and dashboard access. The goal is simple: keep communities manageable without exposing private infrastructure.
Plain summary
The short version.
This summary is here so server owners can understand the practical privacy shape before reading the full policy.
Examples include server IDs, user IDs, channel IDs, role IDs, cases, tickets and configuration.
Authorized operators can ask for review, correction or deletion where technically and legally possible.
Legal note.
This page is written to be clear and practical, but it should not be treated as legal advice. A qualified professional should review it for your jurisdiction and business needs.
Where it applies
One policy for the VERTEX platform.
This policy covers the systems that make VERTEX usable as a Discord operations platform.
Discord bot
Slash commands, moderation workflows, tickets, protection, music, giveaways, logs, reaction roles, verification, welcome messages, backups and health checks.
Web dashboard
Discord OAuth sign-in, selected server workspace, live bot status, Lavalink telemetry, configuration panels and guarded staff actions.
Public website
Documentation, support links, invite links, legal pages and public product information hosted at botvertex.pro.
Support channels
Information you choose to provide when asking for help, reporting issues, requesting changes or discussing a server setup.
Data we use
What VERTEX may store.
VERTEX is built around Discord server operations. Stored data is usually tied to a server, channel, role, user, message, case or feature setting.
IdentifiersDiscord server IDs, user IDs, channel IDs, role IDs, message IDs and interaction IDs.
ConfigurationEnabled modules, log channels, ticket categories, verification settings, AutoMod rules, music defaults, giveaways and role settings.
ModerationWarnings, timeouts, kicks, bans, case history, reasons, staff actions and audit-style records.
SupportTicket metadata, claims, replies, transcript references, close reasons and staff notes where configured.
Community systemsLevel progress, karma, reaction role selections, welcome state, creator alerts and giveaway entries or winners.
Operational healthBot status, database availability, Lavalink readiness, latency, server counts, runtime checks and dashboard session state.
Support requestsInformation voluntarily sent through official support resources, such as server context, screenshots or issue descriptions.
Why it exists
Data has a job.
VERTEX uses stored information to provide features, protect servers and keep operations understandable.
Run enabled features
Configuration tells VERTEX which channels, roles, rules and workflows belong to each server.
Protect communities
Moderation, AutoMod, anti-raid and verification records help prevent abuse and support accountability.
Support staff decisions
Case trails, ticket history and logs help moderators understand what happened without guessing.
Keep the service reliable
Health signals, runtime checks and storage state help diagnose issues before they become user-facing problems.
What VERTEX does not need.
VERTEX does not need your Discord password, payment card details, private account credentials or direct access to your personal device.
Dashboard privacy
The dashboard shows operations, not secrets.
Dashboard 1.0 is designed to let approved operators control a server without revealing infrastructure details.
Discord OAuth
Sign-in is handled through Discord. VERTEX uses the account identity and server access needed to decide which servers are manageable.
Selected workspace
Dashboard actions operate on the selected server. Operators should always confirm they are viewing the correct server before changing settings.
Hidden internals
Tokens, database paths, filesystem locations and private bot endpoints are not displayed as public dashboard details.
Guarded actions
Sensitive actions use confirmations or controlled flows so accidental destructive clicks are harder to make.
Storage and retention
Kept only while it still has a reason.
Retention depends on the type of record and the feature that created it.
- Configuration may remain until changed, reset, deleted or the server stops using VERTEX.
- Moderation and security records may remain to preserve accountability, integrity and abuse prevention.
- Ticket transcripts and logs may remain according to server configuration and support requirements.
- Backups may remain for a limited retention period depending on the configured recovery behavior.
- Temporary sessions and runtime signals may expire automatically when they are no longer needed.
Backups and integrity records.
Some data may not be removed immediately if it is needed for abuse prevention, recovery, moderation integrity, legal obligations or platform security.
Sharing
When data can leave VERTEX.
VERTEX does not sell personal data. Data is shared only when the service, support, safety or law requires it.
Discord
Actions and messages are sent to Discord because VERTEX operates inside Discord servers.
Authorized server staff
Server owners and approved operators may see records relevant to their own server through commands or dashboard views.
Infrastructure providers
Hosting, support, API or infrastructure providers may process limited information required to keep the service running.
Safety and legal needs
Information may be disclosed if required to comply with law, respond to abuse or prevent harm.
Third parties
VERTEX depends on platform services.
Some systems are outside VERTEX's direct control.
VERTEX may interact with Discord, Twitch, YouTube, Lavalink nodes, hosting providers, domain providers, contact or support tools and other infrastructure used to deliver the service. Those services have their own privacy policies, retention practices, outages, rate limits and security controls.
Requests
How to ask for review, correction or deletion.
Requests work best when they come from a server owner or authorized administrator and include the relevant Discord server ID.
What to include
- Your Discord user ID.
- The Discord server ID.
- The feature involved, such as tickets, moderation or giveaways.
- A clear explanation of what should be reviewed.
What may limit deletion
- Security and abuse prevention records.
- Moderation integrity and case accountability.
- Backup recovery windows.
- Legal or platform obligations.
Age and eligibility
Discord rules still apply.
VERTEX is intended for use through Discord and follows Discord's platform requirements.
Users must meet Discord's minimum age and eligibility requirements. Server owners are responsible for managing their own communities appropriately, including communities where minors may be present.
Contact
Questions should go through official support.
Use the support server for privacy questions, data requests, dashboard issues or server-specific help.
Need help with privacy or stored data?
Bring the server ID and the feature involved.