How We Handle Your Personal Data
Your account with rami slots holds real details — a name, a contact number, a payment handle — and this policy sets out what we do with every...
Where Our Policy Applies And Why
This privacy policy sits on the same footing as the rest of rami slots: we open the doors where local law permits, and we apply that same standard to how your details are gathered. When you register, we keep your name, contact number, date of birth and the payment handles tied to JazzCash, Easypaisa, SadaPay, NayaPay or Raast. That record lets us
verify you, settle withdrawals and answer a query months later. We do not sell your data. We share it only with processors who help us run the account — payment rails, identity checks and hosting — and only as far as the job needs. If a regulator in a supported region asks for a lawful record, we hand over what the law
requires and nothing beyond it. You can ask us to correct, export or erase what we hold, and we will say plainly if a legal duty prevents us from deleting something.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Data Handling Standards We Follow
We keep our data practices plain, because you cannot judge a platform from its front page alone. Every claim on this page traces back to something you can verify yourself: your own...
Rails you already use
Money moves through JazzCash, Easypaisa, SadaPay, NayaPay and Raast, so your details stay inside systems you already deal with every day and can check on your own handset.
Verification before payout
We match the name on your account against your payment handle before any payout leaves. That single check is why a withdrawal occasionally takes longer to clear than you expect.
Encrypted sessions
Pages load over an encrypted connection, and sign-in credentials are held in hashed form rather than plain text, so a copied database would not hand your password to whoever found it.
Two-step sign-in
Switch on a second step at sign-in and we send a code to your number. It adds one tap to your routine and leaves a stolen password useless on its own.
Pakistan support hours
Our team works Pakistan hours, seven days a week, by chat and email. A question about your own record stays with the people who handle it, without a handover to another queue.
We never sell your record
Your data is not sold to brokers or advertising networks. Sharing stays only inside the processors that run payments, identity checks and hosting for your account.
Same Rules On Every Policy Page
Privacy wording should not shift as you move around the site. Our cookie page, our account terms and this policy describe one set of rules, written by the...
| Account Terms | The terms you accept at registration cover how the account runs day to day. Retention wording here repeats itself there, so you never read two versions of the same rule. |
|---|---|
| Cookie Settings | Our cookie page lists each category we set and what wakes it up. Those categories match the ones named in this policy, so switching one off behaves as described here. |
| Withdrawals And Timing | Payout wording lives in one place. The verification checks on the withdrawal page are the same checks this policy cites when explaining why identity records are held for longer. |
| Security Practices | Sign-in steps, hashed passwords and encrypted sessions appear on our security page in more depth. This policy only sets out which of those records we keep and for how long. |
| Data Requests | The route for a copy, correction or deletion is described the same way on the contact page and inside your profile. One process, several entry points, no conflicting instructions. |
| Market Availability | Where we operate is stated across the site in matching words: supported regions only, where local law permits. The same phrasing appears here, so no page promises more than another. |
| Revision Record | When a policy changes, the new version replaces the old one everywhere at once. The updated-date line near the top of each page shows which revision you are reading. |
What You See On This Page
This page is built to be read on a phone first. Paragraphs stay short, each block carries a plain heading, and every right we mention links...
Plain headings
Each block carries a heading that says what the block contains, so you can jump straight to retention, sharing or deletion without reading from the first line.
Short paragraphs
Long obligations are broken into short paragraphs. It reads faster on a phone screen and makes an unusual sentence easier to spot when something has changed since your last visit.
Local rail chips
A single row of chips names the rails we work with — JazzCash, Easypaisa, SadaPay, NayaPay and Raast — so you can see at a glance whether your own route is covered.
Updated-date line
One line near the top records the date of the current revision. Compare it with your last visit and you know within a second whether anything on the page has moved.
Linked contact routes
Every section that mentions a right you hold links to the route that exercises it, whether that is chat, email or the request form sitting inside your profile.
Phone-first layout
Buttons and headings are sized for a thumb, and the chip row wraps instead of scrolling sideways. Plenty of you read this policy on a handset, so we built it that way first.