Privacy Policy
This page explains personal data collection, use, sharing, retention and rights. It is the main place to understand how 663bt handles your account records and support history.
LEGAL REFERENCE
663bt Privacy Policy For Pakistan
663bt sets out how we handle your account data, device signals and support messages when you open your account in supported regions. This policy explains what we collect...
Pakistan privacy termsAccount data useSecurity checksSupport contact paths
How We Handle Your Data
This Privacy Policy applies when you access 663bt, create an account, use account security tools, contact our team, or make transactions where local law permits. We collect the data needed to run your account, verify access, process support requests, maintain security logs, and keep records connected with local payment rails. That can include your name, contact details, device data, login history, transaction
references, KYC material when requested, and messages you send to us. We do not sell your personal data. We share data only with service partners who help us operate account access, risk checks, customer care, technical hosting, and payment handling. Your choices and rights may depend on your location and the rules that apply in supported regions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How Our Policy Is Checked
We keep this policy tied to how 663bt actually works, not generic legal filler. Product, support and payments teams check the wording against account flows, verification steps, security logs and Pakistan payment...
Operational reading
Our account team checks whether each data category matches a real screen or process. If a field is no longer collected, the policy wording is changed rather than left in place.
Payment rail mapping
References to JazzCash, Easypaisa, SadaPay and Raast are mapped to the records we actually need, such as transfer IDs, timestamps and status codes used for account support.
Security log testing
We describe login logs, device signals and session checks because they are used to protect your account from misuse. Access to those logs is restricted inside our support workflow.
KYC data control
When verification material is requested, we handle it separately from general support chat. Retention depends on account status, risk checks, record duties and the rules applying in supported regions.
Plain English edits
We write policy text in clear Pakistani English so you can understand how your data moves. Legal wording is kept where needed, but we avoid hiding key rights in dense paragraphs.
Change tracking
When we change the policy, we update the page date and keep an internal change record. Major privacy changes are flagged through account messaging when that is needed.
PAGE ALIGNMENT
Policy Pages Kept In Step
Your privacy reading should not change from page to page. We keep our privacy wording aligned with cookie terms, account rules, promotions wording and support scripts so you get one clear position.
Cookie Policy
Cookie wording connects to this page by explaining browser storage, analytics tags and session tools. We link those tools back to privacy purposes instead of treating them as a separate issue.
Terms page
Account terms mention verification, security and record duties. We keep those points consistent with this policy so privacy promises and account rules do not conflict.
Promotions page
Promo pages may need eligibility checks and account status data. We keep that wording tied to this policy so you know why certain account details may be checked.
Payments page
Payment text explains transaction references and verification steps. This policy explains the privacy side of those records, including why we keep transfer IDs and support messages.
Support scripts
Our support team uses scripts that match this policy when asking identity questions. Agents are expected to request only what they need to solve the privacy or account issue.
Security messaging
Security alerts and login prompts are written to match the policy. If we ask for extra confirmation, the purpose is account protection and record accuracy.
Visible Privacy Markers Across 663bt
We place privacy cues close to the actions that create data. Account forms, verification screens, support chat and transaction panels explain why a detail is requested...
Account form prompts
Registration fields are limited to details needed to create and protect your account. We avoid asking for unrelated personal data at the first step and explain extra checks when they appear.
Login protection
Login pages collect device and session signals to spot unusual access. These signals are not shown publicly and are used to protect your account from unauthorised entry.
Verification screens
If we request documents, the screen states the purpose and expected format. Files are handled through the account flow rather than open chat whenever that channel is available.
Transaction panels
Payment screens display the rail name and reference field so you can match records later. We use that reference to trace account activity and answer privacy questions.
Chat labels
Support chat reminds you not to share passwords or unnecessary documents. Transcript retention is tied to service quality, dispute handling and privacy request follow-up.
Policy links
Privacy links appear from account and support areas so you can return to the policy during key actions. We keep the wording close to the data moment.
Privacy Questions We Answer Often
We collect account details, contact data, login records, device signals, support messages, transaction references and verification material when needed. The exact data depends on what you do in your account.
We keep payment references to connect a transaction with your account, resolve support cases and check record accuracy. The reference helps us answer privacy questions without asking for unrelated personal details.
Yes, you can ask us what account data we hold. We will verify your identity first, then respond through the account contact route so private records are not sent to another person.
Retention depends on the record type, account status, support needs, security checks and duties in supported regions. We keep data only while there is a valid account, operational or legal reason.
We share data with service partners only when they help operate account access, hosting, security, payment handling or customer support. They receive the data needed for that task, not unrelated account details.
Contact support from your account and tell us which detail needs correction. We may ask for proof before changing sensitive fields, especially mobile numbers, identity records or payment-linked details.