Privacy Policy | Discortics

Last updated: October 8, 2026

Please Read This Policy Carefully

Discortics™ provides Discord bot, dashboard, website, documentation, support, and related services (the "Services"). This Privacy Policy explains what information we collect, why we use it, how we protect it, when we share it, and what choices you have.

This Policy is a notice about processing, not a request for blanket consent. Using Discortics does not waive your data protection rights. Server administrators should inform members about enabled features and their data use. Administrator configuration does not replace a lawful basis or any consent required from affected users.

This Policy applies only to Discortics. Discord, payment providers, analytics providers, hosting providers, and other third-party services have their own policies.

1. Information We Collect

We collect only information that is reasonably needed to operate, secure, improve, support, and bill for the Services.

Discord Account and Server Data

When you use Discortics through Discord or authorize the dashboard, we may receive information from Discord's API, including:

Discord user IDs, usernames, display names, avatars, and public profile data.
Discord guild/server IDs, names, icons, member counts, roles, channels, permissions, and bot installation status.
Configuration choices made by server administrators, such as module settings, command settings, prefixes, moderation settings, ticket panels, role menus, verification settings, embeds, giveaways, applications, suggestions, levels, economy settings, and other bot feature configuration.
Content and metadata needed to perform enabled bot features, such as moderation cases, warnings, logs, ticket metadata, form/application responses, suggestion content, giveaway entries, verification events, command usage, message IDs, channel IDs, role IDs, timestamps, and audit records.
Message content only where it is necessary for an enabled feature, moderation rule, automation, support flow, command, or abuse-prevention function to work.

When a server administrator enables Snipe, Discortics temporarily retains the most recently individually deleted cached message in each eligible channel so members who can view that channel and read its message history can retrieve it with the Snipe command. Bulk-deleted messages are excluded. Discord's individual message-delete event does not identify who performed the deletion, so the retained message may have been deleted by its author or by someone with permission to manage messages. Displayed results redact links, email addresses, attachment links, and attachment previews. The configured confession channel is excluded. Snipe is disabled by default. Its snapshot expires when the original message's ordinary cache period would have expired, and deleting a message does not extend that period.

Dashboard, Website, and Support Data

When you use our website, dashboard, documentation, or support channels, we may collect:

Account/session data used to authenticate you and keep you signed in.
Browser, device, IP address, cookie, log, and analytics data.
Support messages, bug reports, feedback, screenshots, diagnostic details, and other information you choose to provide.
Administrative actions you take in the dashboard or through bot commands.

Advanced Verification

When a server enables Advanced verification, Discortics screens for restricted connections. Alt checks are on by default and can be disabled by server administrators. With alt checks enabled, we also use network information and browser/device fingerprinting to screen for linked accounts. With alt checks disabled, we process the connection transiently for network screening and the Cloudflare challenge, without collecting a browser fingerprint or storing IP or device matching signals for that check. Verification state and timestamps are still stored. Turning alt checks off does not erase matching records collected earlier or through other participating servers; those records follow the retention policy below. Collection starts after the disclosure and your Continue action. We process connection information, browser and device characteristics, and security-challenge data to support community abuse prevention.

When alt checks are enabled, our stored matching data includes:

A keyed HMAC-SHA-256 hash of your IP address for network matching.
Keyed HMAC-SHA-256 hashes derived from combinations of browser/device fingerprint signals for device matching.
Your Discord user ID, participating server IDs, verification state, and verification and membership timestamps.
Technical metadata identifying the matching-provider and hashing-key versions, plus temporary verification-session and challenge state.

Raw IP addresses and raw browser/device observations are processed for the check but are not stored in verification records. We use the connection's network number (ASN) for network screening without retaining it in your matching proof. Our browser check does not request location permission, and our verification records do not contain GPS coordinates, city, country, or location history. These statements describe Discortics verification storage; website logs, analytics and Cloudflare processing are separate categories described in this policy.

