Terms of Service

These Terms govern your use of the Tibia Claims website, backend, Discord bot, account features, and any server-specific features made available through them. Before a new sign-in is retained or an existing account uses protected website or Discord features, Tibia Claims may show the current Terms and Privacy Policy with an unchecked agreement control. By actively selecting that control, you agree to these Terms and acknowledge the Privacy Policy. Merely viewing a public page, installing the bot, typing a command, or dismissing the prompt does not record acceptance. If you do not agree, do not select the control or use authenticated features.

You may use Tibia Claims only if you are legally able to agree to these Terms and meet the minimum-age and account requirements imposed by Discord, applicable law, and the relevant game-server community. If you do not meet all applicable requirements, do not use account features.

Each person may maintain only one Tibia Claims account, connected to one immutable Discord identity. Server groups, strikes, and BLACKLIST apply to all current and future verified characters of that account on the applicable server world. You must not create, control, or use another account to split characters, avoid a review or restriction, or obtain additional permissions.

Tibia Claims provides claim boards, optional Discord sign-in, account and character tools, server-scoped favourites, and server features that are enabled individually. The frontend receives Nevia board information only from the Tibia Claims backend; the backend reads the external Nevia community service, which remains the source of truth. Tibia Claims cannot create, modify, confirm, or cancel a Nevia claim unless a separate external-authority integration is explicitly enabled.

For a native Tibia Claims server whose claim controls are enabled, an eligible signed-in user may create, list, and cancel reservations through the website or the Discord bot. Both interfaces use the same backend decision and reservation store. A private native server and its reservations remain restricted to users authorized for that server.

Board information may be cached, delayed, incomplete, inconsistent, or unavailable. Always verify important details with the relevant community service. Displaying a claim does not guarantee access to a hunting ground, hunting priority, or enforcement by Tibia Claims.

The one-account rule, exact 60-minute verification, re-verification for traded characters, visible-group reconciliation, and provider-confirmed rename handling apply when those character tools are enabled. Periodic lifecycle, auction, and active-claim presence monitoring remain rollout-pending controls and apply operationally only after the prepared successor legal release is deployed, enforced, and accepted and validation and explicit activation are complete.

If you sign in, you are responsible for protecting access to your Discord account and authenticated session and for activity performed through them. Do not share session credentials, impersonate another person, or attempt to obtain permissions that have not been granted to you.

Character management accepts a character name and uses a public-data provider to derive the current canonical name, world, traded status when available, and other characters voluntarily visible on the same public Tibia account. Public results may be cached, incomplete, delayed, or unavailable, and hidden characters cannot be discovered. You choose which characters are added to your library.

For Tibia Claims purposes, a character and every sibling currently listed with it in the same successful public Tibia account response form one visible character-account group. The group may be actively associated with only one Tibia Claims account. If several people share control of one Tibia account, they must choose one Tibia Claims account to represent that group; Tibia Claims cannot determine their private sharing arrangement and may place conflicting or repeatedly transferred groups under review.

You may request control verification for an added character. Tibia Claims gives you a short-lived code, with its exact expiry displayed when issued, to place exactly in that character's public Tibia.com Comment. The backend then uses its public-data provider to check it. The provider may take a few minutes to reflect a newly saved Comment. The code is public while it remains there and may be removed after a successful check. Use only the code generated while signed into your own Tibia Claims account; do not place passwords, session details, or other secrets in the Comment. Verification attempts may be limited, and a check may fail if the code expires, public data changes, or the provider is unavailable.

A successful verification gives every selected saved sibling returned in the same successful response the same VERIFIED status as the code-bearing character. Library selection does not permit another Tibia Claims account to keep a conflicting active association with any observed sibling: those associations may be made inactive even when you do not add that sibling to your own library. Earlier associations are soft-revoked rather than erased, and limited verification, reassignment, and integrity history may be retained.

A recently traded marker does not by itself prevent a new owner from verifying a character, and a fresh successful verification may supersede an earlier account association. A character disappearing from a sibling list may instead have been hidden, so absence alone does not prove a transfer; Tibia Claims may require direct re-verification or manual review. When Tibia's public data confirms former-name continuity, a rename may update the existing character record rather than create a new one while preserving its verification and accepted claim identity.

When active-auction monitoring is enabled, an active verified character reported as recently traded may be checked against public current auctions. A matching listing may place the character on an auction hold and prevent protected claim actions. The hold is not removed merely because the listing later disappears; fresh direct verification may be required. Monitoring or provider errors do not prove continued ownership or that no auction exists.

