Last updated: 26 September 2026. Effective upon publication on 26 September 2026. This security-related account-closure change takes effect immediately to preserve enforcement of active restrictions.

Patriam Studios, a general partnership in British Columbia, Canada, operates the Patriam Minecraft community and is responsible for the personal information described here. Our privacy contact is contact@patriamstudios.com; mark your message “Privacy request”. This policy covers our server, forums, wiki, linked community features, map, statistics and store operations.

1. Information we handle and why

• Accounts and connections: usernames, email addresses, account settings, authentication and recovery records, and identities you link or verify, such as a Minecraft name and UUID or Discord name and ID. We use these to operate accounts, verify ownership, connect services, provide support and protect against impersonation and abuse.
• Connection and security information: IP addresses, connection times, browser or device information, request and error logs, and security events. These can identify or be linked to a person. We use them to deliver and secure the service, diagnose faults, prevent spam and investigate misuse. An IP match alone does not establish that two accounts belong to one person.
• Community and gameplay records: posts, messages, wiki edits and their history, characters, realms, votes, poll choices, gameplay activity, chat and relevant server logs. These support the feature you use, shared-world records, community safety and rule enforcement. Visibility depends on the feature and its access settings.
• Cases and evidence: reports, appeals, bug reports, correspondence, attachments, source references, relevant punishment records, staff notes and decision/audit records. We use them to investigate, decide and independently review cases. Evidence can include information supplied by other people about you.
• Helper applications: your linked account, application answers, status, reviewer notes and decision records. We use these to assess suitability and manage recruitment. The form asks about motivation, experience, availability and judgement, not your date of birth or private contact details. Do not include unnecessary sensitive information.
• Purchases and support: order references, products, amounts, payment status, delivery records and information a payment provider makes available for the transaction or dispute. PayPal processes payments under its own privacy notice. Do not send us payment passwords or complete card details.

We obtain information from you, your use of the services, people who interact with or report an incident, and providers needed for features you use. We limit collection, use and disclosure to reasonable identified purposes, with consent or another basis allowed by applicable law. Optional uses are not a condition of access to an unrelated service.

Our Minecraft server does not enforce secure-profile verification. This setting does not disable all of Minecraft's own reporting features or make chat private. Chat remains subject to moderation and may be logged. Use Cases to send a report to Patriam staff; Minecraft's own reporting system is a separate process.

2. Public content, maps and statistics

Public posts, profiles, wiki content, characters and realm information can be read and copied by other people and may be indexed by search engines. Check the audience before sharing. A private message or restricted page is not a promise that no authorised administrator can access it when necessary to operate the service or investigate a problem.

Under the public-contribution licence in the Terms of Service, public creative work may also appear in Patriam promotional material, including websites, social posts, videos and advertisements. A copyright licence does not replace privacy consent. Before using an identifiable person's image or personal information in promotion, we will obtain any separate consent required by law, with appropriate parent or guardian involvement where needed. Private messages, reports, applications and restricted staff documents are outside that promotional licence.

BlueMap displays the shared Minecraft world and, where enabled, player names, positions or other map information. Plan records server and player activity for statistics and administration; the information a visitor can see depends on the statistics site's permissions. Avoid treating an in-game location or activity record as confidential merely because it is not in a forum post.

Authorised senior staff can view relevant website infractions and request current Plan and LiteBans information while reviewing a player or Helper application. These summaries are fetched on demand rather than copied into a separate forum statistics database. The source systems still store their own activity and punishment records. Missing provider data is not evidence of a clean history.

3. Restricted reports, applications and decisions

Cases and their attachments are limited to the submitter and staff authorised for the case, with additional restrictions for sensitive material. Internal notes and protected evidence are not generally shown to applicants, reporters or the public. Helper applications and review notes are restricted to the applicant's permitted view and authorised recruitment staff.

A person reporting someone else may be told that a case is closed without receiving that person's sanction details or private review notes. We may disclose relevant allegations or evidence where reasonably needed for a fair response, while protecting unrelated personal information and others' safety. Privacy access requests are considered separately under the applicable law and its exceptions.

4. Linked-account security history

When a website integration is created, changed or removed, we retain a restricted observation of the website account ID and username, integration provider, external username and stable identifier, verification state and event time. Authorised administrators use it to investigate abuse and attempts to evade account-based action, including after an account is unlinked or deleted.

Each historical observation becomes eligible for deletion after 24 months and is removed by bounded maintenance during ordinary site or scheduled queue activity. A current active link remains current profile data while it is in use. This restricted history does not contain passwords, verification codes, OAuth tokens, email addresses or IP addresses. Those exclusions describe this history, not every other account or security record we hold.

5. Cookies, browser storage and Cloudflare

The website uses cookies and browser storage for sign-in sessions, optional remembered login, security, language or display preferences, and functions such as remembering viewed topics. These identifiers can relate to your account or device; they are not necessarily anonymous. Blocking essential cookies may prevent sign-in or other requested features.

Cloudflare helps deliver and protect the website, including checks for automated or malicious traffic. Its services receive request, IP and browser information and may use security cookies or browser checks. The website also uses a Cloudflare performance/traffic measurement beacon. We use that information to understand service operation and performance.

Use available cookie controls and your browser settings to manage optional cookies or stored data. Closing a notice or registering does not by itself authorise unrelated optional tracking. If a feature requires additional consent, that choice must be explained separately. Linked or embedded third-party services may apply their own cookies and policies when you access them.

