# PRIVACY POLICY FOR TASTY MOD CHROME EXTENSION
Effective Date: October 22, 2026
Last Updated: October 22, 2026
Tasty Mod ("we", "our", or "the extension") is committed to protecting your privacy. This Privacy Policy transparently explains what data the extension handles, how permissions are utilized, and how we adhere to the principle of data minimization.
==================================================
1. SUMMARY: ZERO PERSONAL DATA COLLECTED
==================================================
Tasty Mod operates entirely on the client side inside your web browser.
- We DO NOT collect, store, transmit, or sell any personal information.
- We DO NOT collect usernames, passwords, IP addresses, browsing histories, or hardware identifiers.
- We DO NOT run remote analytics, telemetry, trackers, or third-party advertising scripts.
- All game interactions and preferences remain strictly confined to your local device.
==================================================
2. EXPLANATION OF PERMISSIONS USED
==================================================
Tasty Mod requests only two specific permissions in its Manifest V3 configuration:
A. "storage" Permission
• Purpose: Used solely by chrome.storage.local to save your custom gameplay configuration.
• What is stored:
- AutoHeal toggle state (ON/OFF)
- AutoHeal HP Umbral threshold (e.g., 91 HP)
- AutoHeal reaction delay / speed (e.g., 100 ms)
- Food multiplier repeat count (e.g., 2)
- Custom hotkey assignments (e.g., Key P, Key N, Key F, Key ESC)
- Visual theme and HUD toggles
• Location: All data is saved strictly in your browser's local sandbox storage on your own machine. It is never synced to external servers or accessible to third parties.
B. Host Permissions ("*://moomoo.io/*", "*://sandbox.moomoo.io/*", "*://dev.moomoo.io/*")
• Purpose: Grants the extension permission to inject its gameplay scripts, hotkey listeners, and tactical HUD elements into the MooMoo.io game canvas.
• Scope: Strictly scoped to the official MooMoo.io game domains. The extension has zero access to any other websites, tabs, or domains you visit.
==================================================
3. ARE ALL THESE PERMISSIONS DEFINITELY NECESSARY?
==================================================
YES. We have performed a strict security audit to ensure full compliance with Google's Principle of Least Privilege:
• Why broad permissions were rejected:
- We DO NOT request "<all_urls>" or wide wildcards. The extension only executes on explicit MooMoo.io addresses.
- We DO NOT request "tabs" permission. We do not inspect your browsing history, active tabs list, or window states.
- We DO NOT request "webRequest" or network intercept permissions.
- We DO NOT request "cookies", "identity", or "management" permissions.
• Could "storage" be omitted?
Without "storage", every time you closed your browser or refreshed the tab, all of your custom hotkeys, HP trigger levels, and ping delay adjustments would be lost, requiring you to reconfigure them on every game launch. Using local storage provides a seamless user experience while guaranteeing 100% local persistence.
• Could Host Permissions be omitted?
Without host permissions on MooMoo.io, the browser security sandbox would prevent the extension from listening to your game key presses (such as pressing 'P' to heal or 'N' for windmills) and communicating with the game canvas.
Therefore, both permissions represent the absolute bare minimum required for the extension to operate as advertised.
==================================================
4. THIRD-PARTY CODE & EXTERNAL SERVICES
==================================================
In strict compliance with Chrome Web Store Manifest V3 guidelines:
- Zero Remote Code: The extension does not load scripts or libraries from external CDNs, greasyfork, or remote servers. All libraries (including the MessagePack decoder) are bundled locally inside the extension package.
- No External Communication: The extension makes zero outgoing network calls to external servers or developer-controlled APIs.
==================================================
5. HOW TO MANAGE OR DELETE YOUR DATA
==================================================
Since all data is stored strictly in your browser's local storage:
- You can reset all saved settings to default at any time by clicking the "Reset" button inside the extension popup.
- Uninstalling the Tasty Mod extension from chrome://extensions immediately deletes all locally stored settings and cached preferences from your computer.
==================================================
6. CONTACT & QUESTIONS
==================================================
If you have any questions or feedback regarding this Privacy Policy or the security of Tasty Mod, please submit an inquiry through the Chrome Web Store support page or project repository.