Skip to content
Sign in

On this page

A Minecraft server and community forum.

Checking players…Checking status…

Play

  • Forums
  • Store
  • Vote
  • Members

Community

  • Team
  • Support
  • Welcome
  • Status
RulesTermsPrivacyCookiesAppeals
Not affiliated with Mojang or Microsoft · © 2026 Titan. All rights reserved.

Privacy

What information Titan holds about you, why we use it, who can see it, how long we keep it, and what choices and rights you have.

Last updated 17 August 2026

On this page

  • The short version
  • Who this policy is from
  • What this policy covers
  • Minimum age and young people
  • Age information and age checks
  • What we hold about you
  • Private messages
  • What we do not do
  • Automated systems
  • Why we use your information
  • Who can see your information
  • Service providers
  • Where your information is processed
  • Other disclosures
  • Cookies and browser storage
  • How long we keep information
  • Your rights
  • Deleting your account
  • How we protect information
  • Data breaches
  • Contact and complaints
  • Changes to this policy

On this page

  • The short version

  • Who this policy is from

  • What this policy covers

  • Minimum age and young people

  • Age information and age checks

  • What we hold about you

  • Private messages

  • What we do not do

  • Automated systems

  • Why we use your information

  • Who can see your information

  • Service providers

  • Where your information is processed

  • Other disclosures

  • Cookies and browser storage

  • How long we keep information

  • Your rights

  • Deleting your account

  • How we protect information

  • Data breaches

  • Contact and complaints

  • Changes to this policy

The short version

Titan holds the information needed to operate your account and the community. That includes your email address, username, anything you publish or submit to Titan, information associated with a linked Minecraft or Discord account, and records needed for moderation, safety, security, appeals, and fraud or ban-evasion prevention.

The Minecraft server and forums may also generate ordinary operational records such as login information, gameplay or server logs, transaction records, anti-cheat information, and security logs.

If you buy a rank, Stripe handles card and billing-address data. Titan stores only the Stripe identifiers, checkout history, subscription state, tier, billing dates, and processing outcomes needed to support the payment and deliver the in-game entitlement.

When you sign in to the website, Titan stores a one-way keyed fingerprint derived from your IP address for up to 30 days. The website does not store the IP address itself in that field. The fingerprint may help our moderation team identify possible alternate-account or ban-evasion activity, but a shared fingerprint or network is not treated as conclusive proof that two accounts belong to the same person.

You must be 16 or older to hold a Titan account. Registration asks for the year you were born; it is not public and is not shown to other members. See Minimum age and young people.

Public forum content may be visible to anyone on the internet. Private messages are not public — and the software restricts who can reach them more tightly than most policies of this kind promise — but you should not treat them as technically inaccessible to Titan. See Private messages.

Titan does not use advertising networks, marketing trackers, tracking pixels, or analytics packages, and does not sell or rent personal information for marketing.

Deleting an account does not necessarily erase every moderation or security record. Where Titan needs limited information to keep a punishment enforceable, prevent abuse, resolve an appeal, meet a legal obligation, or preserve the integrity of its audit records, that information may be retained in a reduced or pseudonymised form.

Who this policy is from

Titan is a Minecraft community consisting of a game server, forums, website, and associated official services.

This policy applies to visitors, account holders, players, and people who interact with Titan through its official systems.

What this policy covers

This policy applies to personal information processed through:

  • the Titan website;
  • Titan accounts and authentication;
  • the Titan forums;
  • Titan’s Minecraft servers;
  • Minecraft and Discord account linking;
  • moderation systems, reports, and appeals;
  • direct messages;
  • official support systems;
  • security and anti-abuse systems;
  • other services expressly operated by Titan.

It does not govern services Titan does not operate. That includes independent Discord servers, social networks, other Minecraft services, video platforms, and any third-party site Titan links to — each of which has its own privacy practices and its own operator.

Linking your Discord account to Titan tells Titan who you are on Discord. It does not put anything you do on Discord under this policy, and it does not make a Discord server Titan’s responsibility merely because Titan members use it.

Minimum age and young people

Titan accounts are 16 and over

You must be 16 or older to create or hold a Titan account.

Titan applies this as a community rule globally, in every country, including those whose law would permit a lower minimum. A single number is one Titan can actually enforce; a number that varies by the member’s claimed country is a number that varies by what the member claims.

You must not:

  • create an account if you are under 16;
  • give a false year of birth to get past this requirement;
  • create an account on behalf of somebody under 16;
  • lend or transfer an account to somebody under 16, whether or not the purpose is to bypass an age restriction;
  • otherwise attempt to circumvent Titan’s age controls.

A parent or guardian cannot override this by giving permission. This is a minimum age, not a consent requirement, so there is nobody who can consent on a younger child’s behalf.

Reading Titan without an account

Some Titan pages and forum content are public and can be read without signing in. Somebody under 16 may therefore be technically able to read public material. They may not create or hold an account, and they may not use any feature that requires one.

Members aged 16 and 17

Meeting the account minimum does not make you an adult. Members aged 16 or 17 are still minors under many privacy and child-protection laws, and Titan treats them accordingly.

Titan therefore minimises unnecessary collection about them and applies particular care to private account information, moderation notes, reports, safeguarding information, private communications, age information, and security records.

Titan does not use anyone’s information for advertising, and that includes information about minors.

Whether an account belongs to a minor is worked out from the year of birth and today’s date each time the question is asked. Titan does not store a “minor” flag, because a stored flag is wrong the day after it is written and nothing wakes up to correct it. A restriction that depends on age therefore lifts by itself as you get older, with nobody editing your account.

Direct messages wait for certainty

Direct messages have their own age check, and it is set to the same number as the account minimum — 16 — but resolved the other way round.

Because Titan asks for a year and not a full date of birth, your age is only known to within about a year. Sign-up spends that ambiguity in your favour: if you turn 16 at any point this year, you may hold an account now. Direct messages spend it protectively: they wait until you cannot still be fifteen.

The practical effect is that a member may hold an account for up to about eleven months before direct messages open to them. That is a real person being made to wait for a feature, and it is still the right side to be wrong on — the situation the check exists for is an adult opening a private channel to somebody who is fifteen, and the cost of being wrong in the other direction is much higher than the cost of a wait.

The same applies if Titan has no year for your account at all — for example where you signed in with Discord and were never asked. Titan cannot apply an age requirement to an answer it does not have, so those accounts are treated as not yet eligible until you supply the year. You can do that once, from your account settings.

The rest of Titan is unaffected. You can read the forum, post, reply, react, report, and appeal.

Accounts found to be under age

If Titan determines that an account is held by somebody under 16, the account may be closed and associated personal information deleted or otherwise handled in accordance with applicable law.

Titan may retain the minimum information lawfully necessary to prevent immediate recreation of the account or to deal with a serious safety, safeguarding, security, fraud, or legal matter.

If you believe an account was restricted or closed on an incorrect view of your age, you can ask for that decision to be reviewed — see Age information and age checks.

Parents and guardians

A parent or guardian may contact Titan about personal information held concerning a member who is legally a minor.

Titan may need to verify:

  • the identity of the person making the request;
  • the identity of the account holder;
  • the requester’s relationship to the account holder;
  • whether the requester has lawful authority to exercise the right being claimed.

Titan will not automatically hand over everything held about a 16- or 17-year-old because an adult says they are that person’s parent or guardian. A young person of that age has privacy rights of their own, and in some situations the law requires their views, maturity and safety to be weighed as well. Titan will consider the request, the relationship, the reason for it, and the interests of the young person before disclosing anything.

Age information and age checks

What Titan asks for today

Registration asks for the year you were born, once, and records that year and the date you answered.

Titan asks for a year rather than a full date of birth because a year is enough to apply an age requirement and is less information to hold. A full date of birth is a strong identifier and a standing liability, and for a Minecraft forum it buys precision nobody needs.

Your year of birth:

  • is not shown on your profile;
  • is not visible to other members;
  • is not readable by ordinary parts of the application;
  • is not used for advertising or profiling;
  • is used only to decide whether you meet an age requirement, and for related safety, account-integrity, legal, and administrative purposes described in this policy.

You cannot change your own year once it is on file. A member who could re-answer could route around every rule built on the answer, so a correction is made by our team, requires a stated reason, and is recorded in the audit log — including both the old and the new year, so that a later reviewer can see what changed rather than merely that something did.

This is the whole of it, today

A declared year of birth is currently Titan’s only age measure. Titan does not operate identity verification, document checks, facial age estimation, or any third-party age-assurance service, and no such provider receives your information.

The rest of this section describes what Titan may do if that changes. It is written in advance so that the limits are agreed before the capability exists, rather than afterwards.

If Titan introduces further age checks

Titan may use additional age-assurance measures where reasonably necessary to enforce the minimum account age, investigate suspected circumvention, review an incorrectly restricted account, or comply with applicable law.

Age assurance can take several forms — verification, estimation, inference, or other age-related signals. Where Titan uses any of them:

  • the method must be reasonably necessary and proportionate to the purpose;
  • less intrusive methods must be preferred, and escalation to a more intrusive one must be justified rather than default;
  • no more information may be collected than the purpose actually requires;
  • the information may not be repurposed for something else simply because Titan now holds it.

Where a specialist provider performs a check, Titan should ordinarily need only the result of that check rather than the identity information behind it. The provider would be permitted to use what it receives only for the authorised purpose, under appropriate contractual and security controls, with access restricted and the information deleted or de-identified when it is no longer required.

Any provider Titan actually engages must be named in this policy before it begins processing.

Australian age-assurance obligations

Where Australian law imposes specific age-assurance obligations on Titan, Titan will take the reasonable steps that law requires to prevent age-restricted Australian users from holding accounts.

Information collected specifically for an Australian statutory age-assurance purpose will be used, disclosed, retained, and destroyed in accordance with the restrictions that law imposes — including any requirement to destroy it once the purpose has been completed.

Where government-issued identification or an accredited Digital ID service is offered for an Australian age check, Titan will provide a reasonable alternative method where Australian law requires one. Titan will not make government identification the only route where doing so would be prohibited.

If Titan gets your age wrong

If your account is restricted or closed because Titan believes you do not meet the minimum age, you can ask for that decision to be reviewed through Titan’s support or privacy contact.

Titan may ask for additional information where it is reasonably necessary to carry out the review, and should ask for the least that will settle the question.

What we hold about you

The information Titan holds depends on how you use the service. Not every category below applies to every member.

Your account

Titan may hold:

  • your email address, used for authentication, account verification, password recovery, security notices, and necessary account communications;
  • your password hash, handled by Titan’s authentication provider rather than stored as a readable password;
  • whether your email address has been confirmed;
  • authentication and session records;
  • timestamps or security values used to invalidate old sessions;
  • two-factor authentication information where you enable it or where it is required for team accounts;
  • security events associated with your account;
  • your year of birth and the date you gave it — see Age information and age checks.

Nobody at Titan can retrieve your password from its stored hash.

Nobody on the Titan team will ever ask you to provide your password, password-reset code, or two-factor authentication code.

Your profile and linked accounts

Titan may hold:

  • your public username;
  • previous usernames;
  • your join date;
  • post count and reaction score;
  • a title or role displayed on your profile;
  • profile information you choose to provide;
  • a profile image or Minecraft avatar;
  • your Minecraft account UUID and in-game name where you link a Minecraft account;
  • previous or relevant Minecraft names where needed for account integrity or moderation records;
  • your Discord account id and Discord username where you link a Discord account;
  • information needed to keep a link trustworthy, such as when it was made and whether it is still valid.

