PRIVACY POLICY - PROJECT BLON: OPENFRONT.IO TACTICAL SUITE & CHEATS
Last Updated: October 31, 2026
1. INTRODUCTION & PRIVACY COMMITMENT
This Privacy Policy governs the use of the "Project Blon - Openfront.io Tactical Suite & Cheats" Chrome extension ("we", "us", or "our"). We are dedicated to maintaining the highest standards of user privacy, digital safety, and data security.
Our core data philosophy is absolute minimalism: we do not collect, harvest, store, sell, or transmit any personal information, browsing history, or gameplay data. All extension operations execute 100% locally on your personal device.
==================================================
2. ARE ALL REQUESTED PERMISSIONS STRICTLY NECESSARY?
==================================================
YES. This extension strictly complies with Google's Principle of Least Privilege and Chrome Web Store Developer Policies. Every permission requested is indispensable to the core functionality of the extension:
A. "storage" Permission
• Why it is required:
Project Blon features extensive customization options, including attack percentage presets (1%, 20%, 50%, 100%), custom keybinding maps, HUD opacity/color themes, and individual on/off toggles for predictors and overlays. The "storage" permission enables the extension to save these user preferences locally via `chrome.storage.local`.
• What it does NOT do:
It never stores personal data, passwords, credentials, browsing records, or sensitive information. It only stores basic configuration key-value pairs (e.g., `combatHotkeys: true`).
• Can it be omitted?
No. Without local storage permission, any customized hotkeys, macro percentages, or GUI settings would be wiped clean every time you refresh your browser tab or restart your browser.
B. Host Permissions: "https://openfront.io/*" and "https://*.openfront.io/*"
• Why it is required:
Openfront.io is the specific web game this tactical helper is engineered for. To render the visual trajectory predictors, SAM missile alerts, economy counters, and attack macro hotkeys on the game canvas, the extension must inject content scripts into the openfront.io DOM.
• What it does NOT do:
We do NOT request broad, risky permissions such as "<all_urls>", "http://*/*", or "https://*/*". Host access is strictly confined to the official "openfront.io" domain and its subdomains. The extension cannot view, monitor, interact with, or alter any other websites you visit.
• Can it be omitted?
No. Under Manifest V3 security rules, content scripts cannot execute or draw overlays on a game page without targeted host permissions for that domain.
C. Permissions We Explicitly DO NOT Request:
To guarantee user safety and prevent unauthorized access, we intentionally avoid requesting:
• NO "tabs" permission (we do not inspect your browser tabs, open URLs, or session history)
• NO "cookies" permission (we never read or touch authentication tokens or session cookies)
• NO "webRequest" permission (we do not intercept or monitor external network traffic)
• NO "identity" permission (we do not access your Google account or personal profile)
• NO remote code execution (all code is audited, packaged, and executed locally from within the extension package)
==================================================
3. INFORMATION COLLECTION AND USAGE
==================================================
• Personal Identifiable Information (PII):
We do NOT collect names, email addresses, physical addresses, telephone numbers, IP addresses, payment details, or game account credentials.
• Telemetry and Analytics:
We do NOT operate any tracking scripts, telemetry loggers, Google Analytics, or external ping workers. The extension is completely decoupled from any external monitoring server.
• In-Game Actions & Gameplay:
Keyboard shortcuts and macro inputs triggered by the player are sent directly to the local game client on your screen. No record of your actions, clan affiliations, or match results is ever transmitted off your device.
==================================================
4. DATA STORAGE & RETENTION
==================================================
All configuration parameters and user settings are stored strictly within Chrome's sandboxed local storage (`chrome.storage.local`). No data is ever transmitted to cloud servers, databases, or third parties.
When you uninstall the extension, Google Chrome automatically and permanently deletes all stored preferences immediately from your machine.
==================================================
5. THIRD-PARTY DISCLOSURE
==================================================
We do not sell, rent, lease, trade, or transfer any user information to outside parties. Because we collect zero data from our users, there is no data to share, monetize, or disclose.
==================================================
6. CHILDREN'S PRIVACY PROTECTION
==================================================
Our extension is fully compliant with the Children's Online Privacy Protection Act (COPPA) and the General Data Protection Regulation (GDPR). Because we do not collect any personal data whatsoever, our extension is safe for users of all ages, including children under 13.
==================================================
7. COMPLIANCE WITH CHROME WEB STORE DEVELOPER POLICIES
==================================================
This extension adheres stringently to all Google Chrome Web Store Developer Program Policies, specifically:
• Single Purpose Policy: Dedicated solely to tactical gameplay enhancement on openfront.io.
• Limited Use Requirements: Permissions are restricted to the absolute bare minimum needed.
• User Data Policy: Zero collection of sensitive personal or financial information.
==================================================
8. CONTACT & SUPPORT
==================================================
If you have any questions, suggestions, or concerns regarding this Privacy Policy or the security architecture of Project Blon, please contact us via our official support channel on the Chrome Web Store or through our documentation page.