DragonBreak Online is a free, unofficial roleplay server for The Elder Scrolls V: Skyrim Special Edition, operated by the DragonBreak Online team ("we," "us," or "our") from the United States. DragonBreak Online is for players 18 and over.
This Privacy Policy explains what information we collect, why we collect it, how we use it, and how you can request access or deletion.
1. What We Collect
We collect only information reasonably necessary to operate, secure, troubleshoot, and moderate DragonBreak Online.
Discord account
When you log in through Discord, we may receive:
- Discord user ID
- Username
- Server roles and permissions
Connection information
Our game server, launcher downloads, and website may receive or record:
- IP address
- Connection or access times
- Basic connection information needed to operate and secure the service
- A one-way code made from your PC's Windows machine ID, used only to enforce bans, to keep referral rewards fair and to keep hold elections to one vote per person (we never keep the ID itself)
Ban enforcement check
When you press Play, the launcher sends a one-way code made on your PC from its Windows machine ID. The launcher never sends the machine ID itself for this check, and we store only a keyed scramble of the code that means nothing outside DragonBreak. Older launchers, released before this check, also try to send the machine ID itself when you log in; our servers turn that request away and do not keep the ID. We use the code to spot a banned player who comes back on another account, and for the referral and election checks described below; we do not use it for anything else. For bans, a match is never proof on its own: staff review it, and players who share a PC are not banned because of it. We also read the date your Discord account was created, which is part of your Discord user ID. We keep the code for 30 days after the PC was last used to play, or for as long as a ban lasts when it belongs to a banned account, and we delete it when your account is deleted unless the account is banned.
Referral rewards
Every account that plays while referrals are open gets a referral code and a referral link, which is an address on our website that ends in the code. We keep a referral record for each such account: its code, when it was first seen in the game, when it last played and, for an account that is new to the game, its play time in its first 24 hours of play (and after that for as long as its referral is waiting to count). The record also holds the account's referral boosts, how much of each is left, and referral messages waiting to be shown to it. For a player who invites others, it holds when their first referral counted and which referral gave them the carry weight. When referrals open, the game also notes which accounts already exist, so that only accounts made after that can be referred.
When a new account joins with someone else's link or code, its record also holds which account invited it, the code, when and how it was used (through the link, or typed in the game), the date the new player's Discord account was created (read from the Discord user ID), and how far the referral has come: waiting, counted, cannot count, held for review or taken back, with when it was counted, held or taken back. The record also keeps the days the new account played while its referral was waiting, and how long it played on each (the 10 most recent).
When you open a referral link in your browser, we set a cookie that holds the code (see Website cookies) and send you on to our website. Opening the link records nothing else about you or your visit, apart from our normal connection logs. When you then log in through Discord from the launcher, the login opens in your browser, and the cookie tells our sign-in service which code you came with. While that login is in progress, the sign-in service keeps the code next to a one-way scramble of the login's one-time reference, never the reference itself. If the login creates a brand-new DragonBreak account, the sign-in service records the new account, the code, the time and the date your Discord account was created, and passes them to the game server. An account that existed before that login is never linked to a referral through the link. If your browser loses the cookie, or you opened the link on another device, you can type the code in the game instead, in your first 24 hours of play.
A referral counts only for a brand-new account that meets the referral rules, such as the age of its Discord account when it was referred and the time it has played. To keep the rewards for inviting real new players:
- Same PC, only from this version on. We do not use the ban enforcement check codes for referrals before this version of the Privacy Policy is in effect and players have accepted it. After that, when a new account has played enough to count, we may compare its codes with those of the player who invited it and of the other players the same person invited whose referrals are waiting, held or counted. If they match, the referral is held for review, and a Lead GM or above decides whether it counts. A match never stops a referral on its own. It affects only the referral reward, and it is never a ban or a penalty.
- No address check. We do not compare IP addresses for referrals.
When the PC check runs, it reads the codes we already keep and does not copy them: the referral record keeps only the outcome and, for staff, its reason, such as "PC check". Staff can also take a referral back, and a referral is taken back automatically when the new account is banned; the record keeps when and why. Each step of a referral, and each referral boost or carry weight given or taken back, is also logged for staff, with the accounts, characters and codes involved, but never a PC code or an address. Only staff see the reasons. We use this information only as reasonably necessary to run referral rewards and keep them fair.
Hold elections
To keep each hold election to one vote per person, an account may vote only if it meets the voting rules: the age of its Discord account (read from the Discord user ID), how much it has played and on how many days (counted by the game server; for days before this check began, taken once from the launcher's session reports), and how long the voting character has been a citizen of the hold. For the play-day rule, the game server keeps a list of the days each account played (the 120 most recent) with the account's other game data. When a vote opens, the election notes the play time and play days of each citizen account, and when you vote, it keeps which of your characters voted and when. We also check:
- Same PC, only from this version on. We do not use the ban enforcement check codes for elections before this version of the Privacy Policy is in effect and players have accepted it. After that, once this check is in use, if the codes show that another account on the same PC has already voted in that election, your vote is held for staff review. It is never refused automatically: a Lead GM or above decides whether it counts, records the reason, and can undo the decision. Accounts on one PC also count once toward the number of citizens a hold needs to start an election.
- Same address. We do not check addresses in elections until our game server can see the address each player really connects from. Once it can, staff may also review votes from accounts that last connected to the game from the same IP address. For that, once this check is in use, when you vote the election keeps a scrambled mark of the address you last connected to the game from. A vote is never refused because of a shared address.
Only a Lead GM or above can strike a vote, after reviewing it. They record the reason, and can undo it. The election keeps a record of each held or struck vote: whose vote it was, who decided, when and why. If your vote is held or struck, you are told the outcome in game, or the next time you open the vote.
We use this information only as reasonably necessary to keep hold elections fair.
Characters and game activity
The game server records information necessary to operate the persistent world, including:
- Character information and appearance
- Skills and progression
- Inventory and equipment
- Property and other game assets
- Chat
- Commands and actions
- Trades
- Combat
- Crafting
- Other gameplay activity necessary to operate or moderate the server
Launcher diagnostics
The launcher records a short session report when a play session starts and ends. This may include:
- Whether the session ended normally or with a crash
- Launcher version
- Client version
- Game version
If you choose to submit a problem report, it may additionally include:
- Launcher and game logs, including the game's diagnostic log
- A crash log, when available
- Your description of the problem
- Memory/RAM
- Processor
- Graphics card
- Available disk space
- Windows version
Problem reports are only submitted when you choose to send them or agree to send one after a crash.
Automatic error reports
When the game or the launcher runs into an error, it may send an automatic error report. This may include:
- The error message and where in our code it happened
- The game, client, and launcher versions, and your Windows version
- A short list of your most recent in-game actions, such as menus opened or items used
- Short excerpts of the game and launcher logs, with personal file paths removed
- Your DragonBreak account
For a short time after certain events, such as being downed, the game may also record which movement keys are held and which panels are open, to find input problems. It never records what you type.
Automatic error reports and these input records are used only to find and fix bugs. You can turn them off in the launcher where that option is available, and reports about a game crash ask for your agreement before they are sent.
Character statistics and journal
The game keeps long-term statistics for each character, which you can see in your character journal. These may include:
- Play time and session lengths
- Distance travelled
- Combat counts, such as players downed and defeated, deaths caused by players, and creatures defeated
- Counts of robberies, pickpocketing and time spent in jail
- Trades, dungeons and expeditions completed
- Your character's creation date, and when your account first signed in
These are counts only. They don't record who you traded with or fought.
If you write a backstory, origin or other journal text for your character, we store it with your character. It is filtered for slurs, and staff read it only when a report or ticket involves it.
Accepting these documents
When you accept the Terms of Service and this Privacy Policy in the launcher, we record your account, the version you accepted, the time, and your launcher version.
Thalmor dossiers
Characters who hold certain ranks in the Thalmor faction can keep dossiers: notes they write about named characters, as part of roleplay. A note is stored on the game server with the character it is about, the character who wrote it and the time. Other Thalmor characters of those ranks can read the dossiers in game, and staff can read them when they moderate or investigate a report. Notes are filtered for slurs, and every note written or struck is logged for staff. A note is kept until a Thalmor of a writing rank or staff strike it.
Bug reports and support
When you submit a /bug report, support ticket, or other report, we may receive the information you choose to provide. A /bug report may include a snapshot of your character or game state at the time of the report.
Voice chat
DragonBreak Online uses a LiveKit voice server operated by us for proximity voice chat.
We do not record or store game voice chat. Voice is transmitted live between players participating in the service.
Other players may independently record gameplay or voice using their own software. We do not control those recordings.
Website cookies
Our website sets a short-lived cookie while you sign in with Discord, and a session cookie while you are signed in. If you open a referral link in your browser, we also set a cookie that holds that referral code for 30 days. Your browser sends it back to us only when it opens our Discord login or another referral link, and we use it only to credit the player who invited you when that login creates a new account. We do not use tracking or advertising cookies.
Information we do not receive
We do not receive or store your:
- Steam account credentials
- Nexus Mods account credentials
- Payment card information
2. Why We Collect Information
We use collected information to:
- Operate your account, characters, and the persistent game world.
- Maintain backups and restore game data when necessary.
- Connect players to the service and protect the service from abuse.
- Investigate cheating, exploits, harassment, and other rule violations.
- Enforce bans and other moderation decisions.
- Run referral rewards: credit the player who invited you, and keep the rewards fair, so that they reward inviting new players, not making extra accounts.
- Keep hold elections to one vote per person.
- Diagnose crashes and technical problems.
- Improve server stability and gameplay systems.
- Respond to support requests and bug reports.
We do not sell your personal information, use it for advertising, or create advertising profiles about you.
We aim to collect and retain only information reasonably necessary for these purposes. Privacy and security commitments made in this policy are intended to describe our actual practices accurately.
3. Third-Party Services
DragonBreak Online relies on third-party services that operate under their own terms and privacy policies.
These may include:
- Discord — authentication, community, communication, and support.
- Steam — your copy of Skyrim Special Edition.
- Nexus Mods — distribution of mods used by the service.
- GitHub — distribution of launcher and related project files.
- LiveKit — live proximity voice communication operated through infrastructure controlled by DragonBreak Online.
- Cloudflare — delivery and protection of our website and the launcher's connections to our servers. Cloudflare processes IP addresses and connection information when you use them.
- Anthropic (Claude) — AI assistants our staff use to help operate, troubleshoot, and moderate the service. They may process server logs, bug reports, and support tickets on our behalf.
We do not control how independent third-party services collect or process information under their own policies.
4. Who Can Access Your Information
Access to DragonBreak information is limited to DragonBreak staff who need it to:
- Operate the service.
- Provide support.
- Moderate players.
- Investigate reports.
- Diagnose and fix technical problems.
- Maintain the service and its security.
Bug reports or moderation information may be shared with appropriate staff or posted to our internal/Discord-based tracking systems when necessary to handle the report.
You may mark a launcher problem report as private when that option is available.
Staff see the full results of the referral and election checks, including why a referral or a vote was stopped or held, and only a Lead GM or above decides a case held for review. Other players never see your PC code, your IP address, or why a check stopped or held your referral or your vote. The player who invited you sees only how far your referral has come (the hours and days played toward it, without your name), whether it is waiting for staff review and whether it counted. If it cannot count, they see only that it "cannot count", with no reason.
We do not share personal information outside the DragonBreak team except when necessary to operate the service through a service provider, when you ask us to do so, or when required by law.
5. How Long We Keep Information
We retain information only for as long as reasonably necessary for the purposes described in this policy.
Our current target retention periods are:
| Information | Target retention |
|---|---|
| Account and active character data | While your account remains active |
| World backups | 30 days |
| Server activity and connection logs | 90 days |
| Ban enforcement check codes | 30 days after the PC was last used to play; for a banned account, while the ban lasts |
| Referral records in the game | While your account exists; erased when your account is deleted |
| Referral sign-ups noted by our sign-in service | Deleted when your account is deleted; otherwise dropped once older than 30 days, the next time a new player signs up through a referral link (checked at most once a day) |
| Referral logins in progress | Until the login finishes; one that never finishes is dropped at the next referral login once it is 30 minutes old |
| Referral cookie in your browser | 30 days |
| Election records of who voted, held and struck votes, the play time checked for voting, and any address marks | Until the hold's next election; the note of which hold your account votes in (one hold per player) is kept with your account's game data |
| Launcher session and problem reports | 180 days |
| Bug-report snapshots | 180 days |
| Thalmor dossier notes | Until struck in game, or by staff |
| Character statistics and journal text | While the character exists |
| Records of accepting these documents | While your account exists |
| Support and moderation records | 2 years |
| Ban records | For the duration of the ban and as reasonably necessary to prevent ban evasion |
| Discord posts | According to Discord and server moderation practices |
Some information may be retained longer when reasonably necessary to investigate abuse, enforce a ban, resolve a dispute, maintain security, preserve backups, or comply with legal obligations.
When information is no longer needed, we intend to delete it or securely dispose of it.
6. Your Privacy Requests
You may contact us to request information about personal information we hold about you, request correction of inaccurate information, or request deletion of your account and personal information.
Requests can be made through:
- A DragonBreak Online Discord support ticket
- [email protected]
Deleting your account permanently removes your DragonBreak characters and ends your ability to use that account.
Some information may remain when we have a legitimate reason or legal obligation to retain it, including information necessary for security, fraud prevention, ban enforcement, dispute resolution, or legal compliance.
If privacy laws applicable to you provide additional rights, we will handle requests according to those applicable requirements. California law, for example, provides certain rights concerning access, correction, and deletion of personal information, subject to exceptions.
7. Changes and Contact
We may update this Privacy Policy as DragonBreak Online develops or our data practices change.
The current version will be published with its effective date. Significant changes may also be announced through the DragonBreak Online Discord.
Privacy questions and requests:
[email protected]
Support:
DragonBreak Online Discord tickets
Last updated: October 17, 2026