Privacy Policy
| Category | Data Point | Storage |
|---|---|---|
| Account Identifiers | Discord Snowflake User ID — treated as PII. Associated with preferences, premium status, and admin permissions. | Encrypted |
| Command Metadata | Which command was executed, timestamp, and the server it was used in. Message content is not stored. | Anonymised |
| Dashboard Telemetry | Standard web server logs: IP address, browser type, referring URLs. Used for DDoS mitigation. Standard IPs deleted within 24 hours. | Encrypted |
| Server Configuration | Guild ID, channel IDs, role IDs, and all feature configurations you set up in the dashboard. | Encrypted |
| IP Verification Data | IP address (with consent only), threat intelligence, verification outcome. See Section 07 for full details. | Encrypted |
| Ticket & Support Data | When the ticket system is used: Discord User IDs of ticket participants, message content and attachments within ticket channels (stored as HTML and web transcripts), staff notes added by moderators, ticket metadata (category, timestamps, assigned staff, priority, tags), and optional satisfaction ratings (1–5 stars) submitted by ticket owners. | Encrypted |
| Staff Application Data | When a server's staff application system is used: Discord User IDs of applicants, application question responses, decision records (accepted/rejected), and timestamps. Stored per-guild and accessible to that guild's administrators only. | Encrypted |
Feature Delivery
Maintaining welcome messages, automated moderation rules, and all feature configurations.
Abuse Prevention
Identifying bot raids, users attempting to crash the bot, circumventing bans through alt accounts, and operating the IP Verification security feature.
Internal Analytics
Aggregating anonymised usage data to identify underutilised features. Individual usage is never sold or used for advertising.
Legal Compliance
Responding to verified legal requests or Discord Trust & Safety inquiries regarding Terms of Service violations.
| Provider Type | Purpose | Data Shared |
|---|---|---|
| Infrastructure (Cloud) | Database hosting and compute | All encrypted records |
| Payment Processors | Premium billing | Email, billing details only |
| Error Tracking | Debugging and crash reporting | System logs, stack traces (no PII) |
| IP Intelligence API | IP Verification threat analysis — VPN, proxy, Tor, hosting, risk scoring, and geolocation. Only called when a user initiates IP Verification. | IP address (per-verification, with user consent) |
AES-256 Encryption at Rest
All sensitive data including IP addresses, User IDs, and verification records are encrypted at rest using AES-256.
HMAC-Based Lookups
User IDs and IP addresses used for deduplication are stored as HMAC hashes — one-way transforms that cannot be reversed.
Least-Privilege Access
Strict internal access controls. Only the minimum required team members have access to production data, and all access is audited.
Isolated VPC Environments
Database and compute infrastructure is isolated in private VPCs not exposed to the public internet.
Server Removal (30 Days)
If a server removes the bot, all configurations and associated logs are queued for deletion, processed every 30 days to prevent data loss from accidental bot kicks.
On-Request Erasure
Exercise your right to erasure by contacting support@rankcore.org or using the /privacy delete command in Discord. Production data is removed immediately.
IP Verification Record Retention
IP Verification records are retained for as long as the server's configuration is active, or until manually deleted by the server administrator or upon a user erasure request. Records deleted by an administrator are immediately removed from production.
Backup Persistence (90 Days)
While data is removed from production immediately following an erasure request, it may persist in encrypted off-site backups for up to 90 days before being completely overwritten.
Essential Cookies
Session cookies required for Discord OAuth2 authentication and dashboard functionality. These cannot be disabled without breaking login.
Functional Cookies
Used to remember UI theme preferences and dashboard settings. Stored in localStorage — not transmitted to our servers.
Consent Record
A consent flag is stored in localStorage to track whether you have acknowledged these terms. It contains no PII and is never transmitted to our servers.
Data Collected
| Data Point | Purpose | Storage Method |
|---|---|---|
| IP Address | Core identifier for all checks | AES-256 encrypted + HMAC for lookups |
| VPN / Proxy Detection | Enforce server's VPN/proxy block policy | Boolean flags, encrypted |
| Tor Exit Node Detection | Enforce server's Tor block policy | Boolean flag, encrypted |
| Hosting IP Detection | Block datacenter/bot traffic | Boolean flag, encrypted |
| Risk Score (0–100) | Graduated threat assessment | Integer, encrypted |
| Country & City | Geographic allow/block policy enforcement | String, encrypted |
| ISP / Provider Name | Logged for administrator review | String, encrypted |
| Discord User ID | Link verification record to a user | HMAC hash + AES-256 encrypted copy |
| Guild (Server) ID | Scope record to the verifying server | HMAC hash + AES-256 encrypted copy |
| Verification Outcome | PASSED / BLOCKED / FLAGGED status | Plaintext enum in record |
| Flag Reasons | Detailed reasons for block/flag | Array, plaintext in record |
| Timestamp | Verification date and time | ISO-8601 datetime |
What Administrators Can See
Server administrators can view verification records via the RankCore dashboard. The IP address displayed to administrators is always masked as [hidden] — they cannot see your actual IP. They can see: verification outcome, flag reasons, country, risk score, ISP, VPN/proxy flags, and your Discord User ID. They can delete any record, manually approve a blocked user, or manually ban them.
Anti-Bypass Technical Guarantees
- The verification token is 48 cryptographically random bytes, stored as SHA-256 hash only — never in plaintext.
- Each token is strictly one-use. It is burned (marked used) the moment your POST request is received.
- Tokens have a server-configured TTL of 5–30 minutes. Expired tokens are deleted from the database.
- The token is bound to your specific Discord User ID and Guild ID — it cannot be used by a different person.
- Rate limiting: a maximum of 3 active tokens per user per guild per TTL window.
- Your IP address is captured entirely server-side — it cannot be faked or spoofed by the client.
Your Consent Rights
IP Verification always requires your explicit consent via a checkbox on the verification gate page. Consent is validated server-side — the system will not process your IP without it. You may withdraw participation by not completing the verification flow, though this may restrict your access to the server per the administrator's configuration.
Erasure of Verification Records
You may request deletion of your IP Verification record at any time by contacting the server administrator, who has a per-record delete function in the dashboard, or by contacting RankCore support at support@rankcore.org with your Discord User ID and the server name. Records deleted from production are removed immediately; backup copies are purged within 90 days.
What is Collected Per Ticket
| Data Point | Purpose | Storage |
|---|---|---|
| Discord User IDs (owner & participants) | Track who created and participated in the ticket | Plaintext in ticket record |
| Username / display tag at creation | Human-readable reference in transcript header | Plaintext in ticket record |
| Message content & attachments | Full conversation stored as HTML transcript and/or web transcript — viewable by server admins | HTML file (per-ticket) + encrypted DB record |
| Ticket metadata | Category, open/close timestamps, priority level, tags, assigned staff ID, claimed staff ID | Encrypted DB record |
| Staff notes | Internal notes added by moderators — visible only within the ticket channel to staff | Encrypted DB record |
| Satisfaction rating (1–5 stars) | Optional post-close rating submitted by the ticket owner via DM button | Integer in ticket record |
| Intake question responses | Answers provided by the user when opening a ticket (if configured by the server) | Encrypted DB record |
| Close reason | Text reason provided by staff or owner when closing the ticket | Plaintext in transcript & log record |
Who Can Access Ticket Data
Server administrators and users with the configured ticket handler role can view all open and closed ticket records via the RankCore dashboard, including transcripts. RankCore developers may access ticket records only for the purposes of security investigations, bug fixes, or when responding to a legal request. Ticket data is never shared with third parties beyond what is described in Section 03 (infrastructure providers).
Transcript Retention
HTML transcript files and web transcript records are retained as long as the server's bot configuration is active. When a server removes the bot, all ticket records — including transcripts — are queued for deletion within 30 days. Individual ticket records can be deleted at any time by a server administrator via the dashboard. Users may request deletion of their participation data (including message content from transcripts) by contacting support@rankcore.org with their Discord User ID and server name.
Important Notice: Message Content
We do not knowingly collect data from children under 13. If we discover such data has been collected, we will take immediate steps to delete it in full, including any IP Verification records. Parents or guardians may contact us at support@rankcore.org to request deletion.
Right of Access
Request a copy of all personal data we hold about you, including any IP Verification records.
Right to Rectification
Request correction of inaccurate personal data we hold about you.
Right to Erasure
Request deletion of your personal data, including all IP Verification records. Contact support or use /privacy delete.
Right to Portability
Request an export of your data in a machine-readable format. Server admins may export IP Verification records as CSV.
To exercise any GDPR right, contact our Data Protection Officer via the official support server or at support@rankcore.org. Legal basis for processing IP Verification data is legitimate interests (server security) combined with your explicit consent, which you may withdraw at any time.
California residents have the right to: know what personal information we collect (including IP Verification data), request deletion of that information, and opt out of the "sale" of personal information. We do not sell your personal information.
To exercise CCPA rights, submit a request via our support email. Requests are fulfilled within 45 days. IP Verification records are included in the scope of any California privacy request.
We reserve the right to update this policy at any time. If significant changes are made — such as new data collection categories or changes to IP Verification data practices — we will provide notice via our official Announcements channel in the support server. Your continued use of the bot after changes constitutes acceptance of the revised terms.
Email — support@rankcore.org
For data access requests, erasure requests (including IP Verification record deletion), GDPR/CCPA enquiries, and all privacy-related questions.
Support Server
Primary channel for real-time support. Our legal and support team can assist with any privacy concerns via the official Discord support server.