Matching hashes remain pseudonymous personal data linked to your Discord account, not anonymous data. Verification sessions expire after one hour and are subsequently removed by scheduled cleanup.

We also keep internal verification decision summaries for support and review: your Discord and server IDs, the outcome and reason category, whether the report came from our checks or your browser, first and latest occurrence times, and an attempt count. A summary may identify a linked account and the categories of checks involved. Browser-reported failures are diagnostic reports and do not establish wrongdoing. These summaries contain no raw network addresses, browser/device observations, stored matching values or security credentials. They are restricted to authorized Discortics operators and are not shown on the public verification page.

Matching links Discord accounts across all participating servers. A shared network or matching browser/device characteristics can link accounts. Clearing cookies or using a private window may not prevent matching because device characteristics can still be observed; no identifier is guaranteed to persist or to be unique. Another linked account's presence, ban or recent departure may prevent automatic verification. Shared networks, similar devices and changing browser settings can produce incorrect results; a match does not establish identity or wrongdoing. Missing or unavailable checks leave verification incomplete. Existing verification records can be reused in other participating servers. You may decline the check, remain unverified and ask server staff for human review or another way to join. A staff whitelist applies only to that server; Discortics cannot guarantee a server's admission decision.

Cloudflare processes network information and challenge data to proxy and secure the connection. We collect browser/device observations through our own verification service, without an external fingerprinting vendor. Network screening lists are downloaded in bulk without sending visitor identifiers to their providers. See Cloudflare's privacy policy.

The purpose is duplicate-account screening and community abuse prevention. Where applicable, we rely on legitimate interests subject to necessity and balancing assessments; terminal-access or fingerprinting consent must also satisfy applicable local rules, unless a specific exemption applies. A Continue action alone does not establish that every jurisdiction's requirements are met. Server administrators determine their server's verification policy; Discortics determines how the global verification records are operated. Retention is described in section 7 and your rights in section 10.

Privacy and Data Removal

Use /privacy, ;privacy, or Dashboard → Privacy to open the signed-in Delete my data flow. It confirms deletion for your own Discord account; server-management permission is not required. For other privacy rights or help, email info@vexvo.io.

Leave all servers using Discortics first. Membership and new activity can create fresh data.
Confirm permanent deletion of your personal data from active Discortics databases and caches, including levels, stored messages and counters, feature records and Advanced verification data.
Deletion removes verified access across servers. You cannot verify with Discortics for three calendar months from confirmation.
Lifetime Premium and its custom bot access are removed. Transfer them before confirming if you want to keep them.
Active subscriptions and other owned custom bots must be cancelled or transferred before deletion can be queued.
The automated flow preserves other users' data and server-owned content. It does not erase every historical Discord-hosted message, legally retained payment-provider records or rotating backups.

We store your Discord ID, a request reference, timestamps and cleanup status while processing the confirmed request. Confirmation tokens are stored only as hashes and expire after five minutes. The dashboard distinguishes queued, processing, blocked and completed requests. A queued request or a staff notification does not confirm deletion. Cleanup removes verified access where applicable, notifies relevant server staff and records completion only after the required cleanup succeeds.

A minimal receipt and session-revocation record remain for seven days after completion. A separate record containing your Discord ID and verification restriction expiry remains for three months from confirmation. Other data protection requests are handled separately by email; contact us about applicable rights, retained records or a blocked deletion.

Billing Data

If you purchase paid Services, we and our payment providers may process purchase records, plan details, invoice data, transaction identifiers, payment status, billing contact details, tax information, and fraud-prevention signals. Discortics does not intentionally store full payment card numbers or full card security codes.

2. How We Use Information

We use information to:

