Same Definitions
Terms such as account, rail and supported region mean the same thing here as they do on our terms of use page, so nothing shifts between documents.
LEGAL REFERENCE
How sun slots Handles Your Account Data
Your data terms sit here in one place, written in plain language so you can see what we collect, why we keep it and how our team handles...
Account dataPayment detailsCookie choicesContact rightsPolicy updates
What This Policy Covers
We wrote this policy for sun slots and for the account you open with us. It covers the details you hand over at registration — your name, date of birth, contact number and chosen payment rail — along with the records our systems create while you use the lobby, such as session times, device type and game activity. It explains what we
do with those records, who inside our team can see them and which processors receive them, for example payment handlers and identity checks. Our posture is jurisdiction-first: we apply the rules that reach our brand, and where local law permits we hold your records only while a clear purpose exists. You can ask what we hold, ask for a correction, or ask
us to close the account and remove what we are no longer required to keep.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HOW WE HANDLE IT
How We Draft And Check These Terms
Nothing on this page came from a template. Our own team drafts each clause, support agents test whether the wording answers the questions they really receive, and every revision is dated so...
Plain-English Drafting
Every clause on this page was written by our own content team, then checked against the wording our support agents actually use when you ask about your records.
Version Stamps
Each revision carries a date and a short changelog line at the foot of the page, so you can see what moved between versions.
Named Handlers
Data questions land with a named team rather than a faceless queue, and you get the same handler back when you reply to our first answer.
Local Rails Only
We name only the routes we support for Pakistan — JazzCash, Easypaisa, SadaPay, NayaPay and Raast — and never list a rail you cannot use.
We Do Not Sell Records
We do not sell your account records. Sharing happens with processors who need the detail to clear a transfer, check an identity or keep the service running.
Account Control
You can open your profile at any time to see what we hold, change your contact number, or close the account and choose what we delete.
MATCHING PAGES
Consistency Across Our Policy Pages
Our policy set shares one vocabulary. The terms you read here about records, retention and sharing are the same terms used on our cookie and account pages, so a reader who moves...
Shared Date Stamps
When we change how we describe data handling, the same revision date appears here and on the cookie notice, keeping the whole set in step.
One Contact Route
The support card further up uses the same address listed on our other policy pages, so a request sent from any of them reaches the same team.
Consistent Rails
Wherever our policy pages name JazzCash, Easypaisa, SadaPay, NayaPay or Raast, the surrounding wording matches, so you never have to compare two descriptions.
Matching Headings
Section headings about what we hold and how long we keep it repeat across our policy set, which makes a long document easier to skim on a phone.
Shared Escalation Path
If a first answer does not settle your question, the escalation path is identical on every policy page and leads to the same senior agent.
Aligned Language
Every page in this set is written in the same Pakistani English, so no paragraph reads as though it arrived from a different document.
Layout Choices On This Page
How this page is built matters as much as what it says. Long clauses are broken into short blocks, every heading jumps to its own place...
Summary Band
The opening band gives a short summary of the terms below, so you can read the shape of our data handling before you scroll.
Anchored Sections
Every heading links to its own anchor, so you can jump straight to retention, sharing or account closure without reading the full document.
Plain Wording
We avoid legal shorthand where a normal sentence works, and where a term is unavoidable we define it the moment you meet it.
Mobile Reading
Paragraphs break early on small screens and the chip row wraps instead of scrolling sideways, so the page stays readable on a Pakistani phone connection.
Change Log Block
A running block near the foot lists each revision with a date and one line describing what changed, which you can check before you sign in.
Contact Card
The support card sits close to the end, with channels, hours and expected reply times, so you never finish reading without knowing where to write.
Privacy Points Readers Raise
It covers the personal details you give us when you open an account — name, date of birth, contact number and payment rail — plus the records our systems create while you play.
Only the routes we support for Pakistan: JazzCash, Easypaisa, SadaPay, NayaPay and Raast. Each is named so you know which processor may receive the limited detail needed to clear a transfer.
Yes. Message support from your registered address and we will send what we hold on your account, usually within one working day and always with a written follow-up you can keep.
Retention depends on the purpose. Session and device logs turn over far quicker than identity or transfer records, and we explain the reasoning whenever you ask about a specific category.
Processors handle payments and identity checks, and a small number of technical suppliers keep the lobby online. We name the categories rather than listing companies we may change.
Every revision gets a date and a single line in the change log, and material changes are flagged in your account inbox before they take effect where local law permits.
Write to our support team and ask. If the first reply misses the mark, say so and the request moves to a second agent on the same escalation path listed across our policy pages.