PRIVACY POLICY FOR DIEPFRIED CHROME EXTENSION
Last Updated: October 2026
DiepFried ("we", "our", or "the extension") values and respects your privacy. This Privacy Policy details our data practices, outlines how user information is handled, and provides full transparency regarding the browser permissions required to operate this extension.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. SUMMARY OF CORE PRINCIPLES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
• 100% Client-Side Execution: All mod menu logic, rendering, and macro engines run entirely within your local browser sandbox.
• Zero Personal Data Collection: We do not collect, store, sell, log, or transmit any personally identifiable information (PII).
• Zero Remote Telemetry or Tracking: No Google Analytics, no advertising networks, no user tracking beacons, and no external telemetry servers are bundled or contacted by this extension.
• Strictly Local Storage: All saved presets, custom themes, and user preferences remain on your local computer via Chrome's local storage API.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2. DETAILED PERMISSIONS BREAKDOWN & WHY THEY ARE NEEDED
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
To deliver its features, DiepFried requests an absolute minimum set of browser permissions:
1) "storage"
• Why it is needed:
Allows the extension to save your preferences across browsing sessions. This includes your chosen visual theme (e.g. Midnight, Neon, Dark), custom crosshair preferences (shape, color), auto-respawn toggles, and custom tank build point distributions.
• Data handled:
Only local key-value configuration objects. No personal credentials, history, or identifiers are saved.
2) Host Permissions ("https://diep.io/*" and "https://api.diep.io/*")
• Why they are needed:
- "https://diep.io/*": Needed to inject the client-side mod menu UI, render the custom vector crosshair, and connect with the game's canvas and WebSocket stream for packet telemetry.
- "https://api.diep.io/*": Needed to communicate with the official Diep.io sandbox directory, enabling the in-game "Lobby" tab to display active community custom games and allow 1-click joining or creating custom rooms.
• Data handled:
Only game-specific network packets and room IDs. No personal browsing activity is monitored.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
3. ARE ALL OF THESE PERMISSIONS REALLY NECESSARY?
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
YES, ABSOLUTELY. Every permission requested by DiepFried is strictly required for its stated features, adhering directly to the Google Chrome Web Store's Principle of Least Privilege:
• Why doesn't DiepFried request broad permissions?
Many extensions request "<all_urls>", which grants access to every website you visit on the internet. DiepFried strictly avoids this. DiepFried is locked down exclusively to "https://diep.io/*" and "https://api.diep.io/*". The extension cannot interact with, read, or alter any other website you visit.
• Why not use "activeTab" or "tabs"?
DiepFried does not request "tabs" or "activeTab" permissions. Because the extension has explicit host permissions for "https://diep.io/*", it interacts strictly with the game canvas without needing any broader tab inspection privileges.
• Why not use "cookies"?
DiepFried does not request the "cookies" permission. Your browser authentication cookies and sensitive session identifiers are never inspected by the extension.
• Why not use "webRequest" or "webRequestBlocking"?
DiepFried does not intercept or block your general browser web traffic. It only inspects game canvas data and game-specific WebSocket frames on Diep.io itself.
In conclusion: every single permission requested has a direct, necessary function in providing the in-game menu and saving your game settings. There are zero redundant, excessive, or hidden permissions.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
4. THIRD-PARTY DISCLOSURE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
DiepFried does not share, monetize, or transfer any user data to third parties. We do not partner with data brokers, advertisers, or analytics companies.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
5. DATA SECURITY & USER CONTROL
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Because all data is stored locally in your browser:
• You can clear all saved settings at any time by clearing your browser's extension data or uninstalling the extension.
• Uninstalling DiepFried immediately removes all stored configuration files and scripts from your machine.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
6. CONTACT & COMMUNITY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
If you have any questions, security inquiries, or feedback regarding this Privacy Policy, please join the official DiepFried community support server on Discord: