Privacy policy

We are still reviewing and documenting our privacy practices.

1MoreBlock and OMGboards are privately run hobby communities, not a company or commercial service. That does not remove our responsibility to handle member information carefully.

We do not want or ask for unnecessary real-world identifying information. Please do not give us your real name, home address, identification documents, account passwords, authentication codes, or other private information unless there is a genuine reason to contact us about it.

We do not build advertising profiles, sell personal information, or deliberately collect information merely because we can.

Operating a forum, Discord server, and Minecraft server nevertheless creates technical and community records. These may include account identifiers, Minecraft UUIDs, Discord user IDs, IP addresses, messages, commands, gameplay activity, reports, and moderation decisions.

We try to remove information when we no longer need it and periodically purge old accounts, tickets, logs, and backups. Some information must remain for a reasonable period so we can operate and restore the server, investigate cheating or griefing, understand reports, protect the community, and enforce sanctions. Limited ban records may need to remain longer so that permanent sanctions can still be recognized.

This draft explains what we currently understand about those systems. We are still checking exact retention practices, plugins, bots, backups, and third-party services. Where we cannot yet confirm a detail, we will say so instead of making a promise we may not be able to keep.

Last reviewed: Summer 2026

Who operates the community

1MoreBlock and OMGboards are operated as a personal hobby community by:

Community and server owner: Floris Fiedeldij Dop
Privacy contact: mrfloris@gmail.com
Discord: @mrfloris

Our community services are:

Forums: omgboards.com and www.1moreblock.com
Minecraft server: 1MoreBlock.com
Discord server: discord.gg/floris
Rules and policy website: rules.1moreblock.com

Our other contact information is available on the Contact page.

What this policy covers

This draft covers information handled through:

The OMGboards forum
The 1MoreBlock Discord server
The 1MoreBlock Minecraft server
The rules.1moreblock.com website
Community support, reports, appeals, and moderation
Email correspondence
Optional personal gifts sent through services such as PayPal

It covers information that we receive, create, store, review, or use while operating and moderating the community.

Services operated by other providers

Some parts of our community use services that we do not host or control.

Our Discord server is a community space hosted by Discord. Discord operates its accounts, applications, messages, calls, infrastructure, and internal systems.

Microsoft and Mojang operate Minecraft accounts, authentication, launchers, clients, and other Minecraft services. We operate the 1MoreBlock Minecraft server, but we do not operate the Minecraft account system.

GitHub hosts this rules and policy website through GitHub Pages.

Google provides the Gmail service used for community email. PayPal processes personal gifts sent through its service. Other providers may operate hosting, CAPTCHA, anti-spam, Discord bot, or Minecraft-related services.

These providers may process information independently under their own privacy policies. Their handling or retention of information may continue independently of anything 1MoreBlock stores or deletes.

Information handled through the forum

When you use OMGboards, the forum may process:

Your username, display name, email address, IP address, and account identifiers
Optional profile information that you provide
Registration, login, session, browser, and security information
Threads, posts, reactions, attachments, reports, and other submitted content
Private forum conversations and their participants
Moderation actions, warnings, restrictions, and account history
Cookies and preferences needed to keep you logged in and operate the forum
Anti-spam, anti-abuse, and CAPTCHA results

Public posts, attachments, profile information, and other public activity may be visible to members, visitors, and search engines.

Private forum conversations are stored in the forum database. They are private from ordinary visitors, but they are not hidden from the forum’s systems or authorized administrators when access is required for moderation, security, or support.

The forum is not intended for confidential information. Do not submit information that you would not want stored in the forum database or reviewed if it becomes relevant to a report, security incident, or moderation decision.

The forum may send submitted content to anti-spam or abuse-prevention services. The forum also uses hCaptcha to help prevent automated abuse.

We do not intentionally operate a separate forum advertising or visitor-profiling system. The forum software, web server, security systems, and service providers may still create technical logs needed to operate and protect the site.

Forum retention

We do not guarantee that forum accounts will be retained for any particular period.

As part of recent housekeeping, we removed accounts belonging to members who had not participated during the previous two years. Remaining accounts may also be removed as the forum is reduced, cleaned up, or archived.

