PRIVACY POLICY - Crosshair for Shell Shockers
Last updated: October 2026
1. INTRODUCTION & CORE COMMITMENT
"Crosshair for Shell Shockers - Precision Aim" ("the Extension") is dedicated to protecting user privacy. This extension was engineered from the ground up under a strict privacy-first architecture. It functions solely as a visual Heads-Up Display (HUD) crosshair overlay for Shell Shockers players.
We do not collect, harvest, monitor, sell, or transmit any user data or personal information. Everything executes 100% client-side directly within your browser.
---
2. ARE ALL REQUESTED PERMISSIONS ACTUALLY NECESSARY?
YES. The extension strictly adheres to the Chrome Web Store Principle of Least Privilege. Only the absolute bare-minimum permissions required for core crosshair rendering and user preferences are requested:
• "storage" Permission:
- Why is it needed? This permission allows the extension to store your preferred crosshair configuration (such as your chosen reticle shape, color code, size, thickness, opacity, outline style, and toggle hotkey).
- Could the extension work without it? Without storage, your personalized crosshair settings would be wiped out and reset to default every time you close your browser or navigate to a new page, requiring you to reconfigure your crosshair before every match.
- What does it store? Only simple UI preference values (e.g., {"shape": "cross", "color": "#00ff00"}). It contains zero personal identifiable information (PII).
• Host Permissions (Restricted to Shell Shockers domains: *://*.shellshock.io/*, *://eggcombat.com/*, *://egg.dance/*, *://shellshockers.io/*):
- Why is it needed? To draw the visual reticle over the game canvas, the extension needs permission to inject a lightweight DOM overlay container on Shell Shockers game pages.
- Scope limitation: The extension is strictly confined to official Shell Shockers game URLs. It CANNOT access, read, inject, or interact with any other websites you visit (such as search engines, social media, banking sites, or personal portals).
• Why broad permissions are NOT included:
- We do NOT request "<all_urls>" or broad web access.
- We do NOT request "tabs", "activeTab", "webRequest", "cookies", or "management".
- We do NOT execute remote scripts or external CDN libraries. All code is bundled locally within the extension package in full compliance with Manifest V3 security standards.
---
3. DATA COLLECTION & SHARING (ABSOLUTE ZERO POLICY)
• No Personal Information: The extension does not collect names, email addresses, IP addresses, geolocation, device identifiers, or credentials.
• No Browsing History: We do not track, inspect, or log URLs, searches, or web activity.
• No Gameplay Telemetry: The extension does not log or transmit your game scores, kills, deaths, or play duration.
• No Third-Party Trackers or Analytics: There are no advertising scripts, no trackers (e.g. Google Analytics, Facebook Pixel, Mixpanel), and no hidden beacons.
• No External Data Transfers: The extension makes zero outgoing network requests (no API calls to external servers).
---
4. DATA STORAGE & RETENTION
All configuration data is stored locally on your device using the Chrome Storage API (`chrome.storage.sync` or `chrome.storage.local`). If you enable Google Chrome's built-in profile sync, your settings may be synchronized across your own devices via your personal Google Account.
You retain complete control over your data:
• You can reset all configurations anytime by clicking the "Reset" button in the extension popup.
• Uninstalling or removing the extension from your browser instantly and permanently erases all stored preferences from your local machine.
---
5. SECURITY & FAIR PLAY
The extension does not intercept keyboard inputs outside of the single user-configured hotkey (default: 'X'), which is automatically ignored whenever typing into game chat or input boxes. The extension operates as an accessible visual overlay and does not tamper with game engine memory, hitboxes, or server networking.
---
6. CONTACT & INQUIRIES
If you have questions regarding this Privacy Policy or the extension's permission model, please submit feedback via the extension's official Chrome Web Store support page or project repository.