Privacy Policy

Effective and last updated: October 17, 2026

This Privacy Policy explains what personal information [LEGAL NAME OF THE PERSON OR COMPANY OPERATING GAMERS DB] ("we", "us", "Gamers DB") collects when you use the Gamers DB website, its APIs, and the Gamers DB Desktop Parser (together, the "Service"), what we do with it, who can see it, and the choices you have. Please read it carefully. By using the Service you acknowledge the practices described here.

Contents

1. Who we are and what this policy covers
2. Information we collect
3. How we use information and our legal bases
4. What is public and who can see what
5. The Desktop Parser
6. Cookies and browser storage
7. How we share information
8. Retention
9. Security
10. Your choices and rights
11. Additional information for U.S. state residents
12. Additional information for the EEA, UK, and Switzerland
13. Children
14. Where your information is processed
15. Games, trademarks, and other people's information
16. Changes to this policy
17. Contact us

1. Who we are and what this policy covers

Gamers DB is a community game-knowledge platform that publishes game databases (such as items, spells, NPCs, and tradeskill recipes) and lets players sync character, guild, and combat-parse information from their own computers using the Desktop Parser. For the personal information described in this policy, [LEGAL NAME OF THE PERSON OR COMPANY OPERATING GAMERS DB] is the "controller" (in the language of European and UK law) or the "business" (in the language of U.S. state law).

Mailing address: [MAILING ADDRESS]. Privacy contact: [PRIVACY CONTACT EMAIL]. We have not appointed a Data Protection Officer.

This policy applies to information collected through the Service. It does not apply to third-party sites or services that we link to or that you use to sign in (see How we share information).

2. Information we collect

2.1 Information you give us

• Account details. Email address, display name, and password (if you register with a local account). Passwords are stored only as a salted one-way hash; we cannot read your password. If you turn on two-factor authentication, we also store your authenticator key and your unused one-time recovery codes so we can verify your sign-in codes; we record when two-factor authentication is turned on, off or reset in our security log. If you ask to change your email address, we keep the requested new address until it is confirmed or the request is cancelled, and we record password resets, password changes and email changes in the same log (with the addresses partially masked).
• Sign in with Discord. If you choose to sign in with Discord, we ask Discord for the identify and email permissions only, and receive your Discord user ID, username, and email address. We do not request your servers, friends, messages, or any other Discord data.
• Profile preferences. Your chosen site theme and time zone.
• Game data you choose to sync or upload from the Desktop Parser, described in Section 5, including characters, guilds, inventory, spellbook, faction, achievement, recipe and real-estate information, combat parses, triggers, and (if you enable it) live DPS and live chat streams. If an administrator has given your account access to the Item or Recipe Collector, this also includes item and tradeskill recipe data read from your running game client, as described in Section 5.
• Ownership claims and delegations. Character claims you submit, and access you grant to other users for characters you own.
• Messages to us. Anything you send us when you contact us.

2.2 Information collected automatically

• Activity and security logs. Whether or not you are signed in, when your browser or the Desktop Parser calls our API (which includes most page data loads) and when the site sends its periodic "still active" signal, we record your IP address, browser/user-agent string, the API path requested, the response status, a session identifier, and timestamps. If you are signed in we also record your account, display name, and a partially masked version of your email address. Query-string values are redacted from these records by default. Administrators can view these logs.
• Server and network logs. Our web servers and the servers that host downloads and images (including the Desktop Parser installer and update files) record standard request information, such as IP address, request time, requested file, and user agent.
• Cookies and similar technologies described in Section 6.
• Roles and permissions assigned to your account (for example, standard user or moderator).
• Account lifecycle log. When an account is created, has its email confirmed, is scheduled for deletion, has that deletion cancelled, or is deleted, we record the event time, whether the account signed up locally or with Discord, the roles it held, whether its email was confirmed, how many days it existed (on deletion), and the reason you chose, if you chose one from the list. We use it to understand sign-ups and retention. These records contain no email address, name, IP address, or account ID, are linked to each other only by a random key, and are kept after an account is deleted.

