PRIVACY POLICY & PERMISSIONS TRANSPARENCY
Last Updated: October 2026
Extension Name: Krunker Mod Menu & Tactical Aim Assistant
--------------------------------------------------------------------------------
1. INTRODUCTION & CORE PRIVACY COMMITMENT
--------------------------------------------------------------------------------
Krunker Mod Menu & Tactical Aim Assistant ("we", "our", or "the extension") is dedicated to protecting user privacy and maintaining complete operational transparency.
Our fundamental promise is simple:
• We do NOT collect, harvest, store, or sell any personal information.
• We do NOT track your browsing activity or search queries.
• We do NOT transmit any data to external servers, cloud databases, or third-party analytics platforms.
• The extension operates 100% locally on your device within your browser sandbox.
--------------------------------------------------------------------------------
2. DETAILED PERMISSIONS BREAKDOWN & WHY THEY ARE NEEDED
--------------------------------------------------------------------------------
The extension requests only the absolute minimum set of permissions necessary to deliver its core tactical utilities, adhering strictly to the Chrome Web Store Least Privilege Principle.
• "storage" Permission
Why is it needed?
This permission enables the extension to read and write your configuration preferences (e.g., aim smoothing factor, aim height offset, Box ESP toggles, charms glow color, spinbot speed, and camera perspective) to Chrome's local storage (`chrome.storage.local`).
What does it access?
Only the extension's own JSON settings object. It cannot read stored passwords, autofill data, or cookies from any website.
• Host Permissions ("*://krunker.io/*", "*://browserfps.com/*")
Why is it needed?
Host permissions are strictly scoped to the exact game domains where the user wants tactical enhancements. This allows the extension to inject the WebGL shader helper, in-game [O] shortcut menu, and visual overlay directly into the game canvas.
What does it access?
It ONLY executes on Krunker.io and BrowserFPS.com. It does NOT have access to search engines, banking websites, social media, email accounts, or any other domain.
--------------------------------------------------------------------------------
3. ARE ALL THESE PERMISSIONS REALLY NECESSARY? (LEAST PRIVILEGE AUDIT)
--------------------------------------------------------------------------------
YES. Every requested permission is strictly required for the extension to function, and no unnecessary or invasive permissions are included:
• Why NOT "<all_urls>"?
Many poorly built extensions request broad `<all_urls>` access, triggering browser security warnings. We strictly avoid this by limiting host permissions exclusively to the two game domains.
• Why NOT "tabs" permission?
We do not need to monitor your other browser tabs, see your browsing history, or inspect URLs across your browser sessions.
• Why NOT "webRequest" or "cookies"?
The extension does not intercept network traffic, monitor authentication sessions, or interact with session cookies.
• Why NOT "downloads" or "identity"?
The extension does not download external files or link to Google accounts.
By eliminating all superfluous permissions, the extension guarantees maximum security, zero risk of data leakage, and fast, hassle-free approval on the Chrome Web Store.
--------------------------------------------------------------------------------
4. THIRD-PARTY CODE & EXTERNAL NETWORK CALLS
--------------------------------------------------------------------------------
• No Remote Hosted Code: In full compliance with Google Chrome Web Store Manifest V3 policies, all libraries (including Three.js) are bundled directly inside the extension package. No remote scripts are loaded at runtime from CDNs.
• No Advertising / Trackers: The extension contains zero advertisements, popunders, affiliate tracking, or monetization redirects.
--------------------------------------------------------------------------------
5. DATA RETENTION & REMOVAL
--------------------------------------------------------------------------------
Because all settings are stored locally on your device via `chrome.storage.local`, your data remains entirely under your control. Uninstalling the extension immediately and permanently removes all stored preferences from your browser.
--------------------------------------------------------------------------------
6. CONTACT & INQUIRIES
--------------------------------------------------------------------------------
If you have any questions or concerns regarding this Privacy Policy or permission usage, please visit the extension's documentation page or submit feedback via the Chrome Web Store extension page.