LEGAL REFERENCE

Privacy Policy for Your rc20 Account

rc20 keeps one privacy path for account access, casino activity, slot sessions, sportsbook records and support chats, so you know what data we collect before you open an...

Account data usePayment-context recordsSupport privacySecurity checks
rc20 Privacy Policy for Your rc20 Account

How We Treat Your Personal Data

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

HELP ROUTES

Privacy Questions and Contact Paths

You can ask us about your personal data without using a public comment area or social thread. We separate privacy requests from ordinary lobby questions, then match your message to the account details you provide so we can answer safely. If we need more proof, we ask for the smallest extra record that can confirm control.

Team online

Privacy Email

Use our privacy mailbox for access, correction or removal requests tied to your rc20 account. Include your registered contact detail and avoid sending card photos or extra documents unless our team asks.

Live Chat Path

Start chat from your signed-in account when your question concerns recent activity records. Our team can flag the case for privacy handling while keeping ordinary lobby support separate.

Payment Record Query

If your privacy question involves JazzCash, Easypaisa, SadaPay or Raast references, share only the transaction code and date. We use those details to locate records, not to publish them.

CHECKED COPY

How We Keep This Policy Current

Our privacy wording is maintained by the team that works with account access, security checks, payment references and support records. That matters because the policy has to match...

Operational Input

We base privacy wording on real rc20 workflows, including sign-in logs, wallet references, support tickets and session records. The policy...

Local Context

Pakistan payment references are named plainly, including JazzCash, Easypaisa, SadaPay and Raast. We explain them as privacy context, not as...

Security Alignment

Account protection checks use device, session and access signals to reduce misuse. The policy describes those records so you understand...

Limited Sharing

Where outside service providers help with hosting, fraud checks or support tools, we restrict the data they receive. They are...

Change Tracking

Policy edits are checked against current account flows before publication. If we adjust data handling, the privacy page is updated...

Support Feedback

Questions from your privacy requests help us improve wording. If a phrase causes confusion, we refine it so future account...

Consistency Across Our Policy Pages

This Privacy Policy sits beside other legal pages, but it has its own job. It explains data collection, use, sharing, storage and request handling. We keep related pages...

Terms Page
Our terms describe account rules and service use, while this page describes data handling. Where both pages mention account checks, the privacy wording explains the personal-data side.
Cookie Page
Cookie wording focuses on browser storage, analytics and preference tools. This Privacy Policy connects those signals to account protection, support handling and service security.
KYC Mentions
Where identity checks are required, we explain the record purpose here. We do not ask for extra documents unless a lawful or security need applies.
Payment References
Wallet and bank-rail references may appear in transaction logs. This page explains how those references are stored, checked and limited inside rc20 systems.
Support Scripts
Support responses follow this policy when your question involves access, correction or removal. That keeps chat answers aligned with the written privacy commitments.
Account Security
Security controls may use device and session records. This page explains those records as protection tools, not as a hidden profile for unrelated purposes.
Regional Access
Where local law permits access, our privacy wording still applies to account data created through rc20.today. Regional availability does not remove your data request path.
LAYOUT CUES

Visible Privacy Elements on This Page

We designed this policy page so you can spot the privacy points that matter before you create an account. The layout separates collection, sharing, contact routes and request...

Plain Labels Section headings tell you which privacy point is being explained...
Short Chips Context chips highlight Pakistan rails like JazzCash, Easypaisa, SadaPay and...
Request Path Contact routes are grouped near the front of the page...
Readable Blocks Paragraphs are kept compact because privacy pages should be usable...
Update Signals When policy wording changes, we aim to make the changed...
Account Focus Examples stay tied to rc20 account activity, support messages, session...

Privacy Questions About rc20

We collect account details, contact records, device and session signals, wallet references, game activity logs and support messages. Each category is used for account operation, security checks, service delivery or legal duties.

No. We do not sell your personal data. Limited sharing may happen with providers that support hosting, fraud checks, payments or customer help, and only for the service purpose involved.

Payment references such as JazzCash, Easypaisa, SadaPay or Raast codes are stored as account records. We use them to match requests, check transaction status and answer privacy questions.

Yes. Send a privacy request from your registered contact detail or signed-in account. We may verify control first, then provide the relevant record or correct details where appropriate.

We keep records only for as long as needed for account operation, security, dispute handling and legal duties. Some records may be removed sooner when no longer needed.

Support will route privacy matters away from ordinary lobby help. We check account ownership, limit what is shared in chat and keep the request tied to the correct rc20 account.