A VERIFIED label records that the public-comment and visible-group check succeeded at the stated time. An UNVERIFIED character cannot be used to make a claim and is not presented as a possible claimant. Verification does not prove a person's civil identity, guarantee continuing control, grant Discord rank, satisfy a server authority's separate eligibility rules, or approve a claim. Characters from worlds without a supported claim board may be stored for account convenience but cannot be presented as usable on that board. No legacy character-assignment import is provided.

Removing a character makes that active association unavailable while preserving limited integrity history. Superseding an association through a successful conflicting proof likewise makes it unavailable to the former account while preserving verification, removal, reassignment, and integrity history. Claims are bound to the submitting Tibia Claims account and its character-assignment version; a character reassignment does not transfer those claims to the new account. Signing out does not delete your account, and account suspension or deletion may not remove public board information or reservations retained independently by a game-server authority.

Active-claim presence collection, automatic no-show cancellation, and its Discord message are not active today. The technical and successor-legal-copy foundations exist, but the feature remains disabled pending deployment and enforcement of that release, focused validation, data-retention and account-deletion checks, reacceptance, and staged canary activation. The existence of monitoring data structures or this future-facing description does not mean that a character is currently being watched or that a claim will currently be cancelled for absence.

If activated, presence monitoring will apply only to a real VERIFIED character assignment attached to that claimant's currently active native Tibia Claims reservation. It will not monitor future reservations before they start, unrelated saved characters, Nevia claims, or synthetic Test Characters. Tibia Claims may use independently fresh, complete public world information to classify only that bounded target as online, offline, or unknown. A provider timeout, failure, stale or partial response, ambiguity, maintenance condition, or other unknown result breaks confirmed absence and starts no cancellation timer.

A native claim may be cancelled only after at least 600 seconds, or 10 minutes, of uninterrupted confirmed absence. The backend must recheck the active claim and current verified assignment and apply the ordinary authoritative active-cancellation accounting and claim-now cooldown; the collector cannot make that decision. For a scheduled claim, only that claim's applicable booked duration is retained, while elapsed claim-now use remains used. A private Discord direct message will be queued after a committed cancellation to explain the claim and accounting result. Delivery failure does not reverse the cancellation.

When this feature is active, deleting the Tibia Claims account stops new monitoring, removes current targets, absence state, routine observations, recipient identifiers, and pending monitoring messages, and cannot generate a post-deletion message. Only minimized, detached claim-history evidence needed to explain a completed cancellation may remain under the Privacy Policy.

Each server enables claim capabilities separately. External rank lookup and reservation submission to an independently operated authority such as Nevia are not active unless expressly identified in that server's area. Native Tibia Claims servers, including Karmeya, may enable backend-owned reservations after their rules and access controls are configured.

Every supported server begins with its own active base rules. An authorized administrator may place one Tibia Claims account in one server-scoped group or in the reserved BLACKLIST. That choice applies to all current and future verified characters of the account on that server world; it does not grant authority over another server.

For a native server with manual Discord-role synchronization enabled, an authorized administrator may designate one bound Discord guild, select ordinary roles, assign an explicit Tibia Claims priority, and synchronize those roles into server groups. After you accept the current release, a requested synchronization may ask Discord only for your current role identifiers in that designated guild and retain the highest-priority selected app-group association. It applies to your currently verified characters on the server's Tibia world and may automatically apply to a character you verify there later, without another Discord lookup. Role names and Discord role position do not define your claim rights. Discord is read only after an administrator requests and confirms synchronization; there is no automatic, sign-in-time, verification-time, or claim-time Discord lookup.

If an account is blacklisted on a server, the service may disable claim controls for all its verified characters there and direct the user to the server's administrators. Administrators may apply a temporary or indefinite restriction only for legitimate community operation, must record a non-sensitive reason, and must not use restrictions to harass, discriminate unlawfully, expose private account relationships, or evade the audit trail.

A timed strike may block all claim capabilities for the account on that server or only ordinary, right-now, or advance claim capability. Matching active or future native claims across its verified characters may be cancelled when the administrator confirms the preview; unrelated capability remains available for a specific strike. Expiry or early removal permits new matching requests but does not restore a cancelled claim.

For a server whose external community service remains authoritative, a Tibia Claims group or blacklist controls only the Tibia Claims interface unless and until that external service supports an approved enforcement and reconciliation integration. Tibia Claims will not represent an external cancellation as successful when no such integration exists.

A reservation request is not approved until the designated authority returns an accepted result: the Tibia Claims backend for a native server, or the identified external authority for an externally managed server. A browser or Discord acknowledgement, timeout, or pending response is not approval. Tibia Claims does not grant an in-game right to occupy a spawn or guarantee hunting priority.

