Controller and contact
The controller is Luca Cataldo (MCVote), c/o Autorenglück #69236, Albert-Einstein-Str. 47, 02977 Hoyerswerda, Germany. Contact [email protected] for privacy requests, access or erasure. Full provider details are available in the legal notice.
Website access and delivery
Requests involve your IP address and connection and request data needed to deliver the website. Our CDN and security provider Cloudflare receives the full IP address, requested URL and technical browser information. We do not promise truncation before transmission. Application request logs record the HTTP status. Processing serves availability, troubleshooting and attack prevention under Art. 6(1)(f) GDPR. Hosting and CDN providers receive data required for these tasks.
Discord login and accounts
Public server lists can be viewed without an account. Account functions use Discord OAuth with the identify permission. We receive Discord ID, username and avatar information and link them to an internal user ID. We do not receive your Discord password. New logins do not request email, guild list or guild joining permissions. The legal basis for login and account functions is Art. 6(1)(b) GDPR. Discord processes the login you initiate under its own privacy policy.
Server profiles, claims and reviews
Server submissions, management and claims involve the supplied server data, content and images, account links, claim method, messages, processing status and edit history. Reviews contain a user association, rating, text and timestamps. Published profiles and reviews are public and may be distributed by search engines, APIs and embedded widgets. Private claim messages and moderation notes support internal processing. Requested functions rely on Art. 6(1)(b) GDPR; moderation and protection against abuse rely on Art. 6(1)(f), in our interest in reliable listings and preventing unauthorised claims and manipulation.
Votes and abuse prevention
Votes store the server, Minecraft player name, time, hashes of the IP address and User-Agent, an internal user ID where applicable and a widget referral tag. Rejected attempts may also be logged with decisions, reasons and timing. This supports daily limits, fraud detection, rankings and voting streaks. The legal basis is Art. 6(1)(f) GDPR, our interest in a fair, working voting service. These hashes and account-linked records are pseudonymous data, not anonymous counters. Player names, IP hashes and User-Agent hashes in votes are cleared after 30 days by an hourly cleanup. Anti-abuse audit records are deleted after 30 days; expired sessions are also removed hourly. Vote time, server and any internal account association remain for rankings, totals and your voting streak. This association remains personal data, not anonymous data. Request account and association erasure at [email protected]. Account, claim, review and report retention depends on use and handling; fixed automatic erasure periods are not currently implemented for these categories.
Reports and correspondence
We process email and report contents to respond and investigate errors and security problems. The report form sends category, title, description and optional contact information to the AgentIQCode Issues system (agentiqcode.com), accessible to the team handling reports. Do not send passwords or access keys. Contract-related enquiries rely on Art. 6(1)(b) GDPR; other correspondence and security reports rely on Art. 6(1)(f). Storage depends on handling the report and any resulting project task; no fixed automatic erasure period is currently implemented.
Cookies, device storage and reminders
Login uses mcvote_session for 30 days from sign-in; signing out removes the cookie. Admin verification uses mcvote_admin_ok for ten minutes. Necessary cookies rely on § 25(2)(2) TDDDG, with subsequent processing under Art. 6(1)(b) or (f) GDPR. An explicitly chosen theme is stored as mcvote-theme. Optional reminders use mcvote_reminder, mcvote_reminder_last and browser notifications. Once enabled, they periodically request the leaderboard from our server. Consent is the basis under § 25(1) TDDDG and Art. 6(1)(a) GDPR. Disable reminders in privacy settings or the dashboard and revoke browser notification permission at any time. Local preferences remain until changed or site storage is cleared. Cloudflare may use necessary security cookies depending on the security challenge.
Advertising and consent
Google AdSense is currently disabled in the application. We do not load AdSense scripts, ad frames or preparatory connections to Google advertising services. Reactivation requires suitable consent controls using a certified CMP and updated information about recipients, purposes, data, retention and international transfers. Necessary login cookies do not constitute advertising consent.
Recipients and international transfers
Recipients include people operating the service and handling requests, and hosting, CDN, login and reporting providers for the purposes described above. Cloudflare and Discord may process data outside the EEA, including the USA. Transfers require the conditions in Arts. 44 et seq. GDPR, such as an applicable adequacy decision or appropriate safeguards including EU standard contractual clauses. We do not claim all data remains in the EU. Ask our privacy contact for information and copies of applicable safeguards. Embedding an MCVote widget on another website establishes a connection to MCVote. We and our CDN receive technical request data as for a direct visit. Public widgets do not themselves set cookies or load ads. Website operators must account for this embedding in their own privacy notices.
Retention and erasure
Server status history is pruned after 365 days. Sessions expire after 30 days; expiry does not itself mean all database records are immediately erased. Current backups run every five minutes and retain the latest 24 snapshots, approximately two hours during regular operation. Deleted records may remain in backups until rotation. Accounts, profiles, claims and reviews are retained to provide and administer the relevant function. Player names, IP hashes and User-Agent hashes in votes are cleared after 30 days by an hourly cleanup. Anti-abuse audit records are deleted after 30 days; expired sessions are also removed hourly. Vote time, server and any internal account association remain for rankings, totals and your voting streak. This association remains personal data, not anonymous data. Request account and association erasure at [email protected]. Account, claim, review and report retention depends on use and handling; fixed automatic erasure periods are not currently implemented for these categories.
Your rights
Subject to legal conditions, you have rights of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18) and portability (Art. 20 GDPR). You may object to legitimate-interest processing on grounds relating to your particular situation (Art. 21). Consent may be withdrawn at any time for the future without affecting the lawfulness of earlier processing. Contact [email protected]. We normally respond within one month of receiving a request and notify you of any legally permitted extension.
Complaints, optional information and automated checks
You may complain to a supervisory authority, particularly where you live, work or believe an infringement occurred. The authority at the controller's location is the Saxon Data Protection and Transparency Commissioner. There is no general legal obligation to create an account or submit content. Features require their relevant inputs; report contact details and reminders are optional. Automated limits and abuse checks may reject votes. These are not intended as solely automated decisions with legal or similarly significant effects under Art. 22 GDPR.
[email protected] · Imprint · Sächsische Datenschutz- und Transparenzbeauftragte