Removing a forum account and removing all content connected to that account may be separate operations. Posts, attachments, private conversations, technical records, or backup copies may remain until they are separately removed or the relevant backup is purged.

We are still verifying exactly what XenForo preserves when an account is removed. The final policy will explain this more precisely.

Information handled through Discord

When you participate in our Discord server, we and our authorized bots or integrations may handle:

Your Discord username and display name
Your numeric Discord user ID
Your avatar and other server-visible profile information
Server membership, roles, permissions, and join or leave activity
Messages, attachments, reactions, and other content posted in our server
Support tickets, reports, evidence, appeals, and moderation records
Bot commands and information needed to operate server integrations
A linked Minecraft username or UUID when you connect your accounts

Authorized team members may access content posted in our Discord server for moderation, safety, support, and community management.

Discord tickets

Support and appeal tickets are private Discord channels, not user-to-user direct messages.

Ticket content may be accessible to:

The member who opened the ticket
Authorized team members
Discord
The bot or ticket service used to operate the ticket

Tickets are deleted from our Discord server after they are closed and are no longer needed. We do not intentionally maintain a separate permanent transcript archive.

We have not yet verified what information the ticket bot or its provider may retain after a ticket is deleted. This remains an open item in this draft.

A limited record that an account received a permanent ban may remain so that the sanction can be recognized and enforced later.

Discord direct messages

Discord does not expose ordinary direct messages between users to the 1MoreBlock team. We therefore cannot monitor or log those direct messages.

If someone voluntarily submits a direct message, screenshot, or recording to us as evidence, the submitted copy becomes part of the report or moderation information we receive.

Discord voice

1MoreBlock does not record or retain Discord voice conversations.

Staff members may hear a conversation when they are present in the voice channel, just like any other participant. We do not operate a separate voice-recording archive.

Discord may process voice activity and related technical information under its own privacy policy. We do not receive or control Discord’s internal records.

Information handled through Minecraft

When you connect to the Minecraft server, the server, proxy, plugins, and moderation tools may process or create:

Your Minecraft username
Your Minecraft UUID
Your IP address or the address presented by your connection
Connection, disconnection, and session timestamps
Public chat
Private player-to-player messages
/msg, /whisper, /mail, and similar messages
Commands that you run
Books, signs, item names, name tags, and similar player-created content
Gameplay and plugin-visible activity
Reports, sanctions, appeals, and moderation records
Anti-cheat alerts and related evidence
Server logs, plugin databases, and backups
Discord-account links, roles, groups, and permissions

Minecraft private messages are private from players who are not involved in the conversation, but they are not private from the server. They may be written to server log files and reviewed for moderation.

Staff do not read every conversation or continuously monitor all activity. Relevant content may be reviewed after a report or automated flag, when it clearly appears connected to a violation, or during a reasonable review of logs and surrounding context.

Minecraft IP addresses

Only the server owner has routine access to Minecraft player IP addresses.

The server generally receives an IP address when a player connects directly. A tunnel, proxy, or VPN may prevent the server from receiving the player’s original IP address.

Other staff members do not normally receive IP-address information. During an attack or serious security incident, the server owner may share limited relevant IP information with staff who need it to recognize attack patterns. That shared information is cleaned up when it is no longer needed for the incident.

We allow players to use VPNs and proxies. However, connections may still be blocked where an address is associated with abuse, bots, spam, attacks, or sanction evasion.

Minecraft logs and backups

Minecraft server logs may contain:

Usernames and UUIDs
Commands
Public chat
Private player messages
Connection activity
Direct-connection IP addresses
Errors, plugin activity, and moderation information

We do not currently use a fixed calendar-based deletion period for every Minecraft log.

Logs may remain in server backups until the relevant backup storage is rotated, manually cleared, or reused when the backup drive becomes full. We retain logs for server operation, recovery, security, moderation, and incident investigation.

This draft describes our current practice. We still intend to develop a clearer retention schedule so identifiable logs are not kept longer than reasonably needed for those purposes.

Minecraft plugin databases

Minecraft plugin databases are generally retained for as long as they remain useful for preserving the server and its long-running gameplay state.

