Privacy Policy
This notice describes how HQ Sports Platform handles personal data through its website, generic player registry, tournament administration and sporting history services. The platform contact and responsible legal entity details must be made available to individuals before this notice is treated as a complete statutory disclosure.
1. Information collected
Depending on the activity, the platform processes player ID or passport number, names and display name, date of birth where supplied, gender, contact information, player photograph, selected sports, team membership, tournament registration, scores, statistics, awards, disciplinary events, organization account details and security/session information where generated.
2. Purposes
Information is used to register and distinguish players, administer tournaments, manage teams and fixtures, record scores and achievements, provide player histories, maintain authorized accounts, prevent misuse and maintain system security. Information must not be repurposed for unrelated advertising without an appropriate lawful basis.
3. Controller and processor roles
HQ Sports Platform determines certain purposes for the central generic player registry and its ongoing sporting-history service. Participating tournament organizations may separately determine the purposes and rules for their tournaments. For activities performed solely on an organization's documented instructions, the platform may act as a processor. Actual responsibilities depend on the activity and the relevant agreement.
4. Visibility and disclosures
Public tournament pages may show display names, team names, scores, participation, rankings and sporting achievements. Contact numbers, private email addresses, passport/ID numbers, birth dates, login details and internal administration records are not intended for public display. Photographs and other optional publicity should be displayed only where an appropriate permission or other lawful basis exists. Authorized organization users and service providers may receive only information necessary for their responsibilities.
5. Children and guardians
Additional care is required for young participants. Where required, a parent or legal guardian must authorize registration and relevant processing. Children's contact and identity information should not be publicly disclosed. Parents or guardians may submit verified privacy requests on their behalf.
6. Legal basis and choices
Processing must have a lawful basis under applicable Qatar law. Where consent is required, it should be specific, informed and capable of withdrawal. Withdrawing optional publicity permission does not necessarily erase legitimate historical match results or records retained under another lawful basis.
7. Retention
Player sporting histories are intended to continue across tournaments, but personal data is not retained indefinitely merely because it has been collected. Retention must be reviewed against the relevant purpose, applicable obligations and individual rights. Operational records, uploads, logs and backups should be deleted or anonymized under a documented retention schedule. Specific retention periods remain to be formally adopted and published.
8. Security
Access controls, secure authentication, encrypted connections, upload validation, backups, monitoring and role-based permissions are appropriate safeguards for this service. The presence of this notice does not establish that each safeguard has been independently audited or implemented.
9. Hosting and transfers
Hosting, storage, support and backup providers may process information on the platform's behalf. Their identity, processing locations and any international transfers must be documented and disclosed where legally required. The actual hosting and transfer arrangements require confirmation.
10. Your rights
Subject to Qatar's Personal Data Privacy Protection Law, individuals may request information about processing, access, correction, erasure where applicable, withdrawal of consent, or object to certain processing. Requests may require identity verification. A dedicated privacy contact channel must be published and monitored.
11. Security incidents
Suspected incidents should be investigated and contained promptly. Notifications to the competent authority, relevant controllers and affected individuals will be assessed under applicable law.
12. Cookies
Essential login/session cookies may be used for authentication and site security. Additional analytics or tracking, if introduced, should be separately disclosed and managed as required.
13. Changes and contact
Updates will be published with a revised effective date. Privacy requests should be directed through the platform's published support/privacy contact channel. Contact details are pending designation.