Your username, profile information intended to be public, join date, post count, and reaction score may be visible publicly.

Your email address, year of birth, and non-public security information are not displayed publicly.

Your Discord identity is not public. A Minecraft name is public on this site by design; a Discord handle is a way to reach you off it, so your Discord id and username are shown to you alone and to nobody else on the forum.

Linking a Minecraft or Discord account is optional unless a particular Titan service expressly requires it. You can remove a Discord link in account settings. Minecraft-link corrections use Titan's approved support process so an in-game identity cannot be silently reassigned.

Rank billing, purchase and subscription records

If you start Checkout, buy something from the store, or hold a rank subscription, Titan may store:

  • your internal forum profile identifier;
  • Stripe Customer, Checkout Session, Subscription, Subscription Item, Price, Schedule, Invoice, PaymentIntent, Refund, Dispute, and Event identifiers;
  • the rank requested, current rank, and any pending lower rank;
  • an order record for each thing you buy — what was bought, the Minecraft UUID and player name it is to be delivered to, whether it has been delivered in game, and whether it was later refunded or taken back — kept with your billing records for the same period;
  • subscription and payment status, billing-period dates, cancellation state, and the last synchronization time;
  • short-lived checkout-attempt and idempotency records used to prevent duplicate subscriptions;
  • webhook event type, processing status, attempt count, and a sanitized error summary where processing fails.

Titan does not store raw Stripe webhook bodies, card numbers, bank details, card security codes, or your billing address in its application database.

Stripe receives the account email and Titan profile/tier references needed to create and support the subscription, together with the payment, tax, device, and billing information you provide directly on Stripe's hosted pages. Stripe processes that information under its own privacy terms and legal obligations.

Things you publish or submit

Titan may hold content you provide through its services, including:

  • forum threads and posts;
  • edits and previous versions of edited posts;
  • reactions;
  • reports;
  • evidence submitted with a report;
  • appeals and supporting evidence;
  • replies or information provided during an investigation;
  • direct messages, where you use them;
  • support requests or other communications sent through official Titan systems where those features are available.

Public forum posts may be visible to anyone on the internet and may be indexed, copied, quoted, archived, or cached by third parties outside Titan’s control.

You should therefore treat content deliberately posted in a public area as public information. Deleting your account cannot guarantee that every copy of something you once made public disappears from the internet.

Please do not over-share

Do not deliberately send Titan highly sensitive personal information unless it is genuinely necessary for what you are contacting us about.

In particular, avoid putting private information — yours or anybody else’s — into a public forum post. A support request, a report, or an appeal is the right place for detail that needs to stay out of view.

Reports and evidence

When you report content or another member, Titan may process your report, the reported content, supporting screenshots or recordings, relevant account information, relevant message history, server or forum logs, transaction records, anti-cheat information, observations from our moderation team, and other information reasonably relevant to the report.

When you report content, Titan preserves a snapshot of the relevant content as it existed when the report was made. This allows a report to remain reviewable even if the original content is later edited or deleted.

If you report somebody, do not assume your identity will be revealed to them. Reporter and witness identities are treated as confidential, and the person reported is not told who filed the report.

Minecraft and operational records

Operating a Minecraft server generates records beyond the information shown on your forum profile.

Depending on the Titan server mode and systems in use, Titan may hold information such as:

  • Minecraft account identifiers and usernames;
  • connection, login and logout records;
  • server and gameplay logs;
  • chat records;
  • command or action logs;
  • administrative action logs;
  • transaction or economy records;
  • anti-cheat information;
  • records relating to trades, inventories, land or protection claims, builds, or other gameplay systems where necessary to operate or investigate those systems;
  • server performance and error information;
  • security and abuse-prevention information.

These records may be used to operate the server, maintain game state, investigate reports, diagnose technical problems, detect cheating or exploitation, restore damage where reasonably possible, prevent fraud, and enforce the Rules.

Moderation records

Titan keeps moderation records so decisions can be understood, reviewed, appealed, and enforced consistently.

These records may include:

  • warnings;
  • the rule or conduct involved;
  • warning points or other internal severity information;
  • the date of an incident or moderation action;
  • restrictions or sanctions imposed;
  • sanction duration or expiry;
  • whether a sanction or its points remain active;
  • the team member responsible for an action;
  • information explaining the decision;
  • the in-game name or account identifier relevant at the time;
  • reports made about an account;
  • appeals and their outcomes;
  • information submitted during an investigation;
  • relevant server, forum, transaction, security, or anti-cheat records;
  • observations from our moderation team;
  • internal moderation notes where reasonably necessary for moderation, security, safeguarding, fraud prevention, or administration.

Internal moderation notes are not public. They should be factual, relevant, proportionate, limited to a legitimate purpose, and readable only by people whose role requires them.

Additional care is taken before recording unnecessary personal or sensitive information about a member who is or may be a minor — including members aged 16 and 17.

Titan also keeps an audit log of team actions so important activity can be reviewed and team members can be held accountable.

Evidence relating to moderation

The Rules allow moderation decisions to take account of different kinds of reasonably reliable evidence.

That means Titan may process evidence such as:

  • server or forum logs;
  • chat history;
  • transaction records;
  • anti-cheat information;
  • screenshots;
  • recordings;
  • reports;
  • account records;
  • observations from our moderation team;
  • information voluntarily supplied during an investigation;
  • relevant off-platform material supplied to Titan.

Off-platform material is considered only where there is a meaningful connection to Titan — for example harassment connected to Titan, threats against Titan members, scams targeting Titan members, punishment evasion, account trafficking, attacks on Titan’s infrastructure, a serious safeguarding concern, or another matter within the scope of the Rules.

Titan does not claim authority over unrelated private activity merely because the people involved use Titan.

Evidence is assessed in context. A single category of evidence is not necessarily conclusive.

In particular, accounts using the same network or producing the same IP-derived fingerprint are not automatically treated as belonging to the same person. Shared households, schools, workplaces, public Wi-Fi, mobile networks, carrier-grade NAT, VPNs, shared accommodation, and other legitimate circumstances may cause people to appear technically related.

Technical and security information

Titan also holds limited technical information used for security and abuse prevention, which may include authentication events, session information, security and error logs, request information, rate-limit information, browser or protocol information, IP-derived security identifiers, anti-bot results, and account-integrity signals.

When a website session starts, Titan’s hosting edge may provide a two-letter country code. Titan stores that coarse code with the session so you can recognise its location under Signed-in devices. It is deleted when the session is deleted. Titan does not send saved session IP addresses to a geo-IP service to obtain it.

IP-derived fingerprints

When you sign in to the website, Titan may derive a keyed one-way fingerprint from your IP address.

Only the derived value is stored in Titan’s application database for this purpose.

The fingerprint is used to identify possible relationships between accounts for security, abuse prevention, and punishment-evasion investigations.

It is designed to answer questions such as whether accounts appear to have recently used the same network identifier. It is not intended to reveal an address to our team or to other members.

The fingerprint is deleted after 30 days.

A matching fingerprint is an investigative signal, not proof by itself that accounts belong to the same person.

Rate limiting

Titan may derive short-lived identifiers from connection information in order to prevent abuse of:

  • registration;
  • sign-in;
  • password reset;
  • posting;
  • reporting;
  • messaging;
  • API requests;
  • other endpoints vulnerable to flooding or automated abuse.

These records normally contain counters or temporary identifiers and expire automatically within the applicable rate-limit window.

Provider and infrastructure logs

The fingerprint described above does not mean an IP address never appears anywhere in Titan’s infrastructure. Hosting, network, authentication, or infrastructure providers may create ordinary server or request logs containing information such as:

  • IP address;
  • request time;
  • browser or protocol information;
  • requested resource;
  • network information;
  • error or security information.

Retention of these logs depends partly on the provider and configuration Titan uses.

Access to raw infrastructure logs should be limited to people who need them for security, abuse investigation, technical administration, or legal purposes.

Private messages

Direct messages are not published content. They are not shown to other members, they are not indexed, and they do not appear on your profile.

Private does not mean technically inaccessible to Titan. Titan’s messaging is not end-to-end encrypted, and you should not assume Titan is incapable of reading a message. What follows is what the software actually permits, which is narrower than that sentence on its own would suggest.

How our moderation team can reach a conversation

There is one route, and it runs through a report. A member of the moderation team can read a private conversation only when all of the following are true:

  • a report has been filed on a message in that conversation;
  • that report is currently open or claimed;
  • the report is about somebody the reviewing team member outranks.

The consequences of that design are worth stating plainly, because they are the protection:

  • One report opens one conversation. It does not open the reported member’s other conversations, or the reporter’s.
  • No role grants it. There is no permission flag, rank, or administrator status that opens a conversation on its own. Access is a consequence of an event, not a property of a person.
  • Access closes when the case does. Once the report is resolved, the live read ends. What remains is the snapshot captured when the report was filed, kept as the evidence record.
  • Nobody can open a case about their own messages, and no team member can reach a conversation belonging to a peer or a more senior colleague by having somebody report it.

Reporting a message is therefore what makes it reviewable. If somebody is harassing, threatening, scamming, or endangering you in a private conversation, reporting it is the step that lets our team act on it.

Access outside that route

Titan operates the database that stores messages, and the people responsible for that infrastructure are technically capable of reaching its contents — as is true of any service that is not end-to-end encrypted. Titan does not treat that capability as a general licence to read private conversations.

Outside the report route, Titan may access, preserve, review, or disclose private communications only where reasonably necessary to:

  • operate, maintain, back up, or repair the messaging service;
  • investigate a serious security incident or account compromise;
  • respond to a credible and serious risk to somebody’s safety or life;
  • address a serious safeguarding concern, particularly one involving a minor;
  • comply with a legal obligation or valid legal process;
  • establish, exercise, or defend legal rights.

Access of that kind should be limited to authorised people with a genuine operational need, and limited to what the situation actually requires.

Titan does not read private messages for advertising, marketing, profiling, analytics, or curiosity, and does not use their content to build any profile of you.

Who may use direct messages

Direct messages are subject to their own age check, described under Minimum age and young people.

Conversations you are already part of are not deleted if a restriction later applies — they simply stop accepting new messages, and everyone in them can still read what is there. You can leave a conversation at any time.

What we do not do

Titan does not currently use:

  • behavioural advertising;
  • targeted advertising;
  • advertising networks;
  • marketing tracking pixels;
  • social-media tracking or advertising embeds;
  • cross-site advertising profiles;
  • third-party analytics packages;
  • personal data sales;
  • personal data rental;
  • profiling for advertising.

Titan does not share personal information with advertisers for marketing.

If Titan later introduces materially different tracking, advertising, profiling, or data-sharing practices, this policy must be updated before or when those practices begin, as applicable, and significant changes will be announced.

Automated systems

Titan uses automated systems for routine technical and protective functions, including spam detection, anti-cheat systems, anti-bot controls, rate limiting, security signals, content and link screening, account-integrity signals, and other abuse-prevention measures.

Some restrictions are also applied automatically because they follow directly from a fact on your account rather than from a judgement about you — the messaging age check is the clearest example, and it lifts by itself when the fact changes.

An automated signal may help a human reach a decision. It is not conclusive proof of wrongdoing, and Titan does not treat it as such — the fingerprint match described above is the standing example.

Where applicable law gives you a right to human review of, an explanation of, or a challenge to a significant automated decision, Titan will provide the process that law requires. In practice, moderation outcomes with a real consequence attached are made or confirmed by a person and carry an appeal.

Why we use your information

Where UK or EU data-protection law applies, Titan must have a lawful basis for processing personal information. The basis depends on what the information is being used for.

