Privacy Policy for your rc 21 account
rc 21 explains how your account data, login activity and transaction records are handled when you open an account from Pakistan where local law permits. Read this policy...
Privacy posture for Pakistan accounts
This Privacy Policy describes how rc 21 collects, uses, stores and protects data linked to your account in supported regions of Pakistan. We collect only what we need to run account access, security checks, transaction handling, support replies and product availability where local law permits. That may include your name, phone number, email address, device signals, login records, account preferences and payment
references from local rails. We do not sell your personal data. We share limited data only with service providers that help process account checks, payments, fraud controls, platform hosting or support. When you ask us to correct, access or remove eligible data, we check your identity first so another person cannot make changes on your behalf.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact us about your data
Privacy questions need a clear route, so we keep contact paths separate from lobby help. When you contact rc 21 about your data, include the email or phone linked to your account and describe the request plainly. We confirm account ownership before discussing personal records, transaction references or security events.
Email privacy desk
Send us your account email and the data question you want answered. We match the request to your rc 21 profile before sharing any account data response back.
Live chat handoff
If you start with chat, our team can route privacy requests to the right queue. Chat will not expose private account records until ownership checks are complete.
Payment record query
For JazzCash, Easypaisa, SadaPay or Raast references, share the transaction time and amount. We use those details only to locate the relevant account record.
How we keep the policy current
Our Privacy Policy is written from the way rc 21 actually handles accounts, not from a generic template. We align the wording with support scripts, security checks and payment record flows used...
Process mapping
We map each data category to a real account task, such as login security, profile upkeep, support replies or transaction matching, so the policy stays tied to operational use.
Local rail context
JazzCash, Easypaisa, SadaPay and Raast records are described as references, not full banking access. We keep only the details needed for reconciliation and account checks.
Security checks
Access requests are handled after identity confirmation. This protects your account from another person asking for profile data, payment references or support history without permission.
Retention wording
The policy explains why some records may stay for legal, security or accounting reasons. When retention is no longer needed, data is removed or de-identified where practical.
Plain English
We use direct Pakistani English so you can see what is collected, why it is used and how to contact us without decoding legal phrasing.
Change tracking
When we adjust privacy wording, we update the page date and keep the new wording focused on account data handling, not general product promotion.
Consistent rules across legal pages
The Privacy Policy connects with other rc 21 legal pages, but it has a separate purpose: personal data handling. We keep definitions, contact routes and account references consistent...
| Terms alignment | Where account access rules appear in our terms, this policy explains the data behind those checks, including identity confirmation, login records and account protection activity. |
|---|---|
| Cookie alignment | Cookie wording links to device and session data in this policy. We separate essential session controls from optional analytics so your privacy choices are easier to understand. |
| Transaction alignment | Transaction references are described the same way across legal pages. JazzCash, Easypaisa, SadaPay and Raast records are used for matching, support and security checks. |
| Support alignment | Support pages may ask for contact details, but this policy explains why we need them, how replies are logged and when account ownership is checked. |
| Security alignment | Security wording across the site points back to this policy for data impact, including device signals, failed login attempts and unusual account access checks. |
| Regional alignment | Where access is limited to supported regions, this policy explains how region signals may be used to keep account handling aligned with local law. |
| Rights alignment | Your access, correction and deletion requests are handled through the privacy route, even when the request starts from another legal or support page. |
What this page makes easy
This page is arranged so you can find privacy answers quickly before opening or managing an rc 21 account. We keep the layout focused on practical actions: what...