================================================================================
PRIVACY POLICY - PRODIGY MATH HACKER & MOD LOADER
================================================================================
Last Updated: October 2026
At Prodigy Math Hacker & Mod Loader ("we", "our", or "the extension"), we respect your privacy and are committed to maintaining the highest level of transparency and data protection. This Privacy Policy outlines our data handling practices, explains why specific browser permissions are requested, and provides an objective audit of why each permission is strictly required.
--------------------------------------------------------------------------------
1. OUR CORE PRIVACY COMMITMENT: ZERO DATA COLLECTION
--------------------------------------------------------------------------------
We believe your gaming experience and personal data belong exclusively to you.
• ZERO Personal Data Collection: We do NOT collect, record, track, log, or sell your name, email address, IP address, browsing history, or gameplay statistics.
• ZERO Account Credential Access: We do NOT capture, intercept, or access your Prodigy username, password, login tokens, school credentials, or payment information.
• ZERO Third-Party Trackers or Analytics: There are no Google Analytics, telemetry scripts, ad networks, or external tracking beacons embedded in this extension.
• 100% Client-Side Execution: All modding operations, script loaders, and game patches run locally within your web browser.
--------------------------------------------------------------------------------
2. DETAILED BREAKDOWN OF REQUESTED PERMISSIONS
--------------------------------------------------------------------------------
The extension requests the following permissions in its manifest.json file:
A. "storage"
• Purpose: Saves your configuration options locally within Chrome's built-in storage engine (chrome.storage.sync).
• What is stored:
- Enabled/disabled master toggle state.
- Selected script preset ("prodigyx", "origin", or "custom").
- Custom script URLs entered in the developer options.
• Privacy Impact: Completely isolated to your Chrome profile. This data never leaves your device and is never shared with us or any external servers.
B. "declarativeNetRequest"
• Purpose: Applies network modification rules specified in rules.json to Prodigy web requests.
• What it does:
- Removes restrictive "Content-Security-Policy" (CSP) and "X-Frame-Options" response headers on math.prodigygame.com so custom scripts can load into the game runtime.
- Intercepts requests for the unpatched game client script (game.min.js) so the patched client loader can take precedence.
• Privacy Impact: The extension does not read or intercept the contents of your HTTP traffic; it simply directs the browser engine to omit security headers that would otherwise block client-side modding.
C. Host Permission: "*://*.prodigygame.com/*"
• Purpose: Defines the target environment where the extension operates.
• What it does:
- Grants permission to inject the content script (contentScript.js) into math.prodigygame.com.
- Grants permission for declarativeNetRequest rules to modify headers exclusively for prodigygame.com domains.
• Privacy Impact: Strictly scoped to Prodigy websites. The extension cannot interact with, view, or modify any other website you visit.
D. Host Permission: "*://raw.githubusercontent.com/*"
• Purpose: Allows the extension's content script to make secure HTTPS GET requests to fetch open-source game patches and mod menus hosted on GitHub.
• What it does: Downloads the latest verified community cheat menus (e.g., Prodigy X bundle, Origin bundle) and game patch files.
• Privacy Impact: Read-only access to download public code repositories. No user data is ever transmitted in these requests.
--------------------------------------------------------------------------------
3. ARE ALL OF THESE PERMISSIONS STRICTLY NECESSARY?
--------------------------------------------------------------------------------
YES. Every single permission has been carefully audited and reduced to the absolute minimum viable footprint:
1. Could we remove "storage"?
No. If removed, the extension would forget your preferences every time you close the popup or restart Chrome. Your preset choice and toggle settings would have to be manually re-entered every single time.
2. Could we remove "declarativeNetRequest"?
No. Modern web browsers strictly enforce Content Security Policy (CSP) headers sent by Prodigy's servers. Without declarativeNetRequest removing these headers, the browser will block the injection of all external scripts, rendering the mod loader completely non-functional.
3. Could we remove "*://*.prodigygame.com/*"?
No. Chrome extensions require explicit host permissions to run content scripts on a webpage and apply network modification rules. Scoping it strictly to prodigygame.com ensures the extension only touches the game, and nothing else.
4. Could we remove "*://raw.githubusercontent.com/*"?
No. Because the mod menus and patch files are maintained in community open-source GitHub repositories to ensure rapid updates when the game patches, the browser requires permission to download these scripts via fetch().
SUMMARY: The extension uses the absolute minimal set of permissions required to achieve its functionality under Chrome Manifest V3. Broad and dangerous permissions (such as <all_urls>, webRequestBlocking, cookies, history, or management) are NOT requested.
--------------------------------------------------------------------------------
4. THIRD-PARTY CONTENT & EXTERNAL LINKS
--------------------------------------------------------------------------------
The extension includes links to official game portals (math.prodigygame.com) and an optional onboarding welcome tab (thankyou.html). When you interact with third-party sites, their respective privacy policies apply. We do not control and are not responsible for the privacy practices of third-party websites.
--------------------------------------------------------------------------------
5. DATA RETENTION AND DELETION
--------------------------------------------------------------------------------
Because all settings are stored locally using Chrome's storage API, you have full control over your data:
• You can reset all configurations to factory defaults at any time via the "Reset Defaults" button in the popup.
• Uninstalling the extension from chrome://extensions immediately deletes all locally stored preferences from your browser.
--------------------------------------------------------------------------------
6. CONTACT & QUESTIONS
--------------------------------------------------------------------------------
If you have any questions or concerns regarding this Privacy Policy, please open an issue on our GitHub repository or contact the development team through the Chrome Web Store support portal.
================================================================================