Providing the service

Titan uses information necessary to provide the services you request, including:

  • creating and maintaining your account;
  • authenticating you and maintaining your sessions;
  • providing your profile;
  • linking your Minecraft or Discord account where requested;
  • operating the forums and publishing content you choose to post;
  • operating Minecraft services;
  • creating and administering a rank subscription you request, reconciling payment state, providing invoices and billing support, and delivering the paid game entitlement;
  • providing direct messages;
  • providing reports and appeals systems;
  • providing support;
  • maintaining account and security settings;
  • sending necessary account communications.

Where applicable, this processing is necessary to perform Titan’s agreement with you or to take steps at your request in connection with that agreement.

Legitimate interests

Titan relies on legitimate interests where reasonably necessary to operate and protect the community, including:

  • enforcing the Rules;
  • investigating reports;
  • moderating content;
  • preventing cheating and exploitation;
  • detecting punishment evasion;
  • preventing fraud and scams;
  • protecting accounts;
  • preventing spam and automated abuse;
  • maintaining service security and availability;
  • enforcing the minimum account age;
  • safeguarding members, and younger members in particular;
  • handling appeals;
  • keeping consistent moderation history;
  • keeping our team accountable through audit records, including investigating complaints about the conduct of a team member;
  • protecting the integrity and availability of Titan’s services.

Titan aims to limit this processing to what is reasonably necessary, after weighing it against the rights and interests of the people affected.

Examples include keeping an IP-derived fingerprint for 30 days rather than indefinitely, treating network matches as investigative information rather than conclusive identity evidence, gating access to private messages behind an open report rather than behind a role, limiting sensitive information to team members who need it, and retaining only the parts of deleted-account moderation records that remain necessary.

Legal obligations

Titan may process, preserve, or disclose information where necessary to comply with a legal obligation.

This can include responding to a valid legal demand or court order, meeting a regulatory requirement, complying with a lawful preservation request, responding to an authorised regulator, or preserving information Titan is legally required to retain.

Vital interests and serious safety situations

In exceptional circumstances involving a serious and immediate risk to somebody’s life or safety, Titan may use or disclose relevant information where data-protection law permits this.

This may be relevant, for example, where Titan receives credible evidence of serious threats or child-safety concerns.

Consent

Titan does not currently rely on consent for advertising or marketing.

If Titan introduces an optional feature for which consent is the appropriate basis, consent will be requested separately and should be capable of being refused or withdrawn where required by law.

Titan does not describe processing as consent-based where it is in fact compulsory for holding an account. Calling something optional when refusing it would close your account is not consent.

Who can see your information

Access depends on the type of information.

Other members and the public

Information intended to be public may include:

  • your username;
  • public profile;
  • public posts and replies;
  • reactions;
  • join date;
  • post count;
  • reaction score;
  • public roles or titles;
  • linked Minecraft name where the service displays it.

Information that is not public

Titan does not ordinarily make any of the following public:

  • your email address;
  • your year of birth;
  • age-check information;
  • authentication information;
  • your linked Discord id or Discord username;
  • direct messages;
  • reports and the identities of reporters or witnesses;
  • private appeals;
  • internal moderation notes;
  • security information;
  • IP-derived fingerprints;
  • raw infrastructure logs.

Moderation information

You may be shown the user-facing parts of your own moderation record, including information such as:

  • the warning or sanction;
  • its date;
  • the broad reason;
  • relevant warning points and whether they remain active;
  • a restriction currently in force and its expiry;
  • the available appeal process.

Some information may be withheld from the normal warnings interface where disclosure would reveal or materially compromise:

  • another person’s private information;
  • the identity of a reporter or witness;
  • internal moderation notes;
  • confidential evidence;
  • anti-abuse or anti-cheat methods;
  • security-sensitive information;
  • an active investigation;
  • safeguarding information.

A person who submits a report may not be told the exact punishment imposed on somebody else.

Public bans

If Titan operates a public ban list at /bans, it may display limited information such as:

  • the relevant username or in-game name;
  • the broad category of rule violation;
  • the date;
  • the expiry date where applicable.

A public ban list must not display:

  • email addresses;
  • years of birth;
  • IP addresses or IP-derived fingerprints;
  • private messages;
  • reports or reporter identities;
  • internal moderation notes;
  • confidential evidence;
  • unnecessary personal information.

The Titan team

Team access is based on role and operational need.

A team member should only have access to information needed for their responsibilities.

More sensitive security, administrative, or personal information should be restricted to a smaller group of authorised team members.

Team activity involving moderation or sensitive administrative powers may itself be recorded in Titan’s audit logs, and team members may be required to authenticate again before using those powers.

Service providers

Titan uses third parties to operate parts of the service.

Providers receive only the information reasonably necessary for their role, and may process it according to their agreements with Titan and their own legal obligations.

Supabase

Titan uses Supabase for database and authentication functionality.

Information held there may include account information, authentication information, profile information, forum content, direct messages, moderation records, and other application data described in this policy.

Supabase may also provide authentication-related account emails such as email confirmation and password-reset messages.

Stripe

Titan uses Stripe to create and manage monthly rank subscriptions, calculate tax, host Checkout and invoices, update payment methods, process cancellation, detect payment outcomes, and handle payment disputes.

Stripe may receive your email address, Titan's internal profile/tier references, IP address and device information, and the payment, billing-address, and tax information you provide on Stripe-hosted pages. Stripe handles card and bank details; Titan does not receive those details.

Titan receives Stripe object identifiers and subscription, invoice, tax, and payment-status information needed for delivery, support, accounting, fraud prevention, and legal obligations.

The TitanMP game network

Purchases are delivered in game by the Minecraft network's own software (TitanLink), which runs on separate infrastructure from this site. To deliver what you bought, Titan tells that software the Minecraft UUID of the account you linked and that an order is waiting for it; the network then fetches the order from Titan and hands it over in game.

