LEGAL REFERENCE

The Privacy Policy Sitting Behind Your Account

This page is where we spell out how 777 crazy collects, uses and stores your account details. You'll see what we log when you open your account, how...

Plain-language clausesRegion-aware rulesYour request routesNo data selling
777 crazy The Privacy Policy Sitting Behind Your Account

How We Apply These Rules Where You Live

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

REACHING US

Where To Send A Privacy Request

You can raise any question about this policy through the support desk inside your account, and we reply in the language you write in. Live chat runs from 9am to 2am Pakistan time, email tickets are picked up overnight, and every written privacy request gets a reference number you can track.

Team online

In-account live chat

Open the chat bubble from your account menu and a privacy-trained agent picks up the thread. Keep your account ID handy so we can pull the right record.

Email requests

Write to our data desk with what you need: a copy, a correction or a deletion. We answer within two working days and give you a reference to quote on follow-up.

Clause questions

If a clause reads oddly, ask before you act on it. We explain how the wording applies to your account, your payment rail and your sign-in region in straightforward terms.

WHY YOU CAN CHECK

How We Keep This Page Accountable

We check this page every quarter and again after any change to our payment partners, sign-in flow or storage providers. The clause log at the foot of the page shows each revision...

Named policy owner

One operations lead signs off every revision, so the wording has a single accountable author rather than a summary nobody owns when you write in with a question.

Quarterly wording check

Each quarter we reread every clause against how our payment partners and hosting providers actually handle data, then update anything that has drifted from daily practice.

Dated revision log

Every change carries a date and a one-line reason at the foot of the page, so you can see what moved between the version you read and this one.

Support read-through

Our chat and email agents read the current version before their shift, so the answer you get matches the clause you are asking about instead of a scripted reply.

Plain-English drafting

We write for account holders, not lawyers, and keep defined terms to a minimum. Where a legal phrase is unavoidable, we explain it in the same paragraph.

Local expectations lens

Because most accounts on 777 crazy are opened in Pakistan, each revision is checked against local expectations for record keeping, verification documents and reconciliation timelines.

How This Page Fits Our Other Policies

This privacy policy covers data. Our terms page covers the account agreement, our payments page covers how JazzCash, Easypaisa, SadaPay and Raast transfers are processed, and our cookies...

Policy against terms
The terms page sets the account agreement and fair-use rules; this page describes the personal data that agreement produces and how long we keep each part of it.
Policy against payments
Our payments page explains how to move money with JazzCash, Easypaisa, SadaPay or Raast; this page explains what transaction records we retain and who can view them.
Policy against cookies
The cookies page lists the small files our lobby sets and how you switch them off; this page explains which of those signals become account data on our side.
One shared update date
When one policy changes in a way that touches another, we release both on the same date and cross-link them, so you never read a clause that has been superseded.
One logging standard
The same retention clock runs across all our policy pages, so a verification upload is held for the same period wherever you read about it.
One request route
A privacy request, a transaction dispute and an account question all enter through the same support desk, so you are not chasing three queues for one issue.
One changelog format
Every policy carries the same dated changelog block at the bottom, which means you can compare revisions across pages without learning a new layout each time.

The Layout You'll Find On This Page

This page is built to be skimmed before it is read. A summary strip sits under the heading with the four areas we handle most often...

Summary strip

Four short lines sit under the heading so you can confirm at a glance what this page covers before committing to the full clause list underneath it.

Anchored clause list

Each heading in the left column links straight to its clause, which makes it quick to jump to storage periods, sharing rules or deletion routes on any screen.

Last-updated stamp

A dated stamp under the title shows when we last touched the page, so you can tell whether the version in front of you is the one you read last month.

Language switch

You can read this page in the language you use inside the lobby, and the switch keeps your position in the text so you do not lose your place mid-clause.

Print and save copy

A print view strips the lobby navigation and leaves clean text, which helps if you want a copy for your own records or for someone advising you.

Request block

The support block closes the page with chat, email and account routes together, so you can start a privacy request without navigating back to the lobby first.

Privacy Policy Questions We Hear Often

We store your name, date of birth, contact details, region and the verification documents you upload, plus sign-in times, device type and the references your JazzCash, Easypaisa, SadaPay or Raast transfers generate.

Active data stays while your account is open. After closure we hold the minimum needed for financial reconciliation and legal duties, then delete or anonymise the rest on a fixed schedule.

Only with the providers needed to run your account, such as payment rails, verification partners and hosting. We do not sell personal data, and each partner is bound by a written confidentiality agreement.

Yes. Send a request from your registered email or through the in-account support desk and we compile a copy of your personal data, usually within a few working days of confirming who you are.

Tell support which detail is wrong and attach proof if the change touches verification, such as an updated document. We amend the record, flag the correction and confirm back to you.

We date the new version, log the change at the foot of the page and, where it affects how your data is used, tell you through your account notifications before the change takes effect.