Skip to content
DP-SECURITYReviewed · 2026-11-19Desktop 1.8 · Companion 1.1.1Lire en français

Security and privacy ​

Trust model ​

D&P is a local, single-user application. The engine is authenticated and restricted to loopback; it is not a multi-user network service. A malicious process already running under your account can read private files: the local cookie does not protect against that scenario.

Lua files are untrusted data. The parser does not execute code, allowed paths and sizes are checked, and imports have structural and count limits. CSV export strings are escaped to reduce spreadsheet formula interpretation.

The native window stays within the local origin. Allowed external links are the intended paths to Wowhead Forever (EN/FR), Undermine Exchange and Umbral Market Forever. The policy is explicit in policy.rs; do not add a generic domain without review.

Artwork or metadata loading may contact an external service. The delivered documentation contains local search and its logo; opening external links is a separate choice. Development tools and audits download dependencies and advisory information.

What stays private ​

engine/state, SavedVariables, transaction exports, account paths, keyed session URLs, diagnostic logs and account screenshots. Git ignores known paths, including engine/Open Forge.html (session key), SavedVariables filenames and dp-*.csv exports. Archives use an explicit file allowlist. Renamed exports, logs and personal screenshots under other names require manual inspection; keep them outside the repository or in ignored private-exports/ and private-screenshots/ directories. Always inspect staged files before committing.

The repository starts private. This does not make committing secrets or real history acceptable. Fixtures are synthetic. A personal backup and a shareable package are separate deliverables.

Reporting and remediation ​

Do not publish sensitive data in an issue. Use GitHub private vulnerability reporting when available, otherwise contact the repository owner directly with a minimal sanitized description. See SECURITY.md for useful report details and rotation steps after key or private-file exposure.

Dependencies are locked and audited; an audit with no known advisories does not prove the absence of vulnerabilities. Windows code signing is not configured. In-game validation remains separate from automated tests.

A local-first advisor. Estimates stay visible.