Privacy Information for IX6 Participants
This page explains the categories of information an esports platform may use to operate accounts, events, support and integrity processes.
The deployed operator should review this policy against the actual IX6 services, vendors, retention periods and legal obligations before publication. The page is written as a clear participant-facing framework and does not invent a registration number, office address or external data partner.
Account and event functions create different records
Profile information can include a display name, contact method, region, age status and in-game identity. Event records can include registration, roster, check-in, match result, conduct and support references. Technical logs may record device, app version, network or error information needed for security and service reliability.
Identity or payment information should be requested only where a published verification, administration charge, refund or performance-prize process requires it. The platform should identify the secure channel and avoid collecting unrelated material.
- Profile and recovery information
- Event, roster and result records
- Security, device and support logs
- Verification or transaction records where required
Information should support a stated platform or competition purpose
Data can support sign-in, eligibility, roster administration, scoring, fair-play review, customer support and the settlement of legitimate event balances. Aggregated information can help diagnose performance and improve event operations.
IX6 should not describe organised esports data as information for wagering on match outcomes. Access should be limited according to operational need, and providers acting for the operator should receive only the information required for their service.
Participants should know how to review and correct their profile
Account settings can provide access to contact, identity and visibility choices. A player can request correction when a record is inaccurate and can ask about closure or data rights through the recognised support path. Some event or integrity records may need to remain after account closure.
Security starts with the participant as well. Passwords and OTPs should remain private, and sensitive documents should be submitted only through the official page.
Retention should follow purpose, integrity and legal requirements
Different information can require different retention periods. Active account data supports ongoing use, while result and review records can remain necessary to preserve competition integrity. Transaction and legal records may follow separate obligations.
The operator should publish the applicable privacy contact and process for the live IX6 service. Requests should identify the affected profile or record without sending passwords or unnecessary identity documents through an ordinary message.
Questions worth settling early
Some records may remain for event integrity, disputes, transactions or legal obligations described by the operator.
Use only the official secure verification path, not public comments or team chat.
Yes. The live operator should align it with actual services, providers, retention and applicable obligations before publication.
