Privacy Policy

Browsing needs no account. MCRank's own database does not store your IP address or your search text. MCRank's servers do read your network address and browser details while they handle a request, to build the one-way daily code described below and the abuse-prevention counters, and they do not keep them. The services that deliver the site, Vercel and, where its network service is switched on for the site, Cloudflare, handle network addresses as part of delivering it and may keep their own logs under their own policies, which MCRank does not control.

A resource's description can show pictures that its creator hosts on their own server. When such a page opens, your browser asks that server for each picture, so that server can see your network address and browser details, as it would if you opened the creator's own page. MCRank asks your browser not to tell that server which page you came from, and MCRank does not control or receive anything those servers keep.

When a resource is shown or clicked, MCRank records that event with a coarse page and browser class and a one-way keyed code that changes every day. The code only lets MCRank avoid counting the same visit twice; the address and browser details used to make it are not stored and the code cannot follow you from one day to the next. Automated visitors are excluded from these counts.

Some results are Featured: promotional placements that creators pay for on their own approved resource (see How Featured works and the Advertising Policy). To choose which Featured resources to show, MCRank uses the page you are on and, if you searched, the words you typed to decide which pages and resources match. Those words are not stored, and they are not shared with the creators who pay for Featured placement.

When a Featured card is shown or clicked MCRank records the event exactly as it does for any other resource: a coarse page and browser class and the daily one-way keyed code described above, so that placements can be counted without identifying anyone. MCRank sets no advertising cookies and gives advertisers no personal data.

This policy describes how data is handled. It does not replace the plain explanation of paid placements on How Featured works and in the Advertising Policy, and nothing in it limits any right you have under consumer, advertising or data-protection law.

• Your email address, used to send confirmation, sign-in and password-reset emails and to contact you about your account and resources.
• Your password, if you set one: you type it into MCRank, whose server passes it to Supabase Auth, which stores only a hashed form. MCRank does not store, log or display it.
• A record that your account accepted the Terms of Service and the Privacy Policy: which version of each, and when.
• Sign-in records kept by Supabase Auth, MCRank's sign-in provider: when you sign in it records the network address and browser details of the session and of sign-in events, to protect accounts and investigate abuse. MCRank has not yet documented how long Supabase keeps these records.
• If you link Discord: your Discord account identifier and whether you have joined the MCRank Discord server.
• The resources you submit: their text, destination, price, images (location and camera data is removed from uploads) and the ownership tokens and check results used to verify them.
• Reports you make: the reason and any note. Reports are visible only to MCRank's reviewers.
• Featured purchases, where paid placement is available: the resource, dates, amounts and currency, and PayPal's order and payment identifiers. Card and bank details are entered with PayPal and never reach MCRank.
• A record of moderation decisions about your resources and who made them.

When you paste a link to import, MCRank's server reads that public page, or the public programming interface of Modrinth, Hangar or GitHub, and keeps a private copy of what it read and any images for up to 24 hours, or until you save or discard the import. MCRank sends no cookies or credentials when it does this.

To stop abuse, MCRank limits how often some actions can be repeated. It does this with a one-way keyed code of your account or network address, held for at most a day, not the address itself.

MCRank sets only the cookies needed to sign you in and keep you signed in, and a temporary one while a Discord connection is being completed. It sets no advertising or tracking cookies.

• Supabase: database, sign-in (account and session records, including the network address and browser details of your sign-in sessions) and file storage.
• Resend: delivers the confirmation, sign-in and password-reset emails that Supabase Auth sends for MCRank, so it handles your email address and those messages.
• Vercel: hosting. It handles network addresses and request logs as part of delivering the site.
• Cloudflare: DNS and, where its network service is switched on for the site, network and security services.
• PayPal: payments for Featured placement, where paid placement is available.
• Discord: only if you choose to link or sign in with it.

MCRank has not yet published the regions where its database, files and hosting run, or the safeguards used when data is processed outside your country, and some of the providers above may process data outside your country.

• Visit events: 90 days, then deleted.
• Abuse-prevention counters: no longer than a day.
• Sign-in records held by Supabase Auth: MCRank has not yet documented how long they are kept.
• The record that your account accepted the Terms and Privacy Policy: for as long as the account exists.
• Imports: 24 hours unless you save them.
• Account, resources, reports, payments and moderation history: for as long as they are needed to run MCRank, to keep an accurate record of decisions and payments, and to meet obligations. A fixed period for reports has not been decided.

You can edit or archive your own resources from your account. To ask for a copy of your data, a correction or deletion, or to ask a question about this policy, use the Contact page. Requests are handled by a person.