=== PRIVACY POLICY FOR AURA CLIENT ===
Last Updated: October 2026
1. INTRODUCTION & CORE PRINCIPLE
AURA CLIENT ("Universal Wireframe") is committed to total user privacy and data security. We believe that gaming utility tools should never compromise user trust. AURA CLIENT operates entirely on the client side inside your web browser. We do NOT collect, store, transmit, or sell any personal data, gameplay statistics, or browsing activity.
2. WHAT DATA DO WE COLLECT?
• Personal Identification Data: ZERO collected.
• Browsing History or Search Queries: ZERO collected.
• Keystroke Logging or Text Input: ZERO collected. (The extension specifically ignores hotkey presses whenever an active text field, chat box, or input is focused).
• IP Addresses or Device Identifiers: ZERO collected.
• Third-Party Tracking / Telemetry / Analytics: ZERO. There are no tracking scripts, Google Analytics, or third-party SDKs bundled with this extension.
3. PERMISSIONS EXPLANATION & "ARE ALL THESE PERMISSIONS STRICTLY NECESSARY?"
We strictly adhere to the principle of least privilege. Below is an exhaustive breakdown of the permissions used and why every single one is necessary:
• "storage" Permission:
- Why is it needed?
This permission is used solely via `chrome.storage.local` on your local computer to save your personal preferences (such as your chosen toggle hotkey, preferred wireframe rendering mode like LINES or LINE_STRIP, vertex threshold filter, and whether you prefer the in-game HUD visible or hidden).
- Can it access personal data?
No. It only reads and writes the small configuration object belonging specifically to AURA CLIENT.
• Content Scripts on Targeted Game Domains:
- Why is it needed?
To modify the WebGL rendering pipeline (transforming solid 3D triangle polygons into wireframe lines), the extension's lightweight hook must run in the webpage's canvas context when a compatible game launches.
- Can it access your passwords or accounts?
No. The script only intercepts WebGL canvas rendering contexts (`WebGLRenderingContext` and `WebGL2RenderingContext`) to swap drawing primitives.
• ARE ALL PERMISSIONS STRICTLY NECESSARY? YES, AND WE INTENTIONALLY AVOIDED ALL INTRUSIVE PERMISSIONS:
- We do NOT request "<all_urls>" or broad broad host permissions.
- We do NOT request the "tabs" permission.
- We do NOT request the "activeTab" permission.
- We do NOT request "webRequest" or "webRequestBlocking".
- We do NOT request "cookies" or access to local storage of third-party websites.
- We do NOT use external background servers or remote script execution.
Every permission in the manifest is strictly scoped to the bare minimum required for the WebGL wireframe client to function.
4. NETWORK CONNECTIONS & EXTERNAL REQUESTS
AURA CLIENT makes ZERO background network requests. It never communicates with any external server. All WebGL drawing proxies execute locally in your computer's GPU/browser thread.
5. SECURITY OF YOUR DATA
Since no data is ever transmitted or stored on remote servers, there is no risk of data breach, leaks, or unauthorized third-party access. All configuration resides solely in your browser's local sandbox and can be wiped instantly by uninstalling the extension.
6. CONTACT & COMMUNITY
If you have questions regarding this Privacy Policy or wish to inspect the open source code, you can reach out via our community Discord: