Data use and retention

Privacy Policy

Effective date: October 4, 2026

Loot Captain is a local-first browser extension for comparing EverQuest gear. This policy explains what the extension stores and what network requests it makes.

Data handled

The extension stores the following in browser-local chrome.storage.local:

Where the browser supports it and the user permits it, "Fresh from file" stores a read-only file handle per profile in extension-local IndexedDB. The browser may ask for permission again. The inventory export and handle are not uploaded; imported item names may still be sent to RaidLoot for missing-stat lookups.

Loot Captain does not collect email addresses, passwords, payment information, precise location, browsing history, analytics identifiers, or advertising identifiers. Character and item names are retained locally and may be sent to RaidLoot only when an item lookup is needed. For a statless class-specific armor token, each selected character's class and a public armor-set query may also be sent to RaidLoot on the first resolution; the resulting set is cached locally. Allakhazam and EQResource are developer-time catalog sources only and are never contacted by the extension.

When a comparison is displayed, the extension renders relevant worn-item and candidate-item names, badges, and stat differences into the DOM of the visited RaidLoot or OpenDKP page. This is local page rendering, not collection of browsing history.

Network use

When the user imports a profile or a profile/comparison needs missing stats, Loot Captain fetches public pages from raidloot.com for profile and item information. An OpenDKP item name may be sent automatically to RaidLoot for an exact-name lookup. For class-specific armor-token resolution, each selected character's class and the public armor-set query are sent only on the first cache miss. Requests do not include authenticated browser credentials or cookies.

On OpenDKP pages, the extension reads visible item UI and page item-data responses to add a local comparison badge. That data is not sent to an OpenDKP server by the extension.

Sharing and sale

Loot Captain does not sell, rent, or share user data with advertisers, data brokers, or other third parties except for the public RaidLoot lookup needed to provide the comparison described above. It has no analytics or tracking service.

Limited Use

Loot Captain uses profile, item, and page data only to provide its single purpose: local EverQuest gear comparison on the current page. It complies with the Chrome Web Store User Data Policy and its Limited Use requirements. It does not use data for advertising, credit, insurance, lending, price discrimination, or unrelated personalization.

Retention and deletion

Local data remains in extension storage until the user deletes a profile, clears extension storage, or uninstalls the extension. Fetched public item stats may be refreshed or replaced automatically.

Deleting a profile attempts to remove its remembered inventory file handle. Missing, moved, or denied handles are forgotten so the next refresh can ask for a file again. Clearing all extension data or uninstalling removes the handles. Clearing only chrome.storage.local may leave the IndexedDB handle data behind.

Security and changes

The extension uses minimum declared permissions for local storage, public RaidLoot fetching, and local HTML parsing. It does not execute remotely hosted code. Policy changes will be published with a new extension release and reflected in the effective date.

Contact

For privacy questions, visit Loot Captain support. Do not include personal or sensitive information in a public issue.