LEGAL REFERENCE

How rt666 Handles Your Personal Data

Your privacy matters to us at rt666, and this policy sets out exactly what personal data we collect when you open an account, how we store it, and...

Encrypted account dataJazzCash & Easypaisa transactions protectedRight to access your recordsData deletion on request
rt666 How rt666 Handles Your Personal Data

What Data We Collect and Why

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

PRIVACY CONTACT PATHS

Reach Our Data Team Directly

If you have a question about how your personal data is handled, or you want to exercise any of the rights described...

Live Chat Connect through the chat widget on rt666.casino for...
Email Send your written data request or erasure notice...
Account Dashboard Log in to your rt666 account to download...
POLICY TRUST SIGNALS

Why You Can Rely on This Policy

rt666 builds its privacy practices around concrete operational standards rather than vague assurances. The six signals below reflect the actual controls in place for every account opened in...

AES-256 Storage

All personally identifiable fields in our database are encrypted at rest using AES-256. Your JazzCash and Easypaisa identifiers are tokenised...

TLS in Transit

Every data transfer between your browser and rt666 servers travels over TLS 1.3. This applies to login, registration, payment confirmation...

Access Controls

Only staff with a verified operational need can query personal data, and every access event is logged with a timestamp...

Pakistani Payment Rails

Transaction data from JazzCash, Easypaisa, SadaPay and Raast is processed locally before being passed to our core system, reducing the...

Annual Policy Review

This privacy policy is reviewed and updated at least once per year, or sooner if there is a material change...

User-Controlled Deletion

You may request full erasure of your account data at any time. Requests are processed within 30 days, and we...

CROSS-POLICY CONSISTENCY

How This Policy Aligns Across rt666

Our privacy commitments are consistent whether you are reading this page, our cookie notice, or the terms attached to your account. The table below shows how each principle carries across rt666 policy...

01

Data collection scope

Identical across this policy and the account terms — only registration data, payment identifiers, and session logs are collected.

02

Retention periods

12-month active transaction logs referenced here match the retention schedule published in the account terms for JazzCash and Easypaisa records.

03

Third-party sharing

No sale of personal data to third parties — this position is stated consistently in both this policy and the cookie notice without variation.

04

User rights

Access, correction, and deletion rights listed here are mirrored in the account terms section on data subject requests, with the same 30-day resolution window.

05

Security standards

AES-256 at rest and TLS 1.3 in transit are referenced in this policy and in the technical security appendix of the account terms.

06

Cookie handling

Cookies that carry personal identifiers are subject to the same access controls described here; the cookie notice links back to this policy for the full data-handling picture.

07

Policy update process

The annual review cycle and effective-date convention described here apply to all rt666 legal documents, keeping the policy suite synchronised.

How Privacy Works Inside Your rt666 Account

The privacy controls built into your rt666 account are designed to be visible and usable without needing to contact support. The six features below define what...

Privacy Centre Tab

A dedicated tab in your account dashboard aggregates all privacy actions — data download, deletion request, and consent history — in one place so you never need to search for a form.

Consent Log

Every time you accepted or updated a consent preference on rt666, the event is timestamped and stored. You can review this log at any time from the Privacy Centre without raising a support ticket.

Data Export

Request a machine-readable export of the personal data we hold on your account. The file includes registration fields, session history, and a summary of transaction identifiers linked to your profile.

Communication Preferences

Choose exactly which account-related communications you receive from rt666. Marketing preferences are stored separately from operational notices so you can adjust one without affecting the other.

Session Visibility

Your account security page lists every active and recent session, including device type and approximate location, so you can spot and terminate any access you do not recognise.

Linked Payment IDs

The accounts section shows which payment identifiers — JazzCash, Easypaisa, SadaPay, Raast — are currently linked to your profile, with the option to remove any that are no longer in use.

Common Questions About Your Privacy at rt666

We collect your name, email, phone number, date of birth, and the payment identifier you use — such as your JazzCash or Easypaisa number. Device and session data is also logged automatically for security purposes on every login.

We retain core identity records for the period required by applicable law in your region. Transaction logs tied to JazzCash, Easypaisa, SadaPay and Raast are kept for 12 months post-closure unless a longer period is legally required.

We do not sell personal data. We share only what is necessary with payment processors like JazzCash and Easypaisa to complete your transactions, and with fraud-prevention services operating under strict data-processing agreements.

Log in and go to the Privacy Centre tab in your account dashboard. Select 'Download My Data' and we will prepare a machine-readable file within seven days and notify you by email when it is ready to collect.

Yes. Submit a deletion request through the Privacy Centre or email our data team from the address registered to your account. We process deletion requests within 30 days and send written confirmation once the erasure is verified and complete.

Payment identifiers are tokenised before storage, meaning the raw wallet numbers are replaced with a reference token. The underlying data is encrypted at rest using AES-256 and never stored in plain text on our servers.

We update the effective date at the top of this page each time the policy changes. For material changes, we send a notification to your registered email address at least 14 days before the new version takes effect in supported regions.