Privacy Policy for Your y31d Account
y31d keeps your account, lobby and wallet privacy terms in one clear policy, including how we handle data linked to JazzCash, Easypaisa, SadaPay and Raast. Read this before...
How We Treat Your Personal Data
This Privacy Policy explains how y31d collects, uses, stores and shares data tied to your account where local law permits. We process account details, device signals, session records, wallet references and contact messages so your access can be checked, your balances can be reconciled and your requests can be answered. We do not sell your personal data. We may share limited records
with service partners that help us run login security, wallet checks, fraud controls, chat handling and technical hosting. Those partners only receive the data needed for their task. If you ask us about your privacy rights, we will first confirm that the request comes from you or from someone allowed to act for you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ways to Reach Our Privacy Team
Privacy requests need the right channel, because we must confirm the account before discussing personal data. Use the contact route that matches your access level. If you cannot log in, give us enough detail to locate the account without sending sensitive wallet codes.
Account email
Send a privacy request from your y31d profile email so we can match the message to your account. We may ask for a fresh security check before sharing data.
Live chat
Use chat when you need to ask how a privacy request works before sending documents. Our team can explain the next step without displaying private records inside the chat window.
Security form
If your account access feels unsafe, use the security form and mark the request as privacy related. We will prioritise identity checks before discussing balances or wallet records.
How We Keep This Policy Accurate
We write this policy from our own account and wallet flow, not from a template alone. Our team checks wording against the data we actually collect during sign-in...
Account data map
We map each account field to a clear purpose, such as login security, wallet matching or support handling. This helps...
Wallet record checks
JazzCash, Easypaisa, SadaPay and Raast references are treated as transaction records, not public profile data. Access is limited to staff...
Session logs
Device and session logs help us detect unusual access patterns. We use them for security checks and technical fixes, not...
Staff access control
Team access to private records is assigned by role. We keep internal checks around who can view account details, wallet...
Policy change checks
When we change account, wallet or support flows, we check whether this Privacy Policy needs an update. The aim is...
Request handling
We answer privacy requests after confirming account ownership. This protects your data from being shared with someone who only knows...
How This Policy Fits Our Legal Pages
This page explains privacy only, while our other legal pages handle different account topics. We keep the wording aligned so your data rights, account rules and wallet checks...
Privacy Layout You Can Scan
We design this page so you can find the privacy point you need without digging through unrelated copy. Each visible block focuses on one part of...
Plain section names
Section labels use direct privacy wording so you can move quickly from data collection to contact routes. We avoid vague labels when account data is being discussed.
Short badges
The badges near the hero summarise the policy focus at a glance. They point you toward account data, wallet records and privacy contact paths.
Local wallet context
Where wallet records appear, we name the Pakistani rails involved. This makes the privacy wording clearer for JazzCash, Easypaisa, SadaPay and Raast activity.
Rights language
We explain how to ask about your data without burying the route in legal phrasing. You can contact us from the account email or support channel.
Security cues
Lock and shield cues mark sections that discuss access checks, device records and identity confirmation. These cues help you spot sensitive data handling quickly.
Update trail
Policy update areas explain why wording may change when account tools or wallet flows change. We keep the privacy text tied to actual y31d operations.