PRIVACY POLICY FOR KXS CLIENT - SURVEV.IO & SURVIV CLIENT
Last Updated: October 2026
Kxs Client - Survev.io & Surviv Client ("we", "our", or "the extension") is committed to protecting your privacy. This Privacy Policy clearly describes our data collection practices, security standards, and provides a transparent explanation of all browser permissions requested by the extension.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. SUMMARY OF CORE PRIVACY PRINCIPLES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
• Zero Personal Data Collection: We do not collect, store, transmit, or sell any personal data, IP addresses, browsing histories, or unique user identifiers.
• 100% Client-Side Execution: All client modifications, HUD counters, and visual adjustments occur entirely inside your browser on the client side.
• Local Storage Only: All user preferences (such as HUD toggles, crosshair styles, and volume levels) are stored locally on your device via Chrome's local storage and HTML5 localStorage.
• No Tracking & No Third-Party Analytics: There are no trackers, tracking pixels, telemetry probes, or third-party advertising scripts contained within this extension.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2. DETAILED EXPLANATION OF PERMISSIONS REQUESTED
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
To deliver its in-game HUD and performance features, Kxs Client requests only two specific permissions. Here is exactly what each permission does and why it is required:
1. "storage"
• Purpose: Saves your custom configuration and settings (such as enabling/disabling FPS counters, Focus Mode, low-health warnings, theme selections, and custom crosshair settings).
• How it is used: When you adjust a toggle in the extension popup or the in-game settings menu, the state is saved to your browser's local storage (`chrome.storage.local`) so your customized preferences persist across browser restarts and page refreshes.
• Data Access: Stored solely on your local device. Never uploaded to external servers.
2. "host_permissions" (*://*.survev.io/*, *://*.zurviv.io/*, *://*.cursev.io/*, *://*.resurviv.biz/*, etc.)
• Purpose: Allows the extension's content scripts to execute exclusively on supported battle royale web game pages.
• How it is used: When you visit Survev.io or compatible community servers, the extension injects the client interface, hooks WebSocket connection metadata to display your in-game ping and match ID, and renders the custom HUD elements on your game canvas.
• Data Access: The extension can only interact with the specified game websites. It has absolutely no access to any other websites you visit.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
3. ARE ALL THESE PERMISSIONS TRULY NECESSARY?
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Yes. Kxs Client adheres strictly to Google's "Principle of Least Privilege" (PoLP):
• Strictly Scoped Host Permissions:
Instead of requesting broad permissions such as `<all_urls>` or `*://*/*` (which would grant access to every site you browse), Kxs Client specifies only the exact domains of Survev.io and supported Surviv community servers. It is impossible for the extension to inspect or interact with any non-game websites.
• No Unnecessary High-Risk Permissions:
Kxs Client DOES NOT request:
- NO `activeTab` or general `tabs` permission (does not read tab titles or history)
- NO `webRequest` or `declarativeNetRequest` (does not monitor or intercept general web traffic)
- NO `cookies` permission (does not access authentication cookies)
- NO `identity` permission (does not access your Google account)
- NO `management` or `nativeMessaging` permissions
• Can the extension function with fewer permissions?
Without `host_permissions`, the extension cannot inject the HUD overlay or display in-game ping on Survev.io. Without `storage`, your custom HUD preferences and keybind settings would be reset every time you close the tab. Therefore, both permissions represent the bare technical minimum required for the extension to function.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
4. DATA SECURITY & STORAGE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
All configuration data managed by Kxs Client remains isolated within your browser's sandboxed storage environment. You can completely erase all stored preferences at any time by uninstalling the extension or clearing your browser's extension data through Chrome settings.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
5. CHANGES TO THIS PRIVACY POLICY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
We may update this Privacy Policy from time to time if new features are added. Any changes will be posted in this file and reflected in our extension release notes.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
6. CONTACT & COMMUNITY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
If you have any questions, feedback, or concerns regarding this Privacy Policy or your privacy while using Kxs Client, feel free to visit the official project repository or contact the development community via our documentation page.