Information collected by this website
You can browse public HistoriaMC pages without signing in or directly providing payment information. When you visit, Vercel Web Analytics may process aggregate traffic information such as the page visited, approximate region, referring page, device type, operating system, and browser.
Vercel states that its Web Analytics service stores anonymized visitor data and does not use cookies for visitor analytics.
Website accounts and connected sign-in
If you choose to sign in, HistoriaMC uses Discord OAuth through Supabase. The account system processes a Discord account identifier and may store the display name and avatar supplied by Discord. Supabase processes authentication information and sets the session cookies needed to keep you signed in.
HistoriaMC uses this information to identify your website account, show your connected identity, protect account-only tools, and associate permitted actions with the correct player.
A signed-in player receives a public handle, may edit their display name, and uses their Discord avatar. These fields are publicly readable on profile pages and when used for blog authorship. Website roles are assigned directly by HistoriaMC administrators.
Development-post reactions and responses
Signed-in players may react to development posts or publish responses and replies. HistoriaMC stores the selected reaction, response text, associated post, account identifier, parent response when applicable, and creation, editing, or deletion timestamps.
Published responses appear with the player's public display name, Discord avatar, and a link to their public profile. When a response with replies is deleted, its text and author may be removed while a deletion placeholder remains to preserve the conversation. Staff may hide or retain records when reasonably needed for moderation, safety, or abuse prevention.
Linked Minecraft and nation information
You may link a Minecraft account using a short-lived linking code. HistoriaMC stores the linked Minecraft UUID, username, linking timestamps, and the association with your website account.
The Minecraft server may synchronize your nation membership, role, town and town rank, join date, bank balance, held offices, server rank, and territory permissions with the website. The linked Minecraft identity and civic fields may appear on your public profile. Territory permissions are used to determine whether you can view, edit, or publish territory, but are not displayed on public profiles.
Territory claims and editing activity
When authorized players use the claim editor, HistoriaMC stores territory drafts, selected chunk coordinates, version and publication information, notes when supplied, and which account created, updated, or published a change. Published territory may be shared with the Minecraft server and displayed through public map services when those services are available.
Hosting and administrative access
Vercel hosts the website and may process ordinary request and security information needed to deliver it. Supabase provides authentication and database services for accounts, linked identities, content publishing, nation permissions, and territory tools.
Content editors use website sign-in and staff permissions through Supabase. Authentication credentials are handled by the applicable provider and are not exposed as public website content.
Third-party services
Vercel, Supabase, Discord, Minecraft-related services, and other external websites process information under their own terms and privacy policies. Information shared with HistoriaMC staff through Discord is also subject to Discord's policies and account settings.
How information is used
- Operate, secure, and improve the website.
- Understand which public pages are useful to visitors.
- Authenticate website accounts through Discord.
- Display public profiles and development-post authors.
- Publish development-post reactions and responses.
- Enforce approved site roles assigned by administrators.
- Verify and display linked Minecraft identities.
- Synchronize nation roles and territory permissions.
- Save, review, and publish authorized territory changes.
- Diagnose technical failures and abusive traffic.
- Publish documentation and development updates.
HistoriaMC does not sell website visitor information or use the public site to build advertising profiles.
Retention and your choices
Retention depends on the record and the feature it supports. Provider-held authentication, hosting, and analytics information is also governed by the applicable provider settings and policies. HistoriaMC does not promise a single retention period for every type of record.
You can sign out, update your public profile, delete your own development-post responses, or unlink your Minecraft identity from the account page. Deleting a response removes its displayed text, but a placeholder may remain when needed to preserve replies. Unlinking does not necessarily remove territory already published for a nation, server records, or security-related records. Questions about accessing, correcting, or deleting account information can be sent to contact@historiamc.com.
You can use browser privacy controls or content blockers to limit analytics requests. Blocking analytics does not prevent access to public website content, but blocking authentication cookies will prevent signed-in account features from working.
Children's privacy
The public website is not designed to solicit personal information from children. If you believe a child has shared personal information with HistoriaMC staff, email contact@historiamc.com so the concern can be reviewed.
Policy changes and contact
This policy may be updated when the website, server, or providers change. The effective date above will be revised when material updates are published.
Privacy questions and requests can be sent to contact@historiamc.com. You can also review the Terms of Service.