Site information

Privacy Policy

How Broken Oath Builder handles your files, shared builds, reports and optional accounts.

Last updated 15 November 2026

Your files stay on your device

Save files, game data, screenshots and the game log you open are processed in your browser. The site does not upload those files. The Save Creator edits eligible offline saves in your browser and gives you a download; you decide whether to copy it into the game folder.

Browser storage

The builder uses local storage and browser storage for loaded character summaries, plans, settings and remembered folder access where supported. This lets you return to your work on the same device. Use the builder's Reset control to remove loaded characters and plans, or clear this site's browser data to remove its saved settings and permissions too. Export anything you want to keep first. When you sign in to an account, this browser also keeps a sign-in token and a note of which plans it has saved to the account; signing out removes the token.

Accounts (optional)

You can sign in with Discord to save your build plans to an account, so they open on your other devices. Everything else on the site works without an account.

What Discord shares. Sign-in asks Discord only for your basic profile (the identify permission): your Discord user ID, username, display name and avatar. It does not give us your email, your servers or your messages, and the builder cannot post anything on Discord. The access Discord grants is used once, to read that profile, and then handed back to Discord.

What we store.

• Your account: a one-way, keyed scramble of your Discord user ID (not the ID itself), the date it was created, the date you last used it, and a counter that limits how often plans can be saved.
• Your plans: each plan you save to the account, as a build code. A plan can include its name, class, level, equipment, skills, passive tree and tree tabs, potions and the notes you wrote.
• Your sign-ins: for each browser you sign in on, a scrambled sign-in token, a short label such as "Windows · Chrome" and its dates.

Your account keeps no Discord username, display name or avatar. At sign-in, your display name passes through our server once to reach your browser, which keeps it to show who is signed in; that sign-in record is deleted as soon as the sign-in finishes, or within the hour if it is never finished.

Who can see it. Plans in an account are private: only browsers signed in to that account can read them. They are not listed anywhere and are not shared with the game's developers or anyone else. The site owner can reach the database to keep the service running; it does not show which Discord user an account belongs to. Sharing a plan with a share link works as described below and is separate from your account.

How long. Plans stay until you delete them or your account. A deleted plan is kept as a deletion note for up to 30 days so your other browsers remove it too. A browser's sign-in ends after 90 days without use. An account that is not used for two years is deleted with its plans.

Your controls. In the account menu (your name at the top right of the Tools bar) you can download all your plans, see your signed-in browsers, sign out, sign out everywhere, and Delete my account, which removes the account, every plan in it and every sign-in at once. You can also remove the builder's access in Discord (User Settings, Authorized Apps). Plans already in a browser stay there until you remove them in that browser.

Accounts are stored in Cloudflare D1. Discord's handling of your Discord account is covered by Discord's privacy policy.

Shared builds

Choosing Copy share link sends an encoded build to our Cloudflare share service so it can create a short link. The build can include the character name, class, level, equipment, skills and passive tree. Anyone with the link can open it; treat it as public. It does not include your original save file or Steam ID. Stored short links have no automatic expiry. A long build code or link can also contain the build itself, so anyone you give that code or link to can read it.

Problem reports and fight checks

Sending a report submits the text you write, the current tab and game-data version, and any fight-check summary shown in the form. A build is attached only if you tick that option; attaching it creates a share link with the access described above. Fight log excerpts are optional too: the form previews the selected combat lines with identifying details removed. The full game log is never uploaded. Review your text and attachments before sending and leave out personal information.

Reports are stored in Cloudflare KV for up to 180 days, unless removed earlier, and are accessible to the site owner through an authenticated tool. Attached build links are stored separately and do not expire with the report. To limit spam, the service derives a daily hash from your IP address and keeps a report counter under that hash for one hour. It does not store your raw IP address with your report.

Hosting, analytics and other services

• GitHub Pages hosts the public site. GitHub and Cloudflare process network request information, including IP addresses, to deliver and protect their services. See GitHub's privacy statement and Cloudflare's privacy policy.
• The builder's public pages use GoatCounter for visitor statistics, including page views, referrers and browser or device information. GoatCounter does not use tracking cookies. See GoatCounter's privacy information. These legal pages do not load the counter.
• The support button loads a Buy Me a Coffee script. Using the donation service is optional and subject to its privacy policy. The builder does not receive payment-card details.
• Reading text from a screenshot downloads Tesseract software and language data from external delivery services such as jsDelivr. Image processing stays in your browser.
• The Ladder displays the game's public API data through our Cloudflare cache. The builder does not upload your local saves to the ladder. Importing a Broked DB short link asks our service to retrieve that shared build from Broked DB.

Accounts are optional. The builder does not sell your data or set advertising cookies. External services have their own data-handling practices.

Your choices and requests

You can use the tools without signing in, sharing a build or sending a report. If you have an account, you can download or delete it yourself from the account menu. To ask about access, correction or removal of a stored report or short link, use the contact page. Include the report reference or share link so the owner can find it. Clearing browser data does not delete information already sent to the share or report service. Copies other people have made cannot be recalled.

If this policy changes, the update date on this page will change.