Data We Collect
The list here is identical to the one shown before you tick consent at registration, including account details, device data, login records and settlement references from the wallet you chose.
LEGAL REFERENCE
Your Data, and How We Handle It
This page sets out what account details we hold when you register at vyro casino, why we hold them, how long they stay, and the choices you keep...
What we collectWhy we hold itHow long it staysWho can see itHow to ask us
Where Local Law Sets the Pace
Nothing on this page overrides the law where you live, and we will not pretend otherwise. Where local law permits something, we follow that permission. Where a rule in a supported region asks more of us, we take the stricter path, even when that means handling your records differently from someone else's. You keep real control, not a decorative tick box. You
can ask what we hold, ask for a copy, ask for corrections, and ask us to close your account and remove what we are not required to keep. Settlement references tied to JazzCash, Easypaisa, SadaPay and Raast, plus anything we must retain for tax or dispute reasons, stay for the period the law sets. Everything else goes when the account closes.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHO WRITES THIS
The People Accountable for These Words
The people who run our account systems write these pages, not a copywriter working far from the code. Our compliance and support leads sit together, check each clause against how the platform...
Named Owners
Each clause has a person behind it. If a section changes, the owner signs it off and their role goes in our internal log, so accountability never disappears into a faceless team.
Plain Wording
We avoid legal padding where ordinary English works better. Terms such as retention, processing and disclosure get explained in the same paragraph they first appear, so you never need a dictionary.
Version Dates
Every published version carries a date at the foot of the page, and we keep earlier drafts available to you on request, so you can compare what moved and when it moved.
Local Rails Only
The payment names on this page are the ones you actually use: JazzCash, Easypaisa, SadaPay, NayaPay and Raast. We describe how each one touches your records, without vague talk about unnamed partners.
Access on Request
Ask for your data and get a structured file rather than a screenshot. We send account details, transaction references and support history in a readable format within the period local law allows.
Escalation Path
If an answer does not satisfy you, ask for the escalation step and your case moves to a senior handler outside the first-line desk, with a written response rather than a phone note.
CONSISTENT PROMISES
Same Promises Across Our Pages
Our terms, cookie notice and this policy should never contradict each other, and when they do we correct it quickly. One shared glossary, one retention table and one contact route keep the...
Why We Hold It
Purposes are grouped into running your account, meeting legal duties, preventing fraud and improving the platform. Those same four headings appear on our terms page, so the logic stays recognisable.
Who Can See It
Staff access is limited by role. Support sees your account history, engineers see system logs without wallet identifiers, and nobody outside those groups touches your records without a logged reason.
Retention Periods
The table on both pages lists the same clock: account data for the life of your profile, settlement references for the statutory period, and marketing preferences until you withdraw them.
Your Choices
Correction, copies, closure and marketing withdrawal are offered here and repeated inside your account settings, so you can act from either place without emailing us first.
Security Steps
Encryption in transit, hashed passwords, device verification on new logins and staff access logs are described in the same words on both pages, so nothing is softened for marketing.
Contact Route
One mailbox, one chat window and one phone line serve every page. Whichever link you follow, your request lands in the same queue with the same response window.
What You'll Spot as You Read
Length should not decide whether a policy gets read, so we built this page around movement. Summary cards sit near the opening, numbered clauses follow in...
Summary Cards
Short cards open each block and give you the gist in a single line, so a quick scan tells you whether the section matters to your account today or can wait.
Numbered Clauses
Clauses carry steady numbering, which makes them easy to quote when you contact support or reference a point in a complaint about how we handled your records.
Jump List
A sticky jump list follows you down the page on desktop and folds into a menu on mobile, so you never scroll through sections that have nothing to do with your question.
Retention Table
A single table shows how long each record type stays with us, from login history to wallet settlement references, with the legal reason printed beside every row.
Rights Checklist
Your four main requests appear as a checklist you can copy into an email or chat message, which cuts the back-and-forth and gets your case opened faster.
Change Log
A short log at the foot of the page names what moved and on which date, so returning readers can see at a glance whether anything affects the data they already gave us.
Questions We Get About Your Data
Your registration details, device and login records, support conversations, and settlement references for the wallet you use at payouts, whether that is JazzCash, Easypaisa, SadaPay, NayaPay or Raast.
No. Your wallet credentials stay with JazzCash, Easypaisa, SadaPay, NayaPay or Raast, and we only ever see the confirmation, amount and reference number that the rail returns once a transfer completes.
Most profile data goes within the window local law allows, but settlement references and anything tied to tax or an open dispute stay for the statutory period, then get deleted in the next scheduled sweep.
Yes. Ask through chat or the privacy mailbox and we send a structured file covering your profile, transaction references and support history, normally well inside the period the law sets.
Some hosting and fraud-check services sit outside the country. When that happens we use contractual terms that limit what those providers may do with your records, and we name the categories in the section above.
New devices need verification, passwords are stored as hashes rather than readable text, sessions expire on inactivity, and staff access to account records is logged so unusual viewing stands out.
Open a ticket with support and tag it private data. If the first reply does not settle it, ask for escalation and a senior handler takes over with a written answer inside the same week.