Terms page
Our Terms may describe account conduct and access rules, while this Privacy Policy explains the data behind those actions. We keep both pages aligned so privacy wording does not conflict with account rules.
LEGAL REFERENCE
Privacy Policy for your 3r3r account
3r3r keeps your account data, lobby activity, device signals and Pakistan payment context under one Privacy Policy so you can see how your details are handled before you...
Account dataCookie controlsSecurity checksPakistan payment context
How we treat your private data
This Privacy Policy applies when you use 3r3r in supported regions of Pakistan, where local law permits access. We collect only the details needed to create your account, protect sign-in sessions, process account actions, verify payment context, respond to support requests and meet lawful duties. Some data is provided by you, some is created when you browse the lobby, and some comes
from security tools that help us detect unusual access. We do not sell your personal data.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY HELP
Contact routes for privacy requests
If you need to ask about your data, correction, access, deletion or account privacy settings, use the contact path that matches your request. We may ask you to confirm account ownership before sharing personal data or changing privacy settings. This protects your account from unauthorised requests and keeps payment-related records tied to the correct profile.
Team online
Privacy email
Send privacy requests to [email protected] with your account email or phone number. We check the sender, match the account, and reply with the next step before releasing any personal data.
Live chat privacy queue
Use chat inside your account when you want faster identity checks. Our team can confirm the request type, collect missing details, and move privacy matters to the correct queue without asking for passwords.
Account message centre
For sensitive answers, we may send a reply through your account message centre. This keeps data access replies behind your sign-in controls instead of placing private details in open email threads.
POLICY CHECKS
Privacy checks behind our wording
We write this policy from the way our own account flow works, not as a generic template. The wording is checked against sign-in screens, cookie banners, customer support tools, transaction logs and...
Account creation mapping
We map every account field to a purpose, such as sign-in, verification or support. Fields that are not needed for those purposes should not be requested in the account flow.
Cookie category checks
Cookie wording is matched to the actual categories we use, including session, security and preference cookies. We avoid vague labels so you can understand what each browser signal supports.
Payment record handling
JazzCash, Easypaisa, SadaPay and Raast references are used for transaction context only. We record what is needed to reconcile account actions and keep finance records accurate.
Access control logging
Admin access to private data is logged and limited by role. Support staff see only the account details needed to answer your request or handle a verified issue.
Retention checks
We keep data for account service, dispute handling, safety checks and lawful record duties. When a record is no longer needed, we remove it or reduce it where practical.
Policy change tracking
When this Privacy Policy changes, we adjust the date and wording so you can see what has been updated. Material changes may also be flagged inside your account area.
PAGE ALIGNMENT
How this policy stays consistent
Your privacy rights connect with several other 3r3r pages, so we keep the wording aligned across them. This page explains personal data handling, while related pages explain account rules, cookie choices and...
Cookie page
The cookie page explains browser storage in more detail, while this policy states why cookies matter for privacy. Both pages use the same category names to reduce confusion.
Security page
Security wording covers sign-in protection and account safeguards. This Privacy Policy explains what personal data those safeguards may create, such as device records, access logs and verification outcomes.
Promotion rules
Promotion rules may require eligibility checks. This Privacy Policy explains how related account data is collected, used and retained when you choose to check offers shown inside your account.
Payment help
Payment help explains transaction steps for Pakistan rails. This policy explains how transaction references, status records and account matching details are handled as personal or account-linked data.
Support terms
Support terms explain response handling and conduct standards. This Privacy Policy explains how chat transcripts, email records and identity checks are used to answer your privacy or account requests.
App notices
App notices may mention device permissions and push settings. This policy explains how related device identifiers, preference choices and session records are used by 3r3r.
LAYOUT MARKERS
Policy layout built for quick reading
The Privacy Policy is arranged so you can scan the parts that matter before you create or continue using your account. We keep key privacy themes visible: data...
Clear section labels
Each privacy subject is labelled in plain language, so you...
Account-first examples
Examples use real 3r3r account moments, such as sign-in, support...
Pakistan wording
We reference Pakistan support context and local payment rails only...
Choice prompts
Where you have privacy choices, the page points to the...
Retention cues
Retention wording explains why some records stay longer than others...
Update date area
The policy layout reserves space for update timing, so you...
Questions about your privacy at 3r3r
We collect account details you provide, session data from your device, cookie signals, support messages, verification outcomes and transaction references. Each category must connect to account service, safety, support or lawful record needs.
We keep JazzCash, Easypaisa, SadaPay and Raast references to match transactions with your account, resolve payment queries and maintain accurate records. We do not use these references as a reason to sell your data.
Yes. Contact [email protected] or use your account support channel. We will verify your identity, confirm the scope of the request, and provide data that can be shared under applicable rules.
Cookies help keep you signed in, remember preferences, protect sessions and understand site performance. Some cookies are necessary for account security, while optional browser choices can be managed through available settings.
Only authorised staff and service partners can access private details when they need them for support, security, account operation or legal duties. Access is role-based, logged and limited to the relevant task.
Send a request from your account email or use chat after signing in. We may retain some records where needed for disputes, safety checks or lawful duties, but we will explain the outcome.
We update the wording and date when privacy handling changes. If a change materially affects how your data is used or choices are handled, we may also alert you inside your account.