Provide, operate, maintain, and secure the Services.
Authenticate users and confirm permissions for server management.
Deliver enabled bot features and dashboard functionality.
Process payments, subscriptions, invoices, renewals, cancellations, refunds, taxes, fraud checks, and account status.
Provide support, investigate bugs, respond to abuse reports, and enforce our Terms of Service.
Detect, prevent, and investigate spam, abuse, security incidents, unauthorized access, and violations of law or platform rules.
Improve reliability, performance, usability, and feature quality.
Generate aggregated or de-identified analytics that do not reasonably identify a person.
Send service, security, account, billing, feature, policy, operational, and transactional notices.

3. Service and Transactional Notices

Discortics may, from time to time, send non-marketing service, operational, transactional, account, feature, security, policy, billing, migration, reliability, or announcement notices to users or Discord servers that have chosen to install, configure, purchase, or otherwise use Discortics.

These notices may be delivered through Discord messages, dashboard notices, support channels, email, or other reasonable channels. They are intended to provide information about the Services, account or server status, material feature changes, availability, compliance, safety, billing, migration, or administration. They are not treated as unsolicited marketing merely because they are sent by Discortics to a server or user that uses the Services.

Where a notice is sent to a Discord server, server administrators are responsible for deciding whether Discortics remains installed and which channels or settings are appropriate for that server. Removing the bot, disabling applicable features, or contacting support may stop some future notices, but we may still send legally required, security-critical, account-critical, or service-critical notices where permitted by law and platform rules.

4. Legal Bases for Processing

Where laws such as the GDPR require a legal basis, we process personal data under one or more of the following bases:

Performance of a contract, including providing the Services you request.
Legitimate interests, including security, fraud prevention, service reliability, support, abuse prevention, product improvement, and communicating important service notices.
Consent, where required for optional cookies, marketing, or other optional processing.
Compliance with legal obligations.
Protection of vital interests or public interest where applicable.

5. Cookies and Analytics

We may use cookies, local storage, and similar technologies to keep you signed in, remember preferences, understand usage, improve performance, prevent abuse, and operate the website and dashboard.

You can control cookies through your browser settings. Some features may not work properly if necessary cookies or storage are disabled.

We may use analytics tools to understand aggregate usage and improve the Services. Analytics providers may process limited technical data according to their own policies.

We do not sell personal information.

We may share information with:

Service providers that host, secure, monitor, analyze, support, or process the Services for us.
Payment processors and billing providers for purchases, renewals, fraud checks, tax, invoices, refunds, and chargeback handling.
Discord, where needed for bot and dashboard functionality.
Professional advisers, auditors, insurers, or legal representatives.
Government, law enforcement, courts, regulators, or other parties where required by law or where we reasonably believe disclosure is necessary to protect rights, safety, security, users, or the Services.
Successors or affiliates in connection with a merger, acquisition, financing, reorganization, sale of assets, or similar transaction, subject to appropriate protections.

Service providers may only use information as needed to provide services to us or as otherwise permitted by law.

7. Data Retention

We keep information only as long as reasonably needed for the purposes described in this Policy, including providing the Services, maintaining configuration, supporting users, complying with legal obligations, resolving disputes, preventing abuse, enforcing agreements, keeping backups, and maintaining security records.

Advanced verification retains one global proof while you belong to at least one server with Advanced verification and alt checks enabled. After your last participating membership ends, we retain the proof for one further year for community abuse prevention, then remove it through scheduled cleanup. Confirmed account deletion is handled separately and can remove these records earlier. Leaving one server does not start the one-year period if you still belong to another participating server. Joining a participating server again stops the inactivity period. Disabling Advanced verification or alt checks, or removing the bot, ends that server's participation in global matching retention.

Membership events and periodic checks maintain the retention state. Cleanup rechecks participating memberships before deleting a proof; unavailable or inconclusive checks delay deletion rather than treating an outage as a departure. For older records without a confirmed departure time, the inactivity period starts when absence is first conclusively established. We assess the necessity and proportionality of the one-year safety period; it is not an exemption from your rights. Verification sessions expire after one hour and are subsequently removed by database TTL cleanup; short processing locks also expire.

