1. Information EyesX processes
Color settings, game profiles, crosshair designs, preferences, and most application state are stored locally on your PC. EyesX does not collect game memory, gameplay contents, chat, keystrokes, mouse input, passwords, Riot account information, or files unrelated to EyesX.
The Free Access build does not use the EyesX licensing service and does not require an account or device binding. Licensed editions, when activated, may send the activation key, the account label you enter, a one-way hash derived from a Windows device identifier, activation status, software version, request time, and ordinary connection metadata such as an IP address.
2. Why this information is used
- to bind a one-user license to the activated device;
- to prevent duplicate or abusive activation attempts;
- to check for and deliver product updates;
- to diagnose activation or update failures when support is requested; and
- to protect the availability and security of the EyesX service.
3. Riot and game information
The current EyesX product does not use Riot APIs and does not request or store Riot account data. EyesX does not proxy or inspect game network traffic.
4. Sharing and sale
EyesX does not sell personal information. Infrastructure providers used to host the activation or update service may process limited technical information on our behalf. Feedback submitted through the website is processed by FormSubmit and forwarded by email; the submitted name, email address, category, version, and message are included. FormSubmit states that submissions may be retained for up to 30 days. Information may also be disclosed when required by law or necessary to protect users and the service.
Crosshair names and crosshair codes submitted to the community library are public. They are stored with a random record identifier and submission time so other visitors can preview and copy them. Do not put personal information into a crosshair name.
EyesX records page views and completed download preparations to understand website usage. A salted one-way hash derived from a visitor’s IP address is used to distinguish unique network visitors and measure repeat visits. The raw IP address is not stored in the analytics database and cannot be recovered from the anonymous visitor ID shown in the private admin dashboard.
Private arcade access uses a browser cookie. The owner can see each code’s label, redemption IP, most recent IP and activity time, expiration, and an optional email supplied by the redeemer. Email addresses are not verified. These records help manage access and identify shared codes; they are separate from anonymous website analytics.
5. Retention and security
For licensed editions, license bindings are retained while the associated license remains active and as reasonably necessary for fraud prevention and support. Temporary website and service logs may be retained for a limited operational period. EyesX uses hashed device identifiers where licensing applies, but no networked system can be guaranteed completely secure.
6. Your choices
You can remove local profiles and settings by resetting or uninstalling EyesX. Requests about a license binding, correction, or deletion can be made through the website feedback form, the support channel provided with the license, or the EyesX product-review submission.
7. Changes
This policy will be updated before EyesX begins collecting a new category of information or using Riot account or API data. The effective date above identifies the current version.