These databases are not intended to contain real names, email addresses, payment information, or IP addresses. They may contain Minecraft usernames, UUIDs, permissions, sanctions, or gameplay information.

A Minecraft UUID can identify a particular Minecraft account. We therefore treat plugin records as potentially personal information even when they contain no real-world identity information.

Changing a Minecraft username does not change the account’s UUID and does not necessarily remove earlier records associated with that UUID.

Minecraft accounts and telemetry

We do not ask for or receive your Microsoft or Minecraft password, authentication codes, payment information, or secret account credentials.

Minecraft clients may send telemetry or technical information to Microsoft or Mojang. That processing is between the player and Microsoft or Mojang. 1MoreBlock does not receive or have access to their internal telemetry records.

We disable bStats and similar Minecraft server metrics where we control the setting. We do not use Minecraft analytics to build profiles about players.

Information handled through the rules website

The rules website is a static GitHub Pages website.

1MoreBlock has not added:

User accounts
Contact forms
Advertising trackers
A first-party analytics service
Player profiling
Behavioural advertising

GitHub states that it logs and stores the IP addresses of GitHub Pages visitors for security purposes. This applies even when a Pages site uses a custom domain.

Information collected by GitHub is controlled by GitHub under its own privacy policy. 1MoreBlock does not receive GitHub’s internal visitor logs or analytics.

Email

If you contact us by email, we may receive:

Your email address
Your chosen display name
Your message
Attachments
Message timestamps
Technical email headers

Community email is stored in the server owner’s Gmail account. We do not operate a separate email archive.

Ordinary mailbox management is performed through Gmail. Google controls the underlying email service, infrastructure, and backup retention. Messages may remain in the mailbox until they are manually deleted or removed through Gmail’s normal operation.

Do not send account passwords, authentication codes, identification documents, or other unnecessary confidential information by email.

Personal gifts and PayPal

1MoreBlock does not operate a shop and does not ask players to purchase access or ranks.

If you send the owner an unsolicited personal gift through PayPal, PayPal may provide the recipient with transaction information such as:

Your PayPal name or account identity
Your email address
The amount
A payment note
A transaction identifier
Refund, dispute, or chargeback information

PayPal processes the transaction independently under its own terms and privacy policy.

We use transaction information only to recognize and administer the personal gift, respond to questions, handle disputes, and provide a discretionary thank-you where applicable.

Why we use information

We may use relevant information to:

Operate the forum, Discord server, Minecraft server, and website
Provide community membership, permissions, roles, and linked groups
Maintain Minecraft worlds, inventories, permissions, and gameplay state
Respond to support requests, reports, tickets, and appeals
Investigate cheating, griefing, theft, harassment, threats, scams, or abuse
Protect members, community systems, and server infrastructure
Detect bots, spam, attacks, sanction evasion, and security incidents
Understand moderation reports and their surrounding context
Enforce community rules and platform requirements
Diagnose technical problems
Restore data from backups
Maintain necessary sanction and ban records
Respond to privacy requests, disputes, and valid legal requirements

Our purpose is to operate and protect the community, not to pry into ordinary conversations.

Legal grounds

This part of the policy is still being reviewed before the draft becomes final.

Depending on the information and applicable law, we may process information because:

It is needed to provide a community service that you chose to use
We have a legitimate interest in operating, protecting, and moderating the community
You gave permission for an optional action, such as linking an account
We need to respond to a legal requirement
We need to establish, exercise, or defend a legal claim

The final policy will connect these grounds more precisely to the relevant kinds of information and purposes.

Who may access information

Access depends on the service, staff role, permissions, and reason for access.

We limit access to people and tools that need the information to operate, secure, or moderate the community.

Authorized team members may review relevant messages, reports, gameplay records, and moderation information. General staff do not receive routine access to Minecraft player IP addresses.

More sensitive technical information is restricted to the server owner or people specifically authorized to investigate a relevant attack or security incident.

Logging information and a person reviewing it are different activities. Information may exist in a log without a staff member reading it.

1MoreBlock does not sell personal information.

We do not build advertising profiles about members, trade member databases, or provide community information to advertisers.

Information may nevertheless be disclosed:

To hosting, infrastructure, email, CAPTCHA, anti-spam, bot, plugin, backup, or other service providers
To authorized team members when needed for community operation, security, or moderation
When you make information public or ask us to share it
When reasonably necessary to address a serious safety or security concern
When required by a valid legal obligation
To establish, exercise, or defend a legal claim

In serious or repeated abuse cases, we may share a Minecraft UUID and relevant ban reason with a limited number of other server owners so they can make their own safety decision.

We do not ordinarily share full logs, IP addresses, private conversations, or unnecessary real-world information with other Minecraft server owners.

The final policy will include a more complete inventory of third-party providers and tools after that inventory has been verified.

How long information is kept

Different systems, plugins, providers, logs, and backups retain information for different periods.

Our general approach is:

We do not keep information merely because we can.
We try to remove information when we no longer need it.
We periodically purge inactive accounts, expired tickets, old logs, and backups.
Removing information from a live system may not immediately remove backup copies.
Some gameplay information must remain to preserve the Minecraft server.
Some moderation and security information must remain long enough to investigate incidents and enforce decisions.
A limited permanent-ban record may remain so that the account and sanction can be recognized later.
Information handled independently by Discord, Microsoft, GitHub, Google, PayPal, and other providers remains subject to their retention policies.

The exact schedules and criteria are described in the relevant service sections above. Some periods remain under review while this policy is still a draft.

Security

We take reasonable steps to restrict access to community systems and information.

These steps may include:

Account and role-based permissions
Limiting access to more sensitive technical records
Firewalls and connection filtering
Backups and recovery systems
Moderation and anti-abuse tools
Removing temporary incident information after it is no longer needed
Avoiding unnecessary collection of real-world identifying information

No website, server, database, plugin, bot, email account, or backup system can guarantee perfect security.

If you believe community information has been exposed or misused, contact the server owner privately.

Your choices and privacy requests

Depending on applicable law and the information involved, you may ask us to:

Explain what personal information we hold about you
Provide access to or a copy of relevant information
Correct inaccurate information
Delete information that no longer needs to be retained
Restrict or object to certain uses
Explain why particular information must remain
Identify relevant recipients where information has been disclosed

Send privacy requests to mrfloris@gmail.com.

We may need to verify that the requester controls the relevant forum, Discord, or Minecraft account.

For Minecraft, verification may involve temporarily allowing the account to connect and using the normal Discord-linking process to connect the Minecraft UUID to the requester’s Discord account.

We will never ask for:

An account password
An authentication or two-factor code
Full account credentials
Payment-card information
Unnecessary identification documents

Some requests may be limited where records are needed for security, sanctions, other members’ rights, dispute handling, legal obligations, or the establishment or defence of a legal claim.

Requests concerning information controlled directly by Discord, Microsoft, GitHub, Google, PayPal, or another provider must be directed to that provider.

Where applicable, you may also have the right to contact the privacy or data-protection authority responsible for your location.

Minimum age

You must be at least 13 years old to use our forums, Discord server, or Minecraft server.

If the laws that apply to you require a higher minimum age, that higher age applies. A parent or guardian being present does not override the community’s minimum-age requirement.

If someone tells us that they do not meet the applicable minimum age, we restrict their access until they meet it.

Once they meet the applicable age requirement, they may contact the team to request restored access. This is an age restriction, not a ban appeal, and does not consume their appeal or second-chance opportunity.

The complete participation rule remains in the Community Guidelines.

Changes to this draft

This is a public working draft. It may change as we verify systems, correct mistakes, identify providers, and improve our retention practices.

Editorial corrections that do not change how information is handled may be made without a community announcement.

We will announce meaningful changes concerning:

What information we collect
Why we use it
Who may receive it
How long we keep it
The choices and rights available to members

The final policy will receive a version number and effective date. We will remove the draft warning only after the content and our actual practices have been reviewed and approved.

The following providers operate independently and publish their own policies:

These providers may change their policies independently. Their inclusion here does not mean that 1MoreBlock controls or endorses every part of their services.