Privacy policy

This policy describes the personal data processed by Rankserveurs, why it is processed, how long it is kept and how to exercise your rights. It reflects how the service actually works.

Data controller

• The controller is Rankserveurs, whose identity and contact details are given in the legal notice.
• For personal data matters, the contact point is the site's Contact page.
• No data protection officer has been appointed to date.

Principles

• No data is sold or used for targeted advertising.
• No advertising cookies are set. Google Analytics audience measurement cookies are only set with the visitor's consent (see the Cookies page).
• IP addresses are never stored in clear. When used to limit abuse or deduplicate a measurement, only a keyed fingerprint (salted HMAC) is used.
• Only the data each feature needs is collected.

Data processed, purposes and retention

Account

• The data processed is the email address, the password (hashed by the authentication service, never readable by the team), the display name, the public username, the avatar, the language, display preferences (theme, media playback) and the creation and update dates.
• The purposes are account creation, sign-in, email verification, password recovery and member features (votes, reviews, favorites, collections, saved searches, followed servers, owner space).
• The legal basis is performance of the terms of use.
• This data is kept as long as the account exists. A deletion request is carried out 24 hours after it is made (cancellation window). Published reviews are then kept without any link to the account and shown as "Deleted account", while favorites, collections, searches, follows, notifications, email preferences and consent records are deleted.
• Signing in with Google, Discord or Apple transmits the account identifier, its email address (verified by the service) and, depending on the service, the name and avatar. With Apple, the address may be a relay address provided by Apple. Rankserveurs never receives the password of these accounts. These services handle the sign-in under their own privacy policies.

Votes

• The data processed is the voting account, the server, the vote date, an IP address fingerprint (salted, truncated HMAC), an anonymous technical browser fingerprint and the in-game name, if entered to receive a reward.
• The purposes are counting votes, enforcing the delay between two votes, detecting and cancelling fraudulent votes and delivering vote rewards to the server concerned.
• If the server has enabled vote rewards, it is a specific recipient. The in-game name and vote time are then sent to the technical address declared by that server.
• To show the character's head on the vote page of a Minecraft Java server, the entered in-game name is sent by Rankserveurs to Mojang (public Minecraft profile service), without the visitor's IP address.
• The legal basis is legitimate interest (ranking reliability) and performance of the terms of use.
• The details of each vote (voting account, IP and browser fingerprints, in-game name) are deleted after 90 days. Only the number of votes the server receives each day is kept, with no link to voters.

Reviews, replies and reports

• The data processed is the rating, text, date and author account (public display name). For a report, it is the targeted content, reason, details, author account and decision.
• The purposes are publishing player reviews, letting teams reply, moderation and handling reports of illegal or rule-breaking content.
• The legal bases are performance of the terms of use, legitimate interest (moderation) and the legal obligations of content hosts.
• This data is kept as long as the review is published, and moderation decisions are logged. The public moderation log contains no personal data.

Server listings, teams and claims

• The data processed is information published by owners (public by nature), team members and their roles, invitations (invited email address) and listing claim evidence (DNS record or verification file).
• The purposes are publishing and managing listings, team collaboration and verifying control of a server.
• Processed invitations are deleted after 90 days, unverified claims expire after 7 days and listings are kept while they exist.

Uploaded media

• The data processed is files uploaded by owners (images, videos), technical metadata (dimensions, duration, checksum) and the rights statement for the media.
• The purposes are processing (formats, cropping), moderation and display on the listing.
• Originals are kept in private storage while the media is published or pending, then 30 days after being replaced or removed. Public versions are deleted once no listing uses them.

Cookieless audience measurement

