================================================================================
PRIVACY POLICY - BLOOKET HACKER EXTENSION
================================================================================
Last Updated: November 14, 2026
At Blooket Hacker ("we", "our", or "the extension"), we respect and protect your privacy. This Privacy Policy outlines our data handling practices, explains why each browser permission is requested, and addresses whether all requested permissions are strictly necessary.
--------------------------------------------------------------------------------
1. ZERO DATA COLLECTION PLEDGE (100% LOCAL & PRIVATE)
--------------------------------------------------------------------------------
• ZERO Personal Data Collection: We do not collect, store, log, or transmit personal details such as your name, email, school account, IP address, or device ID.
• ZERO External Servers: Blooket Hacker operates entirely client-side inside your Google Chrome browser. The extension does not connect to any external cloud backend, database, or API server.
• ZERO Telemetry & Trackers: We do not use Google Analytics, advertising SDKs, session recording tools, or tracking cookies.
• ZERO Browsing History Tracking: The extension only activates on blooket.com. It has no visibility into your browsing activity on any other website.
• ZERO Data Selling: We do not sell, rent, monetize, or disclose your information to any third parties.
--------------------------------------------------------------------------------
2. DETAILED EXPLANATION OF REQUESTED PERMISSIONS
--------------------------------------------------------------------------------
Blooket Hacker requests only two permissions in its Manifest V3 configuration:
1. "storage" Permission (`chrome.storage.local`)
• Why it is needed:
Allows the extension to save your preferences directly onto your computer. This includes your chosen response delay (in milliseconds), active playstyle preset (Legit, Auto, Speedrun), feature toggles (Auto-Answer, Glow Highlight, Auto-Skip, Gold Quest ESP, Crypto Hack Helper, HUD visibility), and session question statistics.
• Why it is safe:
All stored preferences remain strictly within your browser's private local sandbox. Nothing is synchronized or transmitted to any external server. Without this permission, you would have to reconfigure your delay slider and mode settings every time you close and reopen Chrome.
2. "*://*.blooket.com/*" (Host Permission)
• Why it is needed:
Allows the extension's content script to execute specifically on Blooket domain pages (such as play.blooket.com, dashboard.blooket.com). This permission enables Blooket Hacker to detect active quiz questions, display the glowing neon answer border, render the draggable floating in-game HUD, and provide Gold Quest & Crypto Hack visual assists.
• Why it is safe:
This permission is strictly domain-scoped to blooket.com. The extension cannot, and will never, read, monitor, or interact with any other website you visit (such as search engines, social media, personal email, or banking portals).
--------------------------------------------------------------------------------
3. PERMISSION AUDIT: ARE ALL THESE PERMISSIONS STRICTLY NECESSARY?
--------------------------------------------------------------------------------
YES. Every single permission requested by Blooket Hacker is vital for its functionality. Furthermore, in strict adherence to Google's Principle of Least Privilege, our architecture was deliberately designed to omit all unnecessary or intrusive permissions:
• WHY WE DO NOT USE "<all_urls>":
Many quiz helpers request access to all websites. We strictly rejected this approach; Blooket Hacker is hardcoded only to activate on blooket.com.
• WHY WE DO NOT USE "cookies":
The extension does not read, access, or modify session cookies or authentication tokens. All assists operate purely on visible client-side DOM and React components.
• WHY WE DO NOT USE "webRequest" OR "webRequestBlocking":
Instead of intercepting network traffic, our extension works client-side via DOM observation and React Fiber component inspection, eliminating the need for elevated network permissions.
• WHY WE DO NOT USE "identity":
The extension does not need your Google account identity, email address, or profile data to assist with quizzes.
• WHY WE DO NOT USE "tabs":
Generic tabs permission gives broad access to tab URLs and titles. We only use standard `chrome.tabs.create` to open our local welcome page (`hello.html`) and user guide (`howtouse.html`).
--------------------------------------------------------------------------------
4. WHAT DATA IS STORED LOCALLY & HOW TO DELETE IT
--------------------------------------------------------------------------------
The only data stored is stored locally on your device in `chrome.storage.local`:
1. Configuration settings: `responseTime` (ms), `preset`, `autoAnswer`, `highlightOnly`, `autoSkip`, `espGold`, `espCrypto`, `showHud`.
2. Session statistics: `questionsAnswered`, `correctAnswers`, `accuracy`.
How to erase your data:
• You can reset all gameplay statistics instantly by clicking the "↺" button in the popup dashboard.
• You can remove all extension data at any time by simply uninstalling Blooket Hacker from Chrome (Extensions > Remove from Chrome).
--------------------------------------------------------------------------------
5. POLICY UPDATES & CONTACT
--------------------------------------------------------------------------------
If this Privacy Policy is updated, the changes will be reflected in the extension's documentation and Chrome Web Store listing.
For questions or support regarding privacy, visit our documentation page or inspect the source code directly within your extension files.