What is sent is your Minecraft UUID and the order — the product, the quantity, and the Minecraft player name on your linked account. Your email address, forum profile identifier, and payment details are not sent to the game network.

Cloudflare Turnstile

Titan uses Cloudflare Turnstile as an anti-bot measure on certain sensitive forms, such as registration, sign-in, or password reset.

Cloudflare may receive technical information including your IP address and information necessary to determine whether a request appears to come from a human user.

Titan does not use Turnstile as an advertising system.

Discord

Where you choose to link a Discord account, Titan receives the account identifier and username needed to record the link, and Discord receives the request that authorises it.

Linking is optional, can be undone from your account settings, and is governed on Discord’s side by Discord’s own privacy policy.

Upstash

Where configured, Titan uses Upstash for short-lived rate-limiting information.

Rate-limit values are based on derived identifiers and expire within the applicable rate-limit period.

Anthropic and Vercel AI Gateway

Where configured, Titan uses Anthropic's Claude models to write short summaries of long forum threads. This feature is off unless Titan has switched it on, and no request is made while it is off.

These requests are routed through Vercel AI Gateway rather than sent to Anthropic directly. Vercel hosts Titan, so it already handles forum content in the ordinary course of serving the site; the gateway is an additional purpose for which it handles that content, and both Vercel and Anthropic are processors for this feature.

When a signed-in member asks for a summary, the text of the visible posts in that thread and the usernames shown on them are sent so the summary can be written. Only posts that are publicly visible to the member who asked are sent; hidden, deleted and pending posts are not.

Titan does not send your email address, your IP address, your account identifiers or any private message to Anthropic, and no summary is generated from a conversation or a support ticket.

The summary Titan receives back is stored on the thread and shown to everyone who can read that thread, alongside the name of the model that wrote it. Titan records which member asked for it. A summary is deleted automatically if any post in the thread is later hidden or removed.

Crafatar

Titan may use Crafatar to render Minecraft player-head images.

Where Titan fetches these images server-side, your browser does not need to send your IP address directly to Crafatar for the image request.

The Minecraft UUID needed to obtain the relevant player image may be sent.

Flagcdn

Titan uses Flagcdn to display a country flag beside a signed-in session’s stored country code.

When you open the Signed-in devices page, Flagcdn may receive your browser’s IP address and the country code contained in the requested image path. Titan does not send the saved IP address of that session to Flagcdn.

Where your information is processed

Titan and its service providers may process information in countries other than the one you live in. The exact locations depend on Titan’s infrastructure and on the providers named above.

Where applicable law imposes requirements on overseas disclosure or international transfer of personal information, Titan will apply the safeguards that law requires for the transfer.

Other disclosures

Titan does not sell personal information or disclose it for third-party advertising.

Titan may disclose relevant information where reasonably necessary and legally permitted:

  • to service providers operating Titan systems;
  • in response to a valid legal requirement;
  • to comply with a court order or lawful regulatory requirement;
  • to investigate or respond to serious fraud or security threats;
  • where somebody appears to be at serious risk of harm;
  • in connection with serious safeguarding or child-safety concerns;
  • to report apparently unlawful conduct where appropriate;
  • to protect Titan, its members, or others from serious unlawful conduct;
  • to establish, exercise, or defend legal rights.

Where law permits, Titan will seek to avoid disclosing more information than reasonably necessary.

Serious safety and safeguarding situations

Where Titan receives credible information suggesting that somebody may be at serious risk of harm, it may preserve, review, or disclose relevant information.

Depending on the circumstances and the applicable law, Titan may contact the relevant service provider, a safeguarding organisation, law enforcement, emergency services, a regulatory body, or another appropriate authority.

What is shared should be limited to what is reasonably relevant to the situation.

Cookies and browser storage

Titan uses cookies and browser storage for authentication, security, user-selected preferences, and optional features.

This can include:

  • authentication cookies used to keep you signed in;
  • local storage for browser-only preferences and vote reminders;
  • session storage for held forum quotes;
  • storage used by Cloudflare Turnstile on pages where the bot check operates.

Removing necessary cookies or storage may:

  • sign you out;
  • prevent you authenticating;
  • reset your settings;
  • prevent a protected form from working.

Titan does not currently use advertising cookies or analytics cookies.

The Cookie Policy identifies the individual cookies and browser-storage items used by the live service, who sets them, their purpose, and their duration.

How long we keep information

Titan does not keep every category of information for the same period. How long something is kept depends on why it was collected, whether the account is still active, and whether security, moderation, legal, safeguarding, fraud-prevention, or dispute requirements still apply.

Titan aims not to hold identifiable information for longer than reasonably necessary.

IP-derived fingerprints

Up to 30 days, after which they are deleted.

Rate-limiting information

Normally minutes to an hour, depending on the applicable rate-limit window.

These records expire automatically.

Age information

Your year of birth is kept while your account is open, because it is the fact every age rule is derived from and there is nothing else to derive them from.

If Titan ever collects information for a specific age-check purpose beyond that declared year, it will be kept only as long as that purpose permits and requires. Where Australian law requires information collected for a statutory age-assurance purpose to be destroyed once the purpose is complete, Titan will destroy it as required. Age-check inputs are not repurposed simply because Titan holds them.

Previous usernames

A released username may be reserved for 90 days after a change to reduce impersonation risk.

Names that have been associated with team roles may be retained longer where reasonably necessary to prevent impersonation of our team or preserve historical accountability.

Posts and threads

Public forum contributions may remain for as long as the forum operates.

Account deletion does not automatically remove every post because removing all contributions from a discussion may materially disrupt content created by other participants.

You may separately request removal of particular personal information or content. Titan will consider that request in light of applicable law and the rights and interests of other people.

Content removed by moderators may enter a recycle or recovery system before being permanently purged according to Titan’s operational retention process.

Direct messages

How long a private conversation is kept depends on the participants’ accounts and on whether the content is needed for a moderation, security, safety, legal, or dispute-resolution purpose.

A conversation has more than one participant, so closing your account does not by itself require Titan to delete messages you sent to somebody else, any more than deleting your account deletes the emails you have sent. Where a message is part of a report, the snapshot captured with that report is retained with the report rather than with the conversation.

Minecraft and operational logs

Retention depends on the type of record and its purpose.

Routine operational logs should not be retained longer than reasonably necessary for operation, security, troubleshooting, moderation, fraud prevention, abuse investigation, or legal obligations.

Records attached to an active moderation case, appeal, security investigation, safeguarding matter, or legal hold may be retained longer where necessary for that purpose.

Your account

Account information is normally retained while your account remains open.

Additional information may remain after closure where described below.

Rank billing records

Titan keeps the minimal Stripe identifiers and subscription records described above for up to 7 years after the later of the final transaction, subscription end, or account closure, where needed for accounting, tax, consumer claims, chargebacks, fraud prevention, or legal obligations.

After that period, the scheduled billing-retention process removes terminal subscription and Customer mappings for deleted accounts unless a specific legal or investigation hold still requires them. Stripe may retain its own transaction records under Stripe's separate legal obligations and retention policy.

Completed or failed checkout-attempt records are removed after 90 days. Successfully processed webhook idempotency records are removed after 90 days; failed processing records may be retained for up to one year for incident investigation. Raw webhook payloads and payment-card data are never stored in these records.

Moderation records

A moderation finding does not necessarily disappear merely because its active warning points expire.

Historical moderation information may be retained so Titan can:

  • distinguish previous conduct from a clean record;
  • investigate repeated or serious misconduct;
  • prevent punishment evasion;
  • review appeals;
  • maintain consistent enforcement;
  • prevent fraud;
  • safeguard the community;
  • maintain accountability within our team.

Expired historical information is not necessarily treated as an active punishment.

After account deletion, Titan should reduce retained moderation information to what remains reasonably necessary for these purposes.

Team audit logs

Audit records may be retained for an extended period where necessary to preserve accountability, investigate the conduct of a team member, investigate a security incident, demonstrate how a moderation or administrative action occurred, or protect the integrity of Titan’s systems.

Legal and investigation holds

Information that would otherwise be deleted may temporarily be retained where it is:

  • relevant to an active investigation;
  • relevant to an unresolved appeal;
  • necessary for a safeguarding matter;
  • subject to a legal preservation requirement or litigation;
  • reasonably necessary to investigate serious fraud or security abuse.

The information should return to its ordinary retention rules once the reason for the hold ends.

Backups

Titan may maintain encrypted rolling backups.

Deleting information from the live system may not immediately remove every historical copy from an existing backup.

Backups should expire according to their normal retention schedule.

Where a deleted account or record is restored from a backup, applicable deletion or suppression measures should be re-applied.

Your rights

Your rights depend on where you live and which privacy law applies. Depending on the circumstances, you may have the right to:

  • ask whether Titan holds personal information about you;
  • ask for access to that information;
  • correct inaccurate information;
  • request deletion;
  • restrict certain processing;
  • object to certain processing;
  • withdraw consent, where processing genuinely relies on consent;
  • receive certain information in a portable format;
  • challenge a significant automated decision, where applicable law gives you that right;
  • make a privacy complaint.

These rights are not absolute in every situation.

Titan may be entitled or required to refuse or limit a request where information must be kept for reasons such as legal obligations, the rights of another person, security, fraud prevention, safeguarding, confidential moderation information, an active investigation, or the establishment or defence of legal claims.

Titan will not charge for an ordinary rights request unless applicable law permits it in exceptional circumstances.

Access and correction

Titan may need to verify your identity before giving access to non-public information or carrying out a sensitive request. That verification should be proportionate to how sensitive the information is — a routine request should not require more proof than the answer is worth.

Titan will not disclose one person’s private information merely because somebody else has asked for a record that happens to contain it. A conversation, a report, and a moderation case usually involve more than one person, and a request from one of them is not consent from the others.

What you can reach yourself

Without contacting anybody:

  • your account page shows your account information;
  • your data page lets you export a copy of your information and request deletion of your account;
  • your warnings page shows the user-facing portion of your moderation record and available appeals;
  • security settings let you manage password and session security.

Taking an export is itself recorded. Each one is limited to a small number per day and writes a row to Titan’s disclosure and audit logs, so that a copy of your information having been taken is an event somebody can later account for. The export itself is not stored — it is built, sent to you, and forgotten.

Other requests

Requests for correction, restriction, objection, or anything the export does not cover are handled through Titan’s privacy contact process, described under Contact and complaints.

Titan will respond within the period required by the law applicable to your request, subject to any lawful extension.

Deleting your account

Deleting your Titan account closes the account and removes or de-identifies information that Titan no longer needs.

It does not automatically erase every piece of content or every record connected to the account.

Active rank subscriptions

Self-service account deletion is blocked while a non-terminal rank subscription remains attached to the account. Cancel through Account Billing first and wait until the paid period ends, so deleting the forum identity cannot orphan a recurring payment or its game entitlement.

Once the account is deleted, the forum profile is de-identified. Minimal Stripe identifiers and terminal subscription state may remain for the approved financial-record period described under How long we keep information. An active billing retention hold delays only those records needed for the specific legal, tax, fraud, chargeback, or consumer dispute.

Public contributions

Posts and threads may remain after account deletion where retaining the contribution is reasonably necessary to preserve discussions involving other members.

Titan may remove, anonymise, or otherwise alter identifying profile information associated with a deleted account where appropriate.

You may separately ask for specific content containing personal information to be removed.

Moderation, safety, and security records

Some moderation, security, fraud-prevention, safeguarding, and audit information may need to remain after account deletion.