The same Tibia Claims Discord bot may be installed in multiple approved Discord guilds. The backend binds each guild's immutable Discord ID to one supported claim server; more than one guild may be bound to the same server. Commands in direct messages, User Install contexts, or unbound or revoked guilds are not authorized. You must not copy, impersonate, invite, or use the bot to bypass Tibia Claims account, character, server, administrator, restriction, or rate-limit controls.

The bot is only a user interface to the Tibia Claims backend. A rulebook-status response is informational and creates no reservation. A real native claim command, where enabled, uses the same backend claim operation as the website. It is accepted only when the backend commits and returns an accepted result; Discord displaying, deferring, or acknowledging the command is not approval.

Commands may be retried safely using their Discord interaction identifier. You must select only characters you are authorized to use and provide accurate command options. An administrator scheduled-eligibility reset is effective only after the backend rechecks current server scope and commits the confirmed allowance epoch; it does not cancel existing claims, clear claim-now cooldowns, restore claim-now allowance charges, or waive other server rules. A confirmed exact-claim refund instead cancels only the selected eligible claim and returns only the scheduled minutes currently charged by it; it does not erase the claim or audit history, refund another claim, or waive other restrictions. Private replies reduce ordinary channel visibility but are still processed by Discord. The bot may show its own temporary character-verification code there; do not submit passwords, session credentials, or unrelated private information.

A signed-in user's favourite hunting grounds are saved separately for each Tibia Claims account and claim server and may be managed through a supported website or Discord interface. You must not use favourites, notification preferences, or bot commands to evade access controls, rate limits, or another server's restrictions.

Where the feature is enabled and supported, you may request a Discord reminder for an eligible scheduled claim or enable availability messages for a favourite hunting ground. Saving a favourite does not guarantee that availability alerts are supported for an externally managed source. A notification is informational only: it does not create, extend, edit, preserve, or cancel a reservation and does not establish priority over another request.

You are responsible for keeping access to your linked Discord account and allowing direct messages if you want to receive them. Delivery can be delayed, duplicated, rejected by Discord, or unavailable, and Tibia Claims does not guarantee that a reminder or availability message will arrive. Changing a preference cannot recall a message that Discord has already accepted or that is already being processed.

The project operator holds the Super Administrator role. Only the Super Administrator may assign, change, suspend, reactivate, or revoke Server Administrator access. For this purpose, the Super Administrator may privately search limited Discord sign-up details held through Supabase, including display name, username, and email, to select the intended registered account. Those details must not be used for unrelated contact, profiling, or disclosure. A Server Administrator may use administrative features only for the specific servers assigned to that Discord identity and receives no authority over another server, the Super Administrator role, the registered-user directory, infrastructure secrets, or operator-only recovery.

Administrators must use their access only for legitimate operation of the assigned community, protect their Discord account and session, provide an accurate non-sensitive reason for each recorded authorization, rule, group, membership, role synchronization, strike, blacklist, allowance-reset, or exact-claim refund action, review every preview and confirmation detail before approving a mutation, and follow these Terms and applicable law. The optionless Test-character reset uses a fixed command reason and affects all ten shared Test allowance scopes for the current Test claim day. Administrators must not use an exact-claim refund, role mapping, strike, or blacklist to give preferential treatment, share access, attempt self-escalation, assign permissions through an unauthorized route, misuse member information, infer or disclose hidden account relationships, or include secrets or unrelated personal information in an administrative reason.

Administrator authorization actions are recorded in a security audit history. Suspension or revocation takes effect for subsequent protected requests but does not erase that history. Tibia Claims may preserve the limited audit record needed to prove who had access, investigate misuse, resolve disputes, and secure the service. Account deletion removes the live Supabase actor link from retained role-source configuration and mapping audit, but may leave the bounded Discord actor and rank, action reason, app mapping snapshot, and time needed to prove the earlier administrative action.

Use the service only for personal, lawful participation in supported claim communities. You must not attempt unauthorized access; probe or bypass authentication, authorization, firewall, or rate limits; overload or disrupt the service; operate duplicate Tibia Claims accounts; deliberately split one visible Tibia character-account group across Discord identities; evade an ownership review or restriction; submit false or misleading identity, character, transfer, rank, or claim data; automate abusive requests; introduce malicious code; scrape in a way that harms availability; or use the service to harass, threaten, or impersonate another person.

We may restrict or suspend access, reject requests, or preserve relevant records when reasonably necessary to protect the service, users, connected communities, or legal rights. We may cooperate with a relevant authority or lawful request where appropriate.