2.3 Summary table

2.4 What we do not collect

• We do not ask for, read, or store your game-account login credentials (for example, your EverQuest or Pantheon account password).
• We do not collect payment card details. The Service does not currently take payments.
• We do not collect precise geolocation, and we do not knowingly collect information classified as sensitive under European law (such as health, biometric, or political-opinion data).
• We do not read the private files on your computer other than the game log, export, and settings files you point the Desktop Parser at.

3. How we use information and our legal bases

We use personal information to:

• create and manage your account, authenticate you, and keep you signed in;
• provide the Service, including character, guild, ranking, parse, and trigger features;
• send account-related emails such as email confirmation, password reset links, email-change confirmations, and security notices when your password or email address is changed (we do not currently send marketing email; if that changes we will ask for your consent where the law requires it and always provide an unsubscribe option);
• protect the Service and its users: detect and investigate abuse, fraud, unauthorized access, and violations of our rules, and enforce access controls;
• diagnose problems, measure capacity, and improve the Service;
• comply with law and respond to lawful requests; and
• exercise or defend legal claims.

Where European or UK law applies, our legal bases are: performance of a contract (providing the Service you asked for); legitimate interests (security, abuse prevention, troubleshooting, and running a public game-data platform, balanced against your rights); consent (for optional features you turn on, such as live streaming, which you can withdraw at any time by turning the feature off); and legal obligation.

We do not use your personal information for automated decision-making that produces legal or similarly significant effects.

4. What is public and who can see what

Character ownership is decided by explicit server-side rules. Being seen in another player's log, roster, or parse does not make you the owner of that character, and we treat those sightings as observations only.

Live chat warning. Chat streaming relays the chat lines your game client writes to its log for the streamed character. Depending on your in-game settings, this can include say, group, raid, guild, channel, and tell (private message) lines, including messages written by other people. Turn streaming on only if you are comfortable with that, and only if you have the right to share the conversations captured. You can turn streaming off at any time in the Desktop Parser.

5. The Desktop Parser

The Desktop Parser is a Windows application you install on your own computer. Most of what it does happens locally. What leaves your computer depends on what you choose:

