Saving, sharing, claiming, and your data

Editing happens in your browser. Auto-save to cloud (in Settings, under Character & saving) writes your build online about a minute after you edit, once a valid IGN is set; with it off, saving is manual. A character that shows Not synced exists only in this browser; after a save the status reads Synced just now or Synced Nm ago.

The top bar holds the manual actions: Save (or Load character when no character is open), Sign in, and the character menu — the character's name with a ▾ — with Restore from cloud, Add character…, Switch character, and Claim this character.

Moving to another device or browser? Load the character or restore from cloud before you start editing there. If the cloud copy is newer than the one on this device, the background auto-save pauses instead of overwriting it — restore or load first, then continue on the up-to-date copy.

Builds are keyed by character name, which means anyone who knows your IGN could save over that character's build. Claiming closes that: sign in with Discord on each device you use, then choose Claim this character in the character menu and confirm with Claim it.

From then on, only your Discord account can save that character; anyone else, including you signed out, is refused. Claiming is optional — for purely local use on your own browser you do not need it — but it is the step that matters once a build is worth keeping safe. Sign in on every device you play the tracker from so your claims and identity follow you, not the browser.

To undo it, choose Release claim in the same menu: that frees the slot and removes the protection, and your build is not deleted. If a name is claimed by another account, the warning icon beside your character names who holds it and offers Dispute this claim.

On Gear, enter your IGN and use Share to copy a link to the current build. Share saves the build online first, then copies the link. A share link is a snapshot, not live collaboration: what the recipient sees is the build as it was when you shared, and later edits of yours do not appear.

Opening someone else's link shows their build under a Viewing a shared build banner that says nothing there is saved. Keep as my build in that banner is the one action that adopts it — with an active character it replaces that character's saved build after you confirm — so review what you are adopting before pressing it. Back to your character returns without changes. Until then, nothing you browse writes into your roster (see Shared builds and your roster).

Cloud saves and share links send build data to the service. Screenshot imports, AI generation, and assistant requests also send the inputs needed for those features; a browser-based editor does not mean every feature stays on your device.

Review Terms and Privacy for storage, retention, and contact details. Use Public visibility to control the listing described below, and review the context attached before submitting a screenshot or assistant request.

Keep your own exported backup if you need a recoverable copy of a build. Public visibility, a share link, and a backup serve different purposes.

In Settings under Character & saving, Public visibility has two states: Visible to everyone or Hidden. That choice controls your appearance on the leaderboard and the public character page.

Hidden does not erase everything: a Discord link preview of your character remains available. If what remains matters to you, the terms page spells out the details, and it describes how to request changes to data held about your build.

Use Characters for roster backups:

1. Choose Export All (n) and keep the exported file somewhere you can find on another device.
2. To restore it, choose Import, then Import from Text or Import from File and provide the exported text or file.
3. Review the preview, which lists how many characters are new and how many already exist. Import All (overwrite n duplicates) replaces the duplicates shown; Skip duplicates (n new only) keeps your existing entries. Cancel if the preview is not what you intended.

For a missing or stale build, check the browser, active profile, IGN, server, and region first. Then check the sync status and use Load character or Restore from cloud before editing on another device. If you have an export, review its import preview before replacing records.

Avoid clearing browser data or resetting the build as your first troubleshooting step: that can remove the local copy you are trying to recover.