Last updated: 2026-09-16. Operated by Noaa AB.
Vaultseer has two parts: an addon that runs inside World of Warcraft, and a companion program that runs on your own computer. Neither part sends anything to Noaa AB or to applib.dev. There is no account, no sign-in, no analytics, no crash reporting and no telemetry.
What the addon does
World of Warcraft addons cannot use the network, and Vaultseer's addon does not try. It writes a snapshot of your character to the game's saved-variables file on your disk: equipped items, equippable items in your bags, talent loadout, Great Vault options, Mythic+ runs, raid lockouts, currencies and professions. It reads a plan file the companion writes into the addon folder, and it accepts text you paste into it yourself. That is the entire surface.
What the companion sends, and to whom
The companion reads the snapshot and, to build a plan, contacts only the services you configured with your own API keys. Each is optional except the first two.
| Service | What is sent | Why |
|---|---|---|
| Firecrawl | Search queries built from your class, specialisation and game patch; page URLs to fetch | Current guides, tier lists, trinket sims and news |
| Anthropic (Claude) | A text summary of the snapshot (character name, realm, gear, bags, vault options, runs) plus the fetched research | The plan and the answers to your questions |
| Wowhead | Item ids of your vault options and bag items | Exact item tooltips |
| Bloodmallet | Your class and specialisation | Trinket simulation rankings |
| Raider.IO | Your character name, realm and region | Your public Mythic+ record |
| Battle.net API | Your character name, realm and region (only if you add a Battle.net client) | Armory data as a cross-check |
Your API keys are stored in a file on your machine with owner-only permissions and are never written to logs. Each provider's handling of what it receives is governed by that provider's own privacy policy.
Signing in with Battle.net (optional)
If you connect your Battle.net account, the companion sends you to Battle.net to approve access to your World of Warcraft profile. Battle.net then returns you to applib.dev/vaultseer/auth/battlenet/callback, which does one thing: it forwards the one-time authorization code to the companion on your computer over localhost and shows a fallback link if the companion is not running. applib.dev does not exchange the code, does not hold your Battle.net client secret, and does not store the code or any token. The exchange and the token stay on your machine.
The local web page
The companion can serve a page on your local network so you can read the plan from a phone. It is protected by a token generated on first start, it is not reachable from the internet unless you make it so, and it stores nothing beyond what the companion already keeps on disk.
Optional features
Speech uses your operating system's text-to-speech and the game's own voice engine; nothing is sent anywhere. The experimental pixel channel reads a small region of your own screen to pick up a question you typed in game; the capture never leaves your machine and is discarded immediately after decoding.
What is stored on your computer
The snapshot and plan files inside the game's folders, a cache of fetched pages and lookups, the plan and research files the companion writes for debugging, and your keys. Deleting the addon folder, the companion folder and the saved-variables file removes all of it. Nothing is held anywhere else, so there is nothing for Noaa AB to delete on request.
Children
Vaultseer is a tool for World of Warcraft players and is not directed at children. It collects no personal information from anyone.
Changes
If a future version sends anything to Noaa AB or adds a hosted service, this page will be updated before that version ships.
Contact
Privacy questions: support@applib.dev or the support form on applib.dev.
World of Warcraft is a trademark of Blizzard Entertainment, Inc. Vaultseer is an independent project and is not affiliated with Blizzard.