Privacy Policy For Pakistan Accounts
alanodt keeps this Privacy Policy close to your account flow: it explains what data we collect, why we use it, and how you can ask us to correct...
How We Handle Privacy
This Privacy Policy describes how alanodt handles personal data when you create an account, verify access, browse our lobby, use support, or make payment requests in supported regions where local law permits. We collect only data that helps us run your account, protect sign-in sessions, meet verification duties, process payout checks, and answer privacy requests. Payment rails such as JazzCash, Easypaisa, SadaPay
and Raast may send transaction references, wallet names, phone-number fragments, timestamps, or bank routing details needed to match activity with your account. We do not sell your personal data. When a partner helps with hosting, analytics, security screening, or payment matching, we require that partner to use the data only for the privacy purpose we assign.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ways To Reach Our Privacy Desk
If your privacy question concerns account access, verification data, cookies, or a payment reference, contact us from the channel linked to your alanodt account. That helps us confirm the request belongs to you before we change, export, restrict, or erase any record.
In-account help
Use the help area after login for requests tied to your profile, wallet records, or security checks. We can match your account faster because the message arrives with session and device markers.
Email privacy desk
Email us from the address on your alanodt profile for access, correction, erasure, or cookie questions. Include only the reference numbers needed; please keep card images or wallet screenshots out.
Payment query route
For JazzCash, Easypaisa, SadaPay or Raast privacy concerns, send the transaction time, masked wallet number, and account email. We use those details only to locate the matching record.
Privacy Signals We Maintain
We write this Privacy Policy from the same controls we use in the alanodt account system. The policy is checked when we change cookies, verification steps, payment matching, support tooling, or data...
Data minimisation
We ask for profile, contact, device, and verification data only when it supports account access, security, payment matching, or legal record keeping. Extra data is avoided where the account flow does not need it.
Access control
Privacy records sit behind role-based permissions. Support agents see only what they need for your question, while payment and security teams receive restricted views matched to their task.
Payment separation
Wallet references from JazzCash, Easypaisa, SadaPay and Raast are stored apart from gameplay records where possible. This limits internal exposure while still allowing reconciliation and withdrawal checks.
Cookie labelling
Cookies are grouped by purpose, such as sign-in, fraud control, language choice, or measurement. The policy explains these groups so you know which ones support account operation.
Retention schedule
We keep data for the period needed to run your account, handle disputes, meet record duties, and protect against misuse. When that reason ends, we delete or anonymise the record.
Policy ownership
Our privacy, support, payment, and security teams check policy changes together. That shared check keeps privacy wording aligned with actual alanodt processes instead of abstract legal language.
Aligned With Related Policy Pages
The Privacy Policy works with our other legal pages, but it has its own job: personal data. We keep wording consistent across cookie, terms, security, and account pages...
| Cookie Policy | The Cookie Policy explains browser storage in more detail, while this page explains how cookie data connects to account security, session handling, language preference, and measurement choices. |
|---|---|
| Terms page | The Terms set account rules and service conditions. This Privacy Policy stays focused on personal data collected while those rules are applied, including verification and access decisions. |
| Security page | Security wording covers safeguards such as encryption, monitoring, and permission controls. This policy explains which personal data is touched by those safeguards and why we use it. |
| Payment terms | Payment terms describe transaction conditions. This page explains privacy handling around wallet references, bank routing details, reconciliation logs, and withdrawal checks linked to your account. |
| Support rules | Support rules explain response handling. This Privacy Policy explains the data our team may request, how identity is confirmed, and how privacy requests move through the queue. |
| Account notices | Account notices may appear during sign-in, verification, or payout checks. This page provides the privacy reason behind those prompts and the data categories involved. |
| Promo board | If you open the promo board, this policy explains how preference data, click records, and eligibility checks may be used without turning those records into public profile data. |
Privacy Elements You Can Read
The alanodt Privacy Policy is arranged so you can find the privacy point that matters before sharing more data. Short panels, clear labels, contact routes, and...
Plain section labels
Each policy area uses direct labels for collection, use, sharing, retention, cookies, and your choices. You do not need legal training to find the data subject you care about.
Local context chips
Where payment privacy appears, we name JazzCash, Easypaisa, SadaPay and Raast so the policy matches the rails you actually see in Pakistan account flows.
Request wording
Access, correction, export, restriction, and erasure requests are described in action terms. We explain what we may need from you before we act on the request.
Cookie detail blocks
Cookie sections separate required session storage from measurement and preference uses. That layout helps you understand what supports login and what can be adjusted.
Partner mentions
When vendors assist with hosting, analytics, payments, or fraud checks, the policy explains the purpose of that sharing and the limits we place on their use.
Update marker
Policy changes are linked to the areas that changed, such as cookies, retention, contact routes, or payment privacy. You can check what moved without rereading every paragraph.