PRIVACY POLICY & PERMISSION AUDIT
Dogeware Enhanced - Krunker.io Mod Menu
Last Updated: October 2026
1. INTRODUCTION & OVERVIEW
Dogeware Enhanced is committed to respecting and protecting user privacy. This privacy policy explains in transparent, plain English how our Chrome Extension operates, what data is accessed, and why specific browser permissions are requested.
2. ZERO DATA COLLECTION & PRIVACY COMMITMENT
• No Personal Data Collection: We do not collect, process, record, or transmit any personally identifiable information (PII), such as your name, email address, IP address, device fingerprints, or account credentials.
• No Tracking or Telemetry: Dogeware Enhanced contains zero analytics trackers, telemetry libraries, advertising pixels, or third-party monitoring scripts.
• 100% Client-Side Processing: All features—including the in-game HUD rendering, 2D ESP overlay calculations, Three.js material tweaks, and smoothing algorithms—run entirely locally inside your browser tab.
• No Remote Data Exfiltration: The extension does not maintain any external servers or backend databases. No information ever leaves your computer.
3. PERMISSIONS BREAKDOWN & WHY THEY ARE USED
To function reliably within modern Chrome (Manifest V3), Dogeware Enhanced requests only two minimal, scoped permissions:
A. "storage" Permission
• Purpose: Saves your configuration choices (e.g., whether ESP boxes are active, your chosen aimbot smoothing percentage, FOV angle, and glow color).
• Implementation: Utilizes the browser's local sandbox API (`chrome.storage.local`). The data remains strictly on your local disk and is never synced or sent anywhere.
B. Host Permissions ("*://krunker.io/*", "*://browserfps.com/*")
• Purpose: Grants the extension permission to inject the client-side user scripts (`content_main.js` and `content_bridge.js`) onto the game canvas page.
• Scope: Strictly limited to the official Krunker.io game domain and its browserfps mirror. The extension has zero access to any other website you visit.
4. PERMISSION AUDIT: ARE ALL THESE PERMISSIONS STRICTLY NECESSARY?
YES, the permissions requested represent the absolute theoretical minimum required for the extension to work, adhering strictly to the Chrome Web Store "Principle of Least Privilege":
• Why not `<all_urls>`?
Many poorly designed extensions ask for `<all_urls>` or `http://*/*`. Dogeware Enhanced strictly limits its host pattern to `*://krunker.io/*` and `*://browserfps.com/*`, ensuring total isolation from your banking, social media, and everyday browsing tabs.
• Why NOT the "tabs" permission?
We intentionally do NOT request the sensitive "tabs" permission. Basic extension actions—such as opening the onboarding guide on installation or launching the game—only need standard tab creation without elevated access to your browsing history or tab URLs.
• Why NOT "webRequest" or "declarativeNetRequest"?
Network interception permissions are invasive and trigger high-friction security warnings. Dogeware Enhanced operates entirely via in-memory Three.js scene traversal and WebGL canvas drawing, eliminating any need to inspect or modify your network requests.
• Why NOT "cookies"?
The extension has no need to inspect session identifiers or auth cookies, so this permission is omitted completely.
In summary, every single unnecessary permission has been stripped away. Only `storage` and targeted game host permissions remain.
5. DATA SECURITY & STORAGE
All user configuration preferences are stored using standard Google Chrome sandbox APIs on the user's local file system. If you uninstall the extension, all saved configuration keys are automatically wiped by Chrome.
6. CONTACT & QUESTIONS
If you have any questions or feedback regarding this Privacy Policy or permission audit, please contact the developer via the official repository or feedback channels listed in the Chrome Web Store developer dashboard.