Privacy & data handling
MCProfiles is a lookup tool for public Minecraft profile data. This page explains what we access, what we store, how limited ads and consent controls work, and how you can request changes.
Privacy-first by design
MCProfiles only fetches data when someone runs a lookup. We do not passively crawl servers or index skins from single-player sessions. Every response shows where data came from and how fresh it is.
Google ads and Google Analytics are opt-in at the deployment level and stay off unless Google consent tooling is also explicitly enabled. MCProfiles Plus stays ad-free, and privacy, billing, claim, and embed flows stay clean.
When Google integrations are enabled, they stay separate from player profile data. We use them to understand product usage, not to enrich individual Minecraft identities.
What we never do
No bulk skin harvesting, no stalking leaderboards, and no reselling of player lists. We don't buy third-party "historical name" dumps, and any external public-site discoveries are manually reviewed and live-verified before they are promoted into our archive.
Data minimization
Short-lived caches, aggregate analytics without storing IPs in the database, and suppression workflows when you ask us to stop retaining profile rows. When Google Analytics or ads are enabled together with Google consent tooling, Google may use cookies or local storage to remember consent choices, measure usage, serve ads, and measure them, but MCProfiles does not merge that Google-side data into player profiles.
Young players & GDPR-minded families
Minecraft skews young. We avoid dark patterns, keep explanations readable, and provide a clear path to ask questions or request data handling changes. This isn't legal advice — see our practices below and contact us if you need specific assurances for your region. If ads are active, we prefer lower interruption formats over aggressive overlays.
What data we access
- Public Minecraft usernames and UUIDs
- Public skin and cape textures associated with a profile
- Optional cape enrichment (for widely-used community capes)
- Optional verified Bedrock gamertag links for players who have publicly opted in
- Public server status — MOTD, version, and player counts
Sensitive names & identity
If you change your Minecraft username, some sites may still show older names from historical caches. MCProfiles does not import legacy username history. The only timeline we may show is from changes we observe after a profile is looked up on MCProfiles — forward-looking, not a full lifetime record.
If past usernames are sensitive for you, treat any public Minecraft username history tool with caution — and use the suppression request below to have your data removed from our systems.
What we show and how
Authoritative data (username, UUID, skin, cape, model type) comes from the official Minecraft source and is labeled with a verification timestamp and source badge.
Derived data (3D previews and avatar renders) is generated from those official textures.
Enrichment data (community capes, verified Bedrock linking) is optional, clearly labeled, and never required for the main profile view.
We do not display full historical name records. We only surface username changes we directly observe going forward, not imported legacy data.
What we store
- Profile data we've looked up (username, UUID, skin/cape references) so pages load quickly and we can track changes going forward
- Server status snapshots for the servers that have been looked up
- Non-identifying first-party usage analytics (type of lookup and timestamp only — we do not store IP addresses in our database)
- Google Analytics measurement data such as page views and engagement events when analytics is enabled
- Short-lived caches to keep pages fast; cache state is clearly shown in the UI
Ads, consent, and Plus
When Google Analytics is explicitly enabled for a production deployment and Google consent tooling is also enabled, we use it to understand which pages are used and where people drop off. Google may use cookies or similar browser-side storage for measurement depending on region and browser settings.
When ads are explicitly enabled on MCProfiles and Google consent tooling is also enabled, we use Google AdSense. Google may use cookies, local storage, and similar browser-side technologies to serve ads, limit frequency, measure performance, and remember privacy choices.
We do not assume Google consent tooling is active by default. If we enable Google's consent messaging for a region, Google may present the relevant consent or opt-out flow before its ad or measurement products are allowed to run there. If that tooling is not configured for a deployment, we keep the related Google integrations turned off rather than claiming consent coverage we have not actually enabled.
MCProfiles Plus stays ad-free. We also keep privacy, billing, claim, and embed flows clean so support and trust-sensitive actions are not wrapped in ad placements.
Publisher-content boundaries
MCProfiles separates usable lookup pages from pages that are eligible for Google publisher scripts. Curated pages such as guides, docs, capes, skins, server discovery, username tools, and this privacy page explain the site's methods and limits in crawlable text.
Generated profile, server, skin, tag, embed, claim, billing, account, support, and API screens are kept out of ad eligibility during review so ads are not placed on low-context, automated, or trust-sensitive surfaces.
Suppression & correction requests
If you want your profile data removed from our database, or if you see incorrect information, submit a request below. We review these seriously and will respond within a reasonable timeframe.