• The data processed is listing-related events (impression, page view, click to the server's website or Discord, address copy, click on "Join" or "Vote"), linked to a session fingerprint computed server-side from the IP address, the browser and the current date, with a secret key (HMAC). The fingerprint changes every day, the IP address is not stored and no cookie or identifier is stored on the device.
• The purposes are aggregated statistics for owners and for running the directory (the same event is counted once per 30-minute window).
• The legal basis is legitimate interest.
• Raw events are kept 35 days, and aggregated daily statistics, without fingerprints, 25 months.
• The site also uses Vercel Web Analytics, provided by the host Vercel, to count visits to public pages (address without parameters, referrer, country, device and browser type). No cookie or identifier is stored on the device, private areas are not measured and statistics are aggregated.

Audience measurement with Google Analytics (with the visitor's consent)

• The data processed is the pages viewed, where the visit comes from (search engine, link, direct access), the device and browser type, the language, an approximate location inferred by Google, and a random identifier stored in a cookie.
• The purpose is to measure site traffic and improve its content. There is no advertising and no cross-site tracking, and Google signals are turned off.
• The legal basis is consent, asked before anything is stored and withdrawable at any time with the “Manage cookies” link at the bottom of every page.
• Data is kept for 14 months at most in Google Analytics, and cookies last 13 months at most.

Emails

• The data processed is the email address, email type, delivery status, provider message identifier, deliverability events (delivered, bounce, complaint, unsubscribe), email preferences (alerts, newsletter) and consent records (date, source, version).
• The purposes are sending account and listing emails (transactional), alerts for followed servers (on request) and the newsletter (only after double opt-in confirmation), and honouring unsubscribes.
• The legal bases are performance of the terms of use (transactional emails) and consent (alerts, newsletter).
• The send log and provider events are kept 90 days, and consent records until the account is deleted. The list of addresses that must not be contacted again is kept to honour that refusal, including after account deletion.
• Sign-in emails (verification, forgotten password) are sent by the authentication service through the same provider.

Payments

• The data processed is the Stripe customer identifier, Podium and Sponsored campaigns (dates, amount), balance top-ups and invoices (amounts, status, links to Stripe documents).
• Rankserveurs never receives or stores card numbers, as payment details are entered on Stripe's pages.
• The purposes are selling the Podium and Sponsored offers, invoicing, refunds and payment fraud prevention.
• The legal bases are performance of the contract and accounting and tax obligations.
• Accounting records are kept for the legal period (10 years in France).

Contact form

• The data processed is the name (optional), email address, subject, message, language, and the account identifier if the sender is signed in.
• The purpose is answering the request.
• The legal basis is legitimate interest.
• This data is kept 90 days in the send log, then for as long as needed to handle the request in the team's mailbox.

Security and abuse prevention

• The data processed is IP fingerprints or account identifiers in rate-limiting counters, the audit log of sensitive actions (moderation, administration, listing identity changes) and the Cloudflare Turnstile bot check on some forms.
• The legal basis is legitimate interest (service security).
• Rate-limit counters are kept 1 day, the audit log 2 years, read notifications 90 days and completed technical jobs 30 days.

Game server measurements

Rankserveurs queries listed servers to learn their player count and Discord activity. Player names that some protocols return are not stored. Only counts are kept (samples 14 days, hourly aggregates 90 days, daily aggregates 2 years).

Recipients and processors

Server owners only receive aggregated statistics about their listing (never visitors' identities) and, if vote rewards are enabled, the in-game name entered when voting.

Fonts are served by the site itself. The browser sends no request to a third-party font service.

Your rights

Everyone has the right to access, rectify, erase, restrict, object to and port their data, and to set instructions for what happens to it after their death. A signed-in account can export its data (JSON format) and request account deletion from its "My data" page. Other requests can be sent via the Contact page. An answer is given within one month.

If there is a problem, a complaint can be lodged with the CNIL, the French data protection authority (www.cnil.fr).

Security

Encrypted connections (HTTPS), access control on every database row, secrets kept outside the code, media originals in private storage, logging of sensitive actions, daily database backups (14 days, plus a monthly backup kept 6 months, currently being set up).

Minors

An account can be created from the age of 15. Below that age, the consent of a parent or legal guardian is required, in line with French data protection law. A parent can ask for a minor's account to be deleted via the Contact page.

Changes

This policy may change as the service evolves. The date of the last update is shown at the top of the page.