E-WARZSH

Your privacy

Who operates the app

E-Warzsh operates E-WARZSH, a football app for leagues, teams, matches, transfers and sports videos in Kurdistan. This notice describes the current account and service data handling.

Information collected

Account data includes your name, phone number, password hash, profile photo, account role, province, branch, area, account status and sign-in/session records. Team and player registrations can include team membership, address, occupation, year of birth and identity documents. Face verification stores a numerical face representation (embedding), model details, capture quality/liveness information and consent records. Notifications use device type and push tokens. The service also stores transfers, appeals, problem reports and notification history. Server logs record requests, IP addresses, timestamps, response status and processing times. These public information pages have no forms and do not collect support messages.

How information is used

We use account and verification information to register and authenticate users, manage profiles, check identity and manage access. Team/player information supports registration, team membership, league participation, matches and transfers. Contact details, device tokens and submitted messages support verification codes, notifications, account assistance, appeals and support. Request and administrative logs help operate, troubleshoot and protect the service.

What other users can see

Signed-in users can view team/player information provided by the app, including names, photos, roles, phone numbers, team membership, location and match information. Some team/personnel responses also include year of birth, address, occupation and document links. Administrators can access records according to their management permissions. Uploaded media and document links must not be treated as private messages or as visible only to the uploader; a person with a working direct link may be able to access the file.

Third-party services

Firebase Cloud Messaging receives device push tokens and notification content to deliver notifications. OTPiq receives phone numbers and verification codes to deliver WhatsApp verification messages. Hosting and network services process requests and store the service data. External video/stream providers receive requests when their content is played. First Iraqi Bank (FIB) is the payment integration associated with earlier transactions; its current app availability is described below. This notice does not assert that an unreviewed mobile SDK collects no additional data.

Identity and face verification

Profile photos and submitted identity documents are stored as uploaded files. Face verification receives numerical embeddings from the app and stores them in the server database with model, quality, liveness and consent metadata. Matching is performed on the application server. This backend does not send face embeddings to Firebase or OTPiq. It has a separate operation to remove the signed-in account’s face enrollment, but deactivating an account does not invoke that operation or delete its photos/documents. Face records and identity documents do not currently have automatic expiry. The mobile capture/model processing and any mobile-only recipients still require confirmation from the app team.

Payments

FIB payments are currently disabled in the app. Disabling payments does not erase earlier transaction records. Where earlier transactions exist, stored information can include phone number, payment identifier, amount, currency, payment status and time, payer name/IBAN and branch/area details. No automatic expiry is currently applied to these records.

Storage and security

Service records are stored in a hosted server database; uploaded photos/documents are stored in server file storage. Website/API connections use HTTPS. Passwords are stored as hashes rather than plain text. Protected API operations use access tokens, and administrator access uses permissions. Request limits and input validation help protect the service. These public pages do not create login sessions, set application cookies, or connect to the account database. These safeguards do not make publicly accessible file links private. No claim is made here that all stored files or backups are encrypted.

Retention

Account, profile, team/player, transfer, document, face-enrollment, notification and earlier payment records currently have no automatic deletion schedule; they remain until explicitly removed through an applicable operation or administrative process. Account deactivation retains these records. Verification codes expire for use, but expiry does not itself delete the associated verification history. Log retention is governed by server log rotation rather than a verified uniform per-user deadline. These informational pages do not store form submissions or use application cookies. The scheduled backup script targets a 14-day retention window for backups it manages; cleanup depends on successful backup jobs. Older/manual backups may remain outside that cleanup. There is no guaranteed date by which a particular person’s data disappears from every backup.

Account deletion

The currently implemented account-status action deactivates the account and matching team memberships and ends the active session. It does not permanently delete personal data. The account-deletion page provides information only and does not accept or process deletion requests. No automatic full-account deletion process, guaranteed completion time or defined post-deletion retention period is currently implemented. Uninstalling the app does not delete server records. Reading these pages does not change or delete your account.

User choices

You can update supported profile details and your profile photo, change your password and sign out through the app’s account features. You can manage camera, photo-library and notification permissions through your device settings; refusing a permission may prevent the related feature from working. Sign-out and permission changes do not remove existing server records. Read the support and account-deletion pages for more information. Do not send passwords or identity documents in a support message.

Children’s privacy

E-WARZSH is intended for people aged 15 and older. Player-registration forms currently accept birth years corresponding to ages 12–99, which is a separate restriction from the app’s intended minimum age. General account signup does not currently collect a date of birth or automatically verify age. Data submitted by users aged 12–17 is handled by the same storage and retention processes described in this notice; no separate automatic minors-data deletion process is implemented. A verified parental-consent or underage-account removal procedure has not yet been established.

Policy updates

Effective date: 10 September 2026. Last updated: 10 September 2026. Changes to this notice will be published on this page with a revised last-updated date. This page does not promise individual email or in-app notification of every policy change.

Contact

Support information

Account deletion information