This is particularly relevant where deleting the record would allow somebody to evade an active punishment, recreate an account immediately, interfere with an investigation, defeat fraud controls, undermine community safety, or destroy evidence needed for a legitimate legal purpose.

Where continued identification is necessary, Titan should retain only the identifiers reasonably needed to keep the record meaningful or enforceable.

This retained information should therefore be described as minimised or pseudonymised, rather than anonymous, wherever Titan can still connect the information to a person or account for enforcement purposes.

Information that no longer needs to identify you should be de-identified where reasonably possible.

The retained record may include information such as:

  • the fact that a moderation action occurred;
  • the rule or conduct involved;
  • its date;
  • the sanction;
  • whether the sanction remains active;
  • the minimum account or game identifiers needed to prevent evasion;
  • information necessary to understand or review the decision;
  • associated audit information.

Retaining a historical moderation record does not automatically mean expired warning points continue to count.

Age information

Deleting your account does not entitle Titan to keep age-check information for longer than the applicable law permits. Any destruction requirement that applies to information collected for a statutory age-assurance purpose continues to apply after the account is gone.

Objections

Where Titan relies on legitimate interests to retain information, you may object to that processing where the law gives you that right.

Titan will consider your circumstances against the reasons for retaining the information and tell you the outcome.

Active investigations and legal holds

Where information is part of an active investigation, unresolved appeal, safeguarding matter, fraud or security investigation, or legal hold, deletion may be deferred for the relevant information until that reason no longer applies.

Titan should tell you where it is legally able to do so.

How we protect information

Titan uses technical and organisational measures intended to limit unauthorised access, alteration, disclosure, destruction, and misuse.

Current measures include the following.

Database permissions

Access controls are enforced at the data layer so members and our team receive only information their role permits them to access.

Controlled writes

Application changes to protected data are intended to go through controlled database operations that verify permissions rather than giving ordinary user accounts unrestricted write access.

Team authentication

Team members are required to use two-factor authentication before exercising moderation or administrative powers.

Particularly sensitive actions may require additional authentication.

Restricted sensitive access

Sensitive account, security, and moderation information is restricted according to team role and need.

Some information is restricted more tightly than by role alone. Private conversations are the clearest case: no role opens one, and access follows from an open report rather than from a permission — see Private messages.

Data minimisation

Titan tries to reduce how much sensitive information it stores in the first place. Examples include:

  • storing a keyed one-way fingerprint for the 30-day account-correlation function instead of a raw IP address in that field;
  • asking for a year of birth rather than a full date of birth;
  • not collecting identity documents or operating an age-verification service;
  • deriving minor status and messaging eligibility rather than storing them as flags;
  • reducing what is retained after an account is deleted.

The secret used to create the IP fingerprint is kept separately from the database that stores the fingerprints.

Audit logging

Important team actions are recorded in audit logs designed to make unauthorised or inappropriate administrative activity detectable.

Encryption

Traffic between your browser and Titan is encrypted in transit using HTTPS where applicable.

Hosting and database providers may also provide encryption and security controls for stored data.

No technical system can be guaranteed to be perfectly secure.

Reporting a vulnerability

If you discover a genuine security vulnerability affecting Titan, please report it privately through Titan’s designated security or administrative contact rather than exploiting it or publishing instructions that could place Titan or its members at risk.

Do not go further into a vulnerability than is reasonably necessary to demonstrate that it is real, and do not access, alter, destroy, or publish other people’s information along the way.

Good-faith security reports will not be treated as misconduct merely because the reporter discovered a vulnerability.

Data breaches

Titan will investigate any suspected unauthorised access to, disclosure of, loss of, or compromise of personal information.

Where applicable law requires a data breach to be notified, Titan will make the notifications that law requires — to affected individuals, to regulators, or to both — within the time it allows.

Depending on the incident, Titan may also:

  • invalidate sessions;
  • reset or force a change of credentials;
  • restrict affected accounts;
  • preserve evidence;
  • notify the relevant service providers;
  • correct the underlying security weakness;
  • monitor for further abuse.

A notification will describe what happened, what information was involved, and what you can do about it, as far as Titan is able to establish those things at the time.

Contact and complaints

To:

  • request access to your information;
  • correct information;
  • request deletion;
  • restrict or object to processing;
  • make another privacy request;
  • report a privacy concern;

contact Titan through its designated privacy contact.

Contact an administrator listed on our team page and say what you are asking for. You do not need to cite any law.

Please give enough detail for Titan to understand and investigate the issue — but do not send sensitive information that the request does not actually need.

For ordinary moderation or technical-support issues that do not concern privacy, use Titan’s normal support or moderation channels.

Complaining to a regulator

If you are dissatisfied with Titan’s handling of your information, you may also have the right to complain to the privacy or data-protection authority responsible for your area.

  • In the United Kingdom, this is the Information Commissioner’s Office.
  • In the European Economic Area, it is generally the competent supervisory authority for the relevant member state.
  • In Australia, this may be the Office of the Australian Information Commissioner, where the matter falls within its jurisdiction.

You do not have to complain to Titan before exercising any right to contact a regulator.

Changes to this policy

Titan may update this Privacy Policy as its services, infrastructure, providers, security practices, legal obligations, age measures, or data practices change.

The “last updated” date at the top shows when the published policy was most recently changed, and each version takes effect on that date unless the change is announced in advance with a later one.

Significant changes affecting what information Titan collects, why it is used, who receives it, the age requirements, how long information is retained, how private messages are handled, or your rights should be announced through an appropriate official Titan channel.

Titan will not quietly introduce advertising, marketing data-sharing, materially broader tracking, or similarly significant new uses of personal information without updating this policy as required.

Where appropriate, changes will be announced before they take effect.

ForumsEventsTagsStoreVoteMembersTeamSupport
Sign in
ForumsEventsTagsStoreVoteMembersTeamSupport
Cart
Sign in
1 player online
All systems operational