• Sign-in. The Parser opens an embedded browser (Microsoft Edge WebView2) to sign you in on the website, then keeps a session using short-lived access tokens and single-use refresh tokens. We store only a SHA-256 hash of each refresh token. Signing out revokes your desktop tokens and clears the embedded browser's data.
• Local data. Game log files, parse history, overlay and trigger settings, and other preferences are stored on your computer. Reading your game logs does not by itself send them to us.
• Reading the running game client. The Parser can read specific character values (such as stats, equipment, inventory, spells, and guild information) from the memory of the game client running on your computer, and from files the game writes when you use its export commands. It reads; it does not modify the game.
• Syncing to the website. Character, inventory, guild, spellbook, faction, achievement, recipe, and real-estate information is uploaded only when you start a sync or enable a sync option for the relevant character. Guild roster and guild-bank uploads and trigger push/pull are deliberate, user-initiated actions. Uploaded character data becomes publicly viewable as described in Section 4.
• NPC observations (on by default). While "Contribute EverQuest NPC observations" is enabled in the Parser settings, the Parser sends what it sees of the game world to build the public NPC database: NPC names and zones, loot drops, vendor items and prices, what merchants offer to pay for items you sell to them (the item, merchant and quoted price, not what or how much you actually sold), and which factions an NPC raises or lowers when it dies or when you complete a quest with it. The names of the zones you are in (and, when your game client is running, the zone's short name) are also noted, with your account ID, so staff can check the zone list against the game's own names; a zone name is only used once several different players have reported it. These records contain no chat and no character name and are shown publicly without any link to you; we keep your account ID with them only to prevent duplicates and to investigate abuse. You can turn this off at any time.
• Item and Recipe Collectors (only for accounts an administrator has given access). These help keep the public item and tradeskill databases accurate. If your account has access, the Parser reads game data your running game client has already loaded: item details (such as names, stats, effects, and prices at a merchant you open) for items in your gear and bags or that you inspect, link, loot, or browse; and tradeskill recipes (recipe numbers, names, trivials, container types, and ingredient names and icons) that your Tradeskill window has searched or shown. It reads a few seconds after moments such as zoning, looting, a death, opening a merchant, or a recipe search, combine, or newly learned recipe, and whenever you press Scan or Read recipes. Only items and recipes that are new or differ from our databases are sent, together with your account ID, the character (server and name) whose game client showed them, and the game version (its version label and a fingerprint of the game's program file). For items, the Parser also sends a copy of the item's raw game data with all memory addresses removed, so fields we learn to read later can be filled in without scanning again. These submissions go to an administrator review queue, where administrators can see which account and characters submitted each one. Approved data becomes part of the public item and tradeskill databases and their public change history, without your account or character name. You can turn automatic scanning, automatic submission, and recipe collection off in Parser Settings under Contribute.
• Parse uploads. When you upload a parse, we store the encounter summary and analysis data you selected (participants, damage, healing, timelines, and related tables). Parses can contain names of other players and NPCs.
• Live streaming (off unless you enable it). Live DPS and live chat streaming send data to our servers continuously while enabled and while the Parser is running.
• Updates. The Parser periodically contacts our download server to check for and download new versions. That server sees your IP address and the app version in its request logs.

6. Cookies and browser storage

We use a small number of cookies and browser-storage entries. We do not use advertising cookies, and we do not use third-party analytics or cross-site tracking.

You can block or delete cookies and site data in your browser settings. Blocking the required cookies will prevent you from signing in; blocking preference cookies means your choices will not be remembered. Because we do not track you across other sites, "Do Not Track" and Global Privacy Control signals do not change how we handle your data; we do not sell or share personal information for advertising in any case.

7. How we share information

We do not sell your personal information. We share it only as follows:

• With other users, as described in Section 4 (for example, public character pages and live streams you enable).
• Service providers that help us run the Service and act on our instructions: server and network hosting, and our email-delivery (SMTP) provider, which receives your email address and the message content when we send you account emails. The fonts, scripts, and stylesheets on our pages are served from our own servers, and we do not load advertising or analytics networks. Occasionally staff-supplied content, such as artwork or news images, may be loaded from another website, which would then see your IP address like any site you visit. The EverQuest Dev Tracker shows pictures that EverQuest staff attached to their forum posts directly from Daybreak's own image servers (assets-cdn.daybreakgames.com and the EverQuest forums), so those servers see your IP address and browser details when you view a post that has a picture; we ask your browser not to send them the address of our page, and pictures hosted anywhere else are shown only as links.
• Discord, if you choose "Sign in with Discord." Discord's handling of your data is governed by Discord's own terms and privacy policy.
• Administrators and moderators of Gamers DB, who can access account and activity information to the extent their role requires (for example to manage users, resolve character claims, or investigate abuse).
• Legal and safety. We may disclose information where we believe in good faith that disclosure is required by law, subpoena, or court order, or is necessary to protect the rights, property, or safety of Gamers DB, our users, or the public, or to enforce our rules.
• Business transfers. If Gamers DB is involved in a merger, acquisition, financing, or sale of assets, personal information may be transferred as part of that transaction, subject to this policy or a successor policy that provides at least equivalent protection.
• With your consent or at your direction.

We may also publish aggregated or de-identified statistics (for example, counts of characters or rankings) that do not identify you.

8. Retention

• Account information: kept while your account is open. When you delete your account it is disabled immediately and removed after a 14-day grace period, during which signing in again cancels the deletion. After the grace period your account, sign-in details, activity and session records, character claims and access you granted, your Terms acceptance record, trigger library and shared triggers, and saved parses (including those published to a guild) are permanently deleted, apart from the limited records described in Section 10.
• Activity events: deleted automatically after 30 days. Activity sessions: deleted automatically after 14 days. These are current defaults and may be shortened or extended for security or legal reasons.
• Traffic summaries: each day we also keep totals only (how many requests and page views, how many errors, how many distinct visitors, which parts of the Service were busiest and how fast they answered) so administrators can see how the Service is used and how its database is growing. These totals contain no account, address or page-level information and cannot be traced to a person; they are deleted after 2 years.
• Server and network logs: kept for a limited period for security and troubleshooting.
• Synced game data, parses, and triggers: parses and triggers are kept until you delete them or your account is deleted. Character pages are built from information synced by players and from what other players' logs show, so they stay on the site as unclaimed when your account is deleted, until removed by an administrator or as part of a verified removal request. Parse archives are subject to per-account limits.
• Item and Recipe Collector submissions: kept, with the submitting account ID and the characters that saw them, while they are reviewed and afterward so that data an administrator already rejected is not queued again. Raw item data is kept per game version so newly understood fields can be filled in. When your account is deleted, your account ID and the characters are removed from these records (kept only as counts, so confirmations already made still count); the approved game data itself stays in the public databases.
• Desktop tokens: access tokens expire quickly; refresh tokens are consumed and replaced each time they are used and are revoked when you sign out.
• Account lifecycle log: kept indefinitely. It holds no information that identifies you (see Section 2.2).
• Backups: deleted data may remain in encrypted or access-restricted backups for a limited time before being overwritten.
• Legal holds: we may keep information longer if needed to comply with law, resolve disputes, or enforce our rules.

9. Security

We use administrative, technical, and organizational safeguards designed to protect personal information, including encrypted connections (HTTPS), one-way password hashing, hashed storage of desktop refresh tokens, access controls that deny access by default and grant it by role and ownership, and audit records of administrative role and permission changes. No online service can be completely secure, and we cannot guarantee the security of your information. If a breach affects your personal information, we will notify you and the appropriate authorities where the law requires. Please use a strong, unique password and keep your devices up to date.

10. Your choices and rights

Regardless of where you live, you can:

• Access and correct your account details on your profile page, or ask us for a copy of the personal information we hold about you.
• Delete your account. Choose Delete account on your profile (Profile > Security). You confirm with your password (and a two-factor code if you use one), or, if you sign in with Discord, with a link we email you. Your account is disabled and every session, including the Desktop Parser, is signed out right away, and it is permanently deleted after 14 days. Signing in again during those 14 days cancels the deletion. You can also delete a single parse yourself, or ask us at [PRIVACY CONTACT EMAIL] to remove a specific character; we will verify your request and respond within 30 days.
• Control what you sync. Do not sync characters you do not want public, and turn off live DPS and chat streaming in the Desktop Parser whenever you like.
• Sign out and revoke sessions. Signing out of the Desktop Parser revokes your desktop tokens.
• Manage cookies through your browser settings (see Section 6).
• Unsubscribe from any non-essential email using the link in the message. Account-security emails will still be sent.

Deleting data removes it from our active systems; copies that other people or search engines already saved are outside our control. Deleting your account releases your character claims but does not delete the characters themselves, which other players' logs also describe; if you are the player of a character and want it removed from public pages, contact us and we will handle the request after verifying it. Contributions you made to the shared game databases (such as confirmed item, recipe, NPC, and zone data) stay, with your account ID removed. We may keep limited records where required by law or to prevent abuse, and the account lifecycle log described in Section 2.2, which does not identify you. We will not discriminate against you for exercising your rights.

11. Additional information for U.S. state residents

If you live in California, Colorado, Connecticut, Virginia, Texas, Oregon, Utah, or another U.S. state with a comprehensive privacy law, you may have the rights to know/access, correct, delete, and obtain a portable copy of your personal information, and to opt out of the sale or sharing of personal information and of targeted advertising or profiling. You can delete your account yourself (Profile > Security); for the other rights, email [PRIVACY CONTACT EMAIL]. We will verify your identity by matching your request to the email address on your account. You may use an authorized agent; we may ask for proof of authorization. We respond within 45 days (and may extend once by a further 45 days where the law allows). If we deny your request you may appeal by replying to our decision with the word "Appeal," and we will respond within the time your state's law requires.

Sale, sharing, and targeted advertising. In the past 12 months we have not sold personal information or shared it for cross-context behavioral advertising, and we do not knowingly sell or share the personal information of anyone under 16. We do not use or disclose sensitive personal information for purposes other than those permitted by law (we collect account log-in credentials, which we use solely to authenticate you).

Categories of personal information we collected in the past 12 months (as defined by California law), and the categories of recipients:

12. Additional information for the EEA, UK, and Switzerland

If the GDPR, UK GDPR, or Swiss data-protection law applies to you, you have the right to access, rectify, erase, restrict, and object to the processing of your personal information, to data portability, and to withdraw consent at any time (without affecting earlier processing). You can erase your account yourself from Profile > Security (see Section 10); to exercise any other right, contact [PRIVACY CONTACT EMAIL]; we will respond within one month (extendable by up to two further months for complex requests, in which case we will tell you). You also have the right to lodge a complaint with your local data-protection supervisory authority; we would appreciate the chance to address your concerns first.

Providing account details is necessary to create an account; if you do not provide them we cannot provide an account. Providing game data is optional; if you do not sync, the related features will not be available for you.

13. Children

The Service is not directed to children under 13, and you must be at least 13 years old (or the higher minimum age of digital consent in your country, up to 16) to create an account. When you create an account, whether with an email address or with Discord, you must confirm that you meet this requirement and accept our Terms of Use. We do not ask for your birthdate or an ID, so we rely on that statement. We do not knowingly collect personal information from children below that age. If we learn that an account belongs to someone below the minimum age, we remove it and erase the data attached to it straight away, the same way as a deletion you request yourself except without the grace period. The account lifecycle log records only that such a removal happened, with no information that identifies the person. If you believe a child has given us personal information, contact [PRIVACY CONTACT EMAIL] and we will delete it.

14. Where your information is processed

Our servers are located in [COUNTRY WHERE THE SERVERS ARE LOCATED]. If you access the Service from another country, your information will be transferred to, stored, and processed in [COUNTRY WHERE THE SERVERS ARE LOCATED], where data-protection laws may differ from those of your country. Where European, UK, or Swiss law applies, we rely on the transfer being necessary to provide the Service you have requested and, where applicable, on other lawful transfer mechanisms. Because character pages are public, information you sync can be viewed from anywhere in the world.

15. Games, trademarks, and other people's information

Gamers DB is an independent fan project. It is not affiliated with, endorsed by, or sponsored by Daybreak Game Company LLC, Visionary Realms, Inc., or any other game publisher. EverQuest, Pantheon: Rise of the Fallen, and other game names and marks are the property of their respective owners and are used only to identify the games covered.

Game data on Gamers DB (character names, guild names, chat lines, and combat logs) contains names that other players use in the game world. We treat these as in-game handles, not as real-world identities, and we do not try to link them to real people. If you believe information about you or your character was published without your permission, contact us and we will review it promptly.

16. Changes to this policy

We may update this policy from time to time. We will post the new version here with a new "last updated" date. If a change is material, we will give additional notice (for example, by email to the address on your account or a notice on the site) before it takes effect where the law requires. Continuing to use the Service after a change takes effect means you accept the updated policy, except where the law requires your fresh consent.

17. Contact us

Questions, requests, or complaints about this policy or our handling of your personal information:

[LEGAL NAME OF THE PERSON OR COMPANY OPERATING GAMERS DB]
Email: [PRIVACY CONTACT EMAIL]
Mail: [MAILING ADDRESS]