Account terms link
The terms explain account rules, while this policy explains data handling behind those rules. When both pages mention verification, this policy clarifies the records used for that process.
LEGAL REFERENCE
Privacy Policy for your rs50 account
rs50 keeps your account, wallet, device and lobby privacy terms in one clear policy so you can open an account with less guesswork. Before you explore the lobby...
Account data useWallet checksDevice securityPakistan support
How this privacy policy applies
This Privacy Policy explains how rs50 handles data linked to account creation, sign-in, wallet activity, security checks, support messages and promotional preferences where local law permits. We use your details to run your account, confirm transfers, protect access, answer service requests and meet record duties that apply to our operation. Payment references can include transaction IDs from JazzCash, Easypaisa, SadaPay or Raast,
but we do not ask you to send card secrets through chat. Some checks may involve device, IP, browser and session records so we can spot unusual access and keep account activity aligned with your profile.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA CHECKS
How we keep policy records accurate
We write this policy from the systems we operate, not from generic wording. Our privacy checks cover account creation, login security, payment reconciliation, support handling and message settings, then we adjust this...
Workflow matching
Our policy wording is matched against actual account screens, wallet steps and support forms. If a field is removed or added, the privacy text is checked against that changed flow.
Local payment context
We mention JazzCash, Easypaisa, SadaPay and Raast because those rails create transaction references we may need for account support, reconciliation and privacy request verification in Pakistan.
Access security
Session records, device signals and login timestamps help us identify account access patterns. We use those records to protect your profile and to answer questions about unusual sign-in activity.
Support handling
Support messages may contain personal details, so we keep them within service channels and use them for your request. We train support replies to avoid asking for wallet secrets.
Change control
When privacy wording changes, we keep the new text aligned with product and support updates. Material changes are written plainly so you can understand the effect on your account.
Request verification
Before we discuss account records, we may verify your identity through details already linked to your profile. This protects your private data from another person using your name.
POLICY ALIGNMENT
Consistency across rs50 legal pages
Our privacy page sits beside the terms and cookie pages, but it has its own purpose. This section explains how the policy stays consistent with related legal pages while focusing only on...
Cookie page link
Cookie wording covers browser storage and similar tools. This privacy page connects those tools to account security, preference settings and service measurement without repeating every cookie category.
Payment wording
Wallet instructions belong in service screens, while privacy wording explains transaction references, verification needs and retention purposes. That separation keeps your payment steps and data rights easier to read.
Promotion settings
If we send account messages, this policy explains preference handling and contact data use. Separate promotional pages may describe current offers, but privacy controls remain described here.
Security procedures
Security pages may describe access protection in operational terms. This policy explains the related personal data, such as device records, login timestamps and support verification notes.
Retention language
Where another legal page mentions record keeping, this policy explains why account, wallet and support records may be retained for service, dispute handling or legal duties.
Update notices
When a related legal page changes, we check whether privacy wording also needs adjustment. The aim is simple: your data choices should not be scattered across unrelated text.
PAGE MARKERS
Privacy layout you can scan
We designed this privacy page so you can find data topics quickly without reading unrelated product copy. The visible markers below show where account, security, wallet, support and...
Account section
This area explains the details you provide when opening or...
Wallet section
This marker covers transaction references from JazzCash, Easypaisa, SadaPay and...
Security section
Here we explain device, session, IP and login records in...
Support section
This part explains how messages, attachments and request histories are...
Preference section
This marker explains how we handle service alerts and optional...
Rights section
This area explains how to ask about access, correction or...
Common Privacy Policy questions
We may ask for contact details, account identifiers, security credentials and location-related signals needed to provide access in supported regions. We use those details to create, protect and maintain your account.
No. We may store transaction references or confirmation records connected to JazzCash, Easypaisa, SadaPay or Raast, but you should never send wallet PINs, passwords or one-time codes to support.
Device, browser, IP and session records help us recognise your account access pattern and investigate unusual activity. These records also help support answer questions about failed logins or account access changes.
Yes, you can contact support to request correction of eligible account details. We may verify the request against your registered contact method before making changes to protect your profile.
Retention depends on the record type and legal or service need. Account, wallet and support records may be kept while needed for service, dispute handling, security checks or required record duties.
Contact us through the in-account support path when possible, or email us if you cannot sign in. Use your registered contact detail so we can verify the request securely.