Terms page link
The terms page covers account use, while this privacy policy covers data use. When both mention verification, we keep wording aligned so the purpose stays clear.
LEGAL REFERENCE
Privacy Policy For Your i2c Account
i2c keeps casino account data, device signals and Pakistani payment references inside a clear privacy policy, so you know what we collect before you open your account. We...
Account data usePakistani wallet referencesSecurity record handlingPrivacy request route
How Our Privacy Policy Works
Our privacy policy covers personal details you give us, account activity created inside i2c, device data used to protect access, and payment references connected with JazzCash, Easypaisa, SadaPay, NayaPay and Raast. We use this data to run your account, process checks, answer privacy requests, detect misuse, and keep records required where local law permits. We do not write the policy as a
blank statement; it explains why each main data group is needed and how long we keep it when practical. If a banking partner, studio wallet, identity checker or support tool receives data from us, the transfer is limited to the stated purpose and logged by our team. You can ask us to correct inaccurate profile details, close unused contact paths, or explain
a record tied to your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA CHECKS
How We Keep Policy Records Clear
We write and maintain the privacy policy from the way i2c actually handles accounts in Pakistan. The wording is checked against our login flow, wallet verification steps, support scripts and casino wallet...
Process mapping
Each privacy clause is matched to a live account step, such as registration, login, wallet receipt checks or withdrawal verification, so the policy reflects what happens inside i2c.
Local wallet context
We identify JazzCash, Easypaisa, SadaPay, NayaPay and Raast references as transaction records, not extra profile data, and handle them only for checks, support and audit needs.
Access control
Internal access to privacy records is limited by team role. Support can see case details, while deeper identity or wallet records require elevated approval and logged access.
Retention checks
We keep account data only for stated operational, security and legal reasons. When a record is no longer needed, it is removed or detached from direct account identity.
Change tracking
Policy edits are recorded with the date, affected clause and internal owner. This helps us explain what changed if you ask about a privacy update later.
Request verification
Before sharing or changing privacy records, we confirm that the request came from the account holder. This protects your data from social engineering and mistaken disclosure.
PAGE ALIGNMENT
Consistency Across Our Policy Pages
Our privacy policy works with the rest of the i2c legal pages, but it has its own job. Terms explain account rules, cookie text explains browser tools, and this page explains personal...
Cookie page fit
Cookie text explains browser storage and session tools. This policy connects those tools to login security, device recognition and privacy choices inside your i2c account.
Security page fit
Security wording focuses on access protection. The privacy policy explains which security records may be created, why they are used, and how request checks are handled.
Payments wording
Wallet pages may describe JazzCash, Easypaisa, SadaPay, NayaPay and Raast flows. This policy explains the related data trail and who may process it.
Support wording
Support pages explain how to contact us. This policy states what case data we collect, how replies are stored, and when privacy requests move teams.
Studio wallet records
Casino studios may create session and wallet entries. Our privacy policy explains how those records connect to your i2c account for balance checks and disputes.
Update notices
When a legal page changes, we keep dates and cross-links clear. Privacy changes are highlighted where they affect data categories, requests or contact routes.
What This Policy Page Shows
This privacy page is built to make data choices easy to find before you open or keep using an i2c account. The layout separates collection, use...
Clear section labels
Each policy section uses plain labels for collection, use, sharing and storage. You can scan the page without reading legal language just to find your data rights.
Account-first wording
The policy speaks directly about your i2c account, not a vague audience. That keeps every privacy promise tied to registration, login, wallet checks and support cases.
Pakistan context
Local references are named where they matter, including JazzCash, Easypaisa, SadaPay, NayaPay and Raast. This helps you see how wallet records fit the policy.
Request pathway
Privacy contact routes are placed near the policy summary. You do not need to search other pages to ask for access, correction or deletion checks.
Security cues
The page explains why device, login and verification records exist. We connect those records to account protection without asking for more data than the process needs.
Change date area
Policy updates are shown with a clear date and affected sections. This helps you compare new wording with what you read during earlier account activity.
Common i2c Privacy Policy Questions
We collect details needed to create and run your account, such as contact data, login records, device signals, wallet references and support messages. Extra documents are requested only when a check requires them.
We keep wallet references to match transfers, verify withdrawals, answer transaction questions and meet record duties where local law permits. We do not treat those references as public profile details.
Yes. Send a privacy request from your registered contact path and tell us which data group you want to see. We verify account control before sharing any record.
Retention depends on the record type. Account, wallet, security and support data may have different timelines because each serves a different operational or legal purpose in supported regions.
Data may go to payment partners, identity check tools, support systems or casino wallet providers when needed for the stated purpose. We limit each transfer to the required task.
Contact the privacy mailbox with your i2c username and the field that needs correction. We may ask for verification before changing contact details, identity records or wallet links.