Internal verification decision summaries expire 90 days after the latest occurrence of the same reason for that account and server, then are removed by database TTL cleanup. Confirmed account deletion includes these summaries.

Confirmed deletion jobs remain available until cleanup succeeds, including when a required step is blocked. Completion receipts and session-revocation records expire after seven days. The separate verification restriction contains only your Discord ID and expiry and lasts three months from confirmation. General privacy correspondence remains subject to request handling and applicable retention requirements. Backups may retain deleted data until their ordinary rotation; any restoration must reapply completed erasure decisions before using the restored data.

Retention periods vary by data type. For example, active server configuration may remain while the bot is installed or the account is active; logs and diagnostic records may be kept for shorter operational windows; billing and tax records may be kept for legally required periods; and backups may persist until they rotate out of backup systems.

Transient message caches, including Snipe snapshots in servers where Snipe is enabled, expire automatically and are not stored as durable message history. Disabling Snipe immediately prevents retrieval and stops new Snipe snapshots; any inaccessible snapshot already in the cache expires within its existing cache period.

When information is no longer needed, we delete, anonymize, aggregate, or isolate it in accordance with our operational and legal requirements.

8. Security

We use reasonable technical, organizational, and administrative safeguards designed to protect information against unauthorized access, loss, misuse, alteration, or disclosure. No system is perfectly secure, and we cannot guarantee absolute security.

You are responsible for protecting your Discord account, dashboard session, server permissions, bot permissions, and access to any device or account you use with Discortics.

9. International Processing

Discortics and its providers may process information in countries other than your own. Where required, we use appropriate safeguards for international transfers.

10. Your Rights and Choices

Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, objection, withdrawal of consent, or information about how your personal data is used. You may also have the right to complain to a data protection authority.

Use /privacy, ;privacy, the signed-in Delete my data flow, or info@vexvo.io for removal requests. For access, correction, portability, restriction, objection or withdrawal of consent, email us. We respond without undue delay and, for applicable GDPR requests, within one month of receipt. If complexity or volume permits an extension of up to two further months, we notify you within the first month with the reason. Requests are normally free; any lawful refusal or fee will be explained.

See GDPR rights and request handling. We may need to verify your identity and authority before responding. Some information may be retained where required or permitted for security, legal compliance, billing, dispute resolution, backups, fraud prevention, or continued operation of the Services.

Server administrators can remove the bot from a server, disable features, change settings, or request deletion of server configuration where applicable. You do not need server-management permissions to request handling of your own personal data. Server administrators may need to handle copies they independently control, such as their own moderation messages; this does not prevent you from contacting Discortics about records we control.

11. Children's Privacy

Discortics is not intended for children under 13, and we do not knowingly collect personal information from children under 13. Users must also comply with Discord's minimum age requirements and any higher age requirement that applies in their country. If you believe a child has provided personal information to Discortics, contact us so we can review and take appropriate action.

12. Third-Party Links and Services

The Services may link to third-party websites, Discord servers, documentation, payment pages, or support tools. We are not responsible for the privacy practices, content, or security of third parties.

13. Changes to This Policy

We may update this Privacy Policy from time to time. The updated version will be posted on this page with a new "Last updated" date. A policy update does not remove your rights or substitute for consent where consent is required.

14. Contact Us

For privacy questions, requests, or complaints, contact us at info@vexvo.io or through our Discord support server at https://discord.gg/buHBCtE.

Server-local verification enforcement evidence

Advanced verification keeps server-local membership and departure evidence linked to existing verification records to apply account-switch rules. Departure evidence expires after at most 365 days. Successful verification history remains during participating membership, then expires after 365 days of departure or confirmed inactivity; it is also removed when the associated global verification record is deleted. Current ban status is checked through Discord and only cached briefly. Approved data-removal review includes membership records. Staff receive rejection reasons, never raw network addresses, browser/device observations or stored matching values.

With alt checks disabled, successful server-local verification history contains account/server IDs and timestamps without new matching signals, and expires after at most 365 days.