How ethereum casino Handles Your Account Data
This policy explains what ethereum casino records when you open an account, how that data travels through our systems and how long it stays with us. You will...
The Rules Behind This Privacy Policy
We treat your account details as something you lend us, not something we own. When you open an account from Pakistan we record only the basics needed to run it: your name, date of birth, phone number, email address and the payment references that appear when you move money through JazzCash, Easypaisa, SadaPay or Raast. Transaction logs sit with our payments team
so any query can be traced fast. Where local law permits, and depending on the rules that apply in your region, some requests are handled differently, and we explain any limit in writing before we act. Records stay only as long as a rule, a dispute or an audit needs them, after which we delete or anonymise the files. Marketing choices sit
apart from your account record, so opting out of messages never blocks your access to the lobby.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reaching Our Data Desk
Something on your record looks wrong? Tell us and we will trace it with you. Privacy requests reach a named team from 09:00 to 23:00 Pakistan time, every day, by live chat inside your account and by email. Most questions are answered within one working day, with a written outcome once a request closes.
Live Chat
Open your account and tap the chat bubble to reach a data agent. Chat is the quickest path when a payment reference looks missing, and the transcript stays on your record.
Email Desk
Write to our privacy mailbox for anything you want in writing, from a copy of your record to a correction. Share your account number and we confirm receipt the same day.
Account Tickets
Raise a ticket from the help panel for deletion, portability or cookie questions. Every ticket carries a reference you can quote when you follow up with our desk.
Who Compiles And Checks This Policy
The policy is written by the team that builds your account flow, not by an outside agency. Drafts pass a data-protection check before they go live, and each change carries a date...
Policy Owner
One named manager signs off every edit to this page. If wording changes the way your data is used, that manager writes the short reason beside the update.
Protection Check
A protection lead checks each draft against the rules that apply to your region before the page goes live, and flags anything needing a local variant.
Plain Wording
We rewrite legal sentences into everyday English and keep an Urdu contact line for readers who would rather ask a question in their own language.
Change Dates
Every revision is stamped with the day it took effect, so you can compare the copy you agreed to with the copy sitting here now.
Retention Window
Our retention schedule is shared with the payments and fraud desks so nobody keeps a file longer than the rule, the dispute or the audit allows.
Region Variants
Where local law permits a different approach, we publish a variant of this page and link it clearly, instead of assuming one version covers everyone.
How This Policy Matches Our Other Pages
Privacy wording only works when it agrees with everything else you accept. The language here is kept in step with our account terms, cookie notice, payment terms and...
| Account Terms | The account terms say what you may do with your login; this policy says what we may do with the data behind it. Both are read together. |
|---|---|
| Cookie Notice | The cookie notice lists each tag we drop and why. This page explains what those tags collect once they are running on your browser. |
| Payment Terms | Payment terms cover timing and charges for JazzCash, Easypaisa, SadaPay and Raast. Privacy wording covers the reference numbers those rails hand back to us. |
| App Permissions | The permissions page shows what the mobile build asks your handset for. Anything the app reads is described in the same words here. |
| Complaints Path | If a data question reaches a complaint, the complaints path sets the timeline while this policy sets what we may disclose while it runs. |
| Security Page | The security page covers logins, two-step checks and device sessions. This policy covers what we log when those checks happen on your account. |
| Account Closure | Closing your account stops play but not every record. The closure block explains which files are erased at once and which stay for a set period. |
Visible Elements On This Policy Page
You should not need a specialist to read your own policy. Everything here is built for quick scanning: a dated banner, short headed blocks, a summary strip close...