Responsible party and contact
MCIdentity operates this website and determines how its operational data is processed. Privacy questions can be sent to [email protected] or submitted through Privacy Request. Operator identity and postal details should be completed before commercial launch.
Minecraft profile data
MCIdentity processes public usernames, UUIDs, skins, skin models, capes, provider responses and observation timestamps. This is separate from visitor data and does not provide access to account passwords, email addresses or private Microsoft account records.
MCIdentity observations
For a stable UUID, MCIdentity may record the current username, first and last observation, provider and an uncertainty window when a change is detected. Earlier names can be incomplete. A verified privacy request may hide a previous name from public display while retaining a restricted audit record.
Searches and public visibility
Search input is processed to return the requested profile and may contribute to aggregate counters. MCIdentity does not publish individual visitor searches or a public recent-search feed.
Technical logs and IP addresses
Hosting infrastructure can process route, timestamp, response status, browser information and network address for delivery and security. Rate-limit identifiers are one-way hashed with a daily rotation. Application logs avoid full IP addresses and submitted search terms. Hosting-level log retention depends on the configured provider and should be kept to the shortest operational period.
Caching and retention
Fresh profile cache entries normally last 15 minutes; stale outage fallbacks can last up to 24 hours. Texture responses are cached for performance. Name observations and verified privacy-case records can be retained longer because they provide the history and audit trail users request.
External providers and international processing
Public profile and session requests are sent server-side to Mojang services. Hosting, network and provider infrastructure may process data in other countries under their own safeguards and policies. Browser texture requests remain on MCIdentity endpoints.
Correction, hiding and deletion requests
You can ask to correct an inaccurate observation, hide a previous username, report personal information or request deletion of visitor-related data. Requests are reviewed and may require proportionate verification. An anonymous request does not automatically hide a current public provider name.
Security measures
MCIdentity uses server-side validation, prepared database statements, CSRF protection, restricted provider hosts, security headers, rate limiting, non-public configuration and output escaping. No internet service can promise absolute security.
Policy changes and contact
This notice may change as the platform develops. Material revisions should update the published date and consent version where appropriate. Contact: [email protected].