Account terms
The account terms explain eligibility and account use. This Privacy Policy matches that wording by showing which account details we collect and how they support secure access.
LEGAL REFERENCE
Privacy Policy For Your y05 Account
y05 puts your account data, payment records and privacy choices in one clear policy for Pakistan. Open your account with confidence where local law permits, then use this...
Pakistan privacy scopeAccount data usePayment record careSupport contact path
How We Handle Your Data
This Privacy Policy explains how y05 collects, uses, stores and shares data connected with your account in supported regions of Pakistan. We collect details you provide during account setup, identity checks, login activity, device signals, gameplay records, wallet activity and support messages. We use that data to operate your account, process payout requests, detect account misuse, answer privacy questions and keep the
lobby working on mobile and web. Payment records linked with JazzCash, Easypaisa, SadaPay and Raast are handled as transaction data, not public profile content. We may keep some records for legal, security and accounting needs, then remove or anonymise them when they are no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Contact Us About Privacy
Privacy questions should reach the team that can check your account trail safely. Use the channel that matches your request, include your account name only when needed, and avoid sending full wallet screenshots unless we ask for a specific cropped record.
Team online
Privacy inbox
Email us for access, correction or deletion requests. We may ask for account checks before changing stored data, so only you can request changes tied to your y05 profile.
Live chat handoff
Start with chat when you need a quick route to the privacy team. Chat staff can confirm the next step, but sensitive data changes are handled through a verified request path.
Payment privacy query
If your question involves JazzCash, Easypaisa, SadaPay or Raast records, share the transaction reference only. We use it to locate the record without exposing extra wallet details.
POLICY CHECKS
How We Keep The Policy Current
We treat this page as a live account document, not a forgotten legal page. When our account flow, verification process, payment routing or support handling changes, we check...
Operational input
Our account, payments and support teams feed practical changes into policy checks. That keeps the wording close to how y05...
Plain language
We avoid legal phrasing that hides the point. Each privacy section is written so you can see what data is...
Local context
Pakistan payment rails are named because they affect record handling. JazzCash, Easypaisa, SadaPay and Raast transactions create references we may...
Security checks
Policy wording is matched against account protection steps such as login monitoring, device checks and payout verification. We explain these...
Change tracking
When we adjust this page, we check related pages for matching terms. You should not see one privacy promise here...
Support feedback
Repeated privacy questions from you help us improve the page. If a section creates confusion, we rewrite it so future...
PAGE ALIGNMENT
Consistent Wording Across Policy Pages
Your privacy rights should not change from one y05 page to another. We align this Privacy Policy with our account terms, cookie wording, support paths and transaction rules so each page explains...
Cookie page
Cookie wording connects with this policy through device and session data. We keep both pages aligned so browser tracking, login memory and preference tools are described consistently.
Security page
Security wording explains protection steps; this policy explains the related data use. Login checks, device signals and account alerts are covered from a privacy angle here.
Withdrawal rules
Withdrawal wording may mention verification steps. This policy explains why identity, wallet references and transaction history can be needed before a payout request is released.
Promo terms
Promo pages may require account checks before an offer is applied. This policy explains how those checks use account status, activity records and eligibility data.
Support page
Support wording tells you how to reach us. This policy adds what happens to messages, attachments and request history after you contact the y05 team.
App wording
Mobile access wording may mention device behaviour. This policy explains how app signals, session data and security logs help keep your account available.
LAYOUT SIGNALS
Visible Policy Touchpoints On y05
We designed the policy page so privacy details are easy to scan before you open an account. The layout separates legal scope, contact routes, data categories and common...
Hero badges
The badges at the start point to the main privacy...
Policy scope block
The main notice explains collection, use, storage and sharing in...
Contact cards
Contact cards separate privacy requests from general support. That keeps...
Trust markers
Trust markers show how we keep the wording current. They...
Comparison rows
Comparison rows show where this policy connects with other y05...
FAQ area
The question area covers requests you are likely to raise...
Privacy Policy Questions Answered
We collect the details you enter, login records, device signals, verification data, wallet references and support messages. We use them to run your account, protect access and handle requests.
Transaction references help us match wallet activity to your y05 account, confirm payout requests and resolve payment privacy questions. We do not display those records as public profile content.
Yes. Contact us through the privacy inbox with the detail you want checked. We may verify your account first, then update records where the request is valid.
We keep request records for as long as needed to answer you, prove the action taken and meet legal or accounting needs. Older records may be deleted or anonymised.
We share only what is needed to process or verify a transaction, such as a reference or account match. The exact data depends on the rail involved and the request type.
Send a deletion request through the privacy contact path. Some records may need to stay for security, legal or accounting reasons, but we will explain what can be removed.