You remain responsible for information you provide. You authorize Tibia Claims to validate, store, process, transmit, and display that information only as reasonably needed to operate, secure, and improve the requested service features and to comply with law. Do not provide secrets or personal information that a feature does not request.

Character and claimant names selected for a public claim, together with reservation times, may be publicly displayed. Do not submit a character or team member without any authorization required by the relevant community rules.

When contributing hunting-ground information, provide only observations you are entitled to share and describe the relevant level, vocation or party, hunt mode, pricing, boosts, and other material context accurately. When a full Tibia-window screenshot is required, it must show the selected character, equipment, Hunt Analyzer, and Input Analyzer from that session. Do not upload an inappropriate, unrelated, reused, fabricated, or deliberately misleading image, and do not paste passwords, session details, private conversations, or unrelated personal information into a contribution or Hunt Analyzer field. Analyzer assistance is a convenience; you remain responsible for reviewing and confirming the normalized preview before submission.

A hunting-ground contribution is reviewed before it can affect public information. Tibia Claims may deny or withdraw inaccurate, unsafe, misleading, duplicate, unsupported, or outdated material. Submitting an observation does not guarantee acceptance, publication, attribution, or permanent retention. You permit Tibia Claims to review, normalize, store, and use accepted contribution values and source material to operate and improve global hunting-ground information, including combining compatible accepted observations into anonymous summaries or ranges. Contributor identity and private Analyzer evidence are not part of that permission for public display.

Discord, Supabase, Vercel, TibiaData, Tibia.com, Nevia, and other external server authorities are separate services with their own terms, privacy policies, availability, and decisions. Tibia Claims is not responsible for their systems or for content reached through external links.

You must comply with the terms of the services you use. Loss of access to Discord or a connected community may prevent access to some Tibia Claims features.

The Tibia Claims interface, branding, software, and original site content are protected by applicable intellectual-property laws. You may not falsely claim ownership or endorsement. Third-party names, logos, game content, trademarks, and community data remain the property of their respective owners.

Tibia, related game assets, and related marks belong to CipSoft GmbH or their respective owners. Tibia Claims is an independent fan-made community project and is not affiliated with, operated by, sponsored by, or endorsed by CipSoft GmbH.

The service is provided on an as-is and as-available basis. Features may be changed, limited, suspended, or discontinued, including when an external data source or authority is unavailable. We do not guarantee uninterrupted, secure, or error-free operation or permanent preservation of account or board data.

You may stop using the service at any time. A signed-in user may permanently delete the Tibia Claims account from the Delete account section in Account info after reviewing the consequences and typing the displayed confirmation phrase. A sufficiently recent verified session is required. Server Administrator access is revoked as part of deletion; the designated Super Administrator must transfer platform control before deleting that account.

Account deletion cancels active and future native claims and removes the current login, profile association, saved character assignments and verification, favourites, notification choices, live server groups and restrictions, enabled monitoring state and pending monitoring messages, and other live account access described in the Privacy Policy. It does not erase minimized previous claim records or necessary detached security/integrity evidence.

We may suspend or terminate access for a material or repeated breach of these Terms, including repeated fake, duplicate, inappropriate, or misleading contribution evidence, a security risk, legal requirements, or withdrawal of a connected service. A temporary claim suspension cancels active and future native claims and blocks new native claims and spawn-data contributions for its stated period. Permanent account termination also closes the account and prevents the same Discord identity from registering another website or Discord-only Tibia Claims account. Voluntary account deletion is separate and does not itself impose that re-registration block. Provisions that by their nature should survive, including intellectual-property, disclaimer, liability, and record-integrity provisions, continue to apply.

To the fullest extent permitted by law, Tibia Claims and its operator disclaim implied warranties and are not liable for indirect, incidental, special, consequential, or similar losses arising from use of or reliance on the service, inaccurate or delayed board data, rejected or duplicated requests, downtime, player disputes, loss of in-game opportunities, or third-party services.

Nothing in these Terms excludes warranties, remedies, consumer rights, or liability that applicable law does not allow to be excluded or limited.

We may update these Terms as the service evolves. Each release identifies its effective date and version. When a change is material, authenticated website and Discord features may require you to review and expressly accept the new release before you can continue using them. Public claim boards may remain available without acceptance. If you do not agree to a new release, do not accept it and stop using authenticated features.

Questions about these Terms or account-deletion requests can be raised with an administrator through the official Tibia Claims Discord server. Do not include passwords, verification codes, tokens, session details, or other secrets in a public channel.

• Contact Tibia Claims on Discord