Handbook readership: when optional cookies are allowed, we use the existing website session to measure visits to Handbook documents and sections and PDF opens through Handbook routes. We use these counts to understand interest and improve the guides. The collector creates no additional browser cookie and stores no raw session identifier, account ID, IP address or browser user-agent string. It stores a keyed session pseudonym that changes each UTC day, the document and section visited, the event type and the last counted time. These are pseudonymous records, not proof of who read or understood a guide. Repeated visits to the same section or a guide's PDFs within 30 minutes count once.

Handbook collection respects declined optional cookies, Do Not Track and Global Privacy Control signals, and excludes recognised automated or prefetched requests. Daily session records outside the most recent 90 UTC calendar days become eligible for deletion through bounded maintenance; aggregate daily document and section counts are retained for longer-term trends. The dashboard shows aggregate statistics to permitted staff and preserves each restricted document's audience. This collection is separate from security logs and other services described in this policy.

6. Who can receive information and where

The Minecraft server is hosted in Quebec, Canada. Authorised partnership members, administrators and staff may access information from other countries when performing duties for the community. Access is limited according to the task and sensitivity of the information. The separate New Zealand company responsible for the Unreal game does not receive this Minecraft-community information for that company's business.

Providers for hosting, security, email, authentication, payments and communication receive the information reasonably needed to provide their service. Providers and overseas access can involve processing outside your province or country, where local courts or authorities may have lawful access. We remain responsible for information under our control and use appropriate safeguards for the services we engage.

We may also disclose information where required or permitted by law, for a lawful investigation, to protect someone's safety, or to establish or defend a legal claim. We do not make all player records public simply because we moderate a community. Contact us for more information about providers and cross-border handling relevant to your information.

7. Retention, deletion and security

We keep personal information only as long as reasonably needed for the stated purpose or a lawful operational, accounting, security or dispute requirement. Retention depends on the record: an active account, a shared-world contribution, an unresolved case, a recruitment decision and a payment dispute have different needs. Relevant decision records are retained for at least the period required by applicable law so an affected person can exercise access rights.

Closing an account or restricting access does not automatically erase every related record. Where lawful and reasonably necessary to enforce an active restriction, investigate evasion, resolve a dispute or meet a legal duty, we may retain a minimal record of the decision, relevant email and IP addresses, and supporting evidence. We delete or de-identify them when retention is no longer justified. An IP match alone does not establish identity. Shared-world contributions and records involving other people require separate review; operational logs and backups rotate under their own schedules. We will explain material limits.

While a forum ban remains active, we may use a restricted email record to prevent new registration with the same address even if the associated account is later closed. We review the need for that record and remove it when no longer justified.

We use reasonable access controls and technical and organisational safeguards appropriate to the information. No online system is risk-free. Keep credentials private, use available account protections, and contact us if you suspect a breach. We will investigate security incidents and give notices required by applicable law.

8. Your choices and privacy requests

You can ask what personal information we hold about you and how it is used or disclosed, request access or correction, and withdraw consent where applicable. We assess any request to close an account or remove information under this policy and applicable law, including any applicable right to erasure. Withdrawing consent may mean we cannot provide a feature that needs that information; it does not invalidate prior lawful processing or prevent retention or use allowed by law.

Email contact@patriamstudios.com with the relevant account email address or username, if known, and a description of your request. We may ask for proportionate proof of identity to avoid disclosing information to the wrong person. Do not send a password, authentication code or identity document unless we have explained why a specific secure verification step is necessary.

We will respond within the applicable statutory time limit and explain any lawful extension, refusal, redaction or correction decision. Access may be limited to protect another person's information, confidential legal advice or another exception recognised by law. If a correction is disputed, you may ask that the record reflect your concern.

A ban, community exclusion or closed moderation appeal does not remove your privacy rights or access to this email contact. You may raise a privacy concern with us and, where applicable, with the Office of the Information and Privacy Commissioner for British Columbia or the Office of the Privacy Commissioner of Canada. We will not treat a good-faith privacy request or lawful complaint as misconduct.

9. Children, changes and contact

Parents and guardians should review the services and privacy choices with young people. Use of Minecraft, Discord, payment and other provider accounts must meet those providers' age and consent requirements. Where a young person cannot give meaningful consent themselves, a parent or guardian must be involved. Contact us if you believe a child's information was provided without necessary permission.

We will date policy updates and communicate material changes appropriately. A new purpose requiring fresh consent will be explained before that use begins. For questions about this policy or our privacy practices, contact contact@patriamstudios.com.

10. Referral rewards and abuse prevention

When you participate in referrals, we record the referring and referred accounts, linked Minecraft identifiers, referral status, qualifying gameplay activity, reward amounts and delivery records. We use these records to award store credit and raffle entries, prevent duplicate rewards and investigate abuse. Restricted staff records include screening evidence, corrections and review decisions.

The game server records connection IP addresses for referral screening. For accounts involved in a referral, we send an IP address to Proxycheck.io to check for shared hosting, VPNs, proxies and related security indicators. We do not send that provider your forum email address, password, referral code or Minecraft identifier. The provider handles queried addresses under its own privacy notice, including processing described there to identify proxies. This is not a promise of zero retention by the provider.

The referral service stores recent connection addresses encrypted on the game server. They become eligible for deletion 30 days after their last recorded use and are removed during bounded maintenance. The website receives keyed address fingerprints and screening results instead of the original addresses. These fingerprints can still link accounts and are treated as restricted personal information. Necessary referral, security, review and transaction records remain subject to the retention and privacy-request provisions above; deleting a recent address does not erase those records.

Activity checks distinguish qualifying play from idle time and use limited activity summaries to identify possible reward farming. Shared networks or a VPN or hosting indicator can hold a reward for staff review. A shared address, business ISP or network classification alone does not prove that two accounts belong to the same person or that a player has broken a rule. You can ask staff to review a held referral and use the privacy contact above for access or correction requests.