Terms link
The Terms page explains account permissions and restrictions, while this Privacy Policy explains which account data supports those rules. If both pages mention verification, this page covers the data angle only.
LEGAL REFERENCE
Your bettekka Privacy Policy
Your Privacy Policy explains what we collect when you open and use a bettekka account, why we need it, and how we keep it controlled. Read it before...
Pakistan data handlingJazzCash contextAccount privacySupport channels
How we handle your privacy
This Privacy Policy covers bettekka account data, device signals, verification records, support messages, and payment-related references used where local law permits. We collect only what we need to run your account, check access, process requests, detect unusual activity, and answer privacy questions. When you use JazzCash, Easypaisa, SadaPay, or Raast, the payment rail may create its own transaction record; we keep the
bettekka-side reference needed for reconciliation, security checks, and customer care. We do not sell your account data. Access is limited to trained teams and service providers working under data-handling duties. We retain records for operational, legal, and dispute reasons, then remove or reduce them when they are no longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Reach us about privacy
If you have a privacy request, speak to us from the same account details you use with bettekka so we can match the request safely. We may ask for confirming details before sharing, changing, or deleting account data, because privacy help must protect you as well as answer you.
Team online
Account inbox
Send a privacy request from your logged-in account inbox when you can access it. This helps us link your message to your account without asking you to repeat sensitive details in open chat.
Live chat handoff
Use live chat for a quick privacy question, then ask the agent to move the matter to the privacy queue if documents or account changes are involved. Chat is for intake, not public disclosure.
Email route
Email us if you cannot access your account or need a written trail. Include your account email or phone number, the privacy request type, and no payment PINs or full wallet credentials.
POLICY CARE
How our policy earns confidence
We maintain this Privacy Policy as an operating document, not a decorative footer page. The wording is shaped around real account events: joining, login checks, wallet references, support...
Plain language
We write privacy terms in direct Pakistani English so you can see what happens to account, device, support, and payment-reference...
Local context
The policy names JazzCash, Easypaisa, SadaPay, and Raast because those rails create practical privacy moments. We explain our side of...
Access control
Internal access to privacy data is role based. Support, risk, payment, and technical teams see only the records needed for...
Security checks
Login patterns, device markers, failed password attempts, and unusual wallet activity may be checked to protect your account. These checks...
Retention logic
We keep different records for different periods, depending on account operation, dispute handling, payment reconciliation, and legal duties. When a...
Policy upkeep
Our team checks policy wording when account flows, support paths, or payment-reference handling changes. The aim is that this page...
PAGE ALIGNMENT
Aligned privacy across legal pages
This page connects with our other legal pages, but it has its own job: explaining privacy data. Terms pages set account rules, cookie pages explain browser storage, and payment wording explains transaction...
Cookie link
The cookie page deals with browser storage, session tags, and preference tools. This policy connects those signals to account security, analytics, and login continuity without turning cookies into a separate legal subject.
Wallet references
Payment wording may explain how a transaction is submitted or checked. This policy explains the privacy record we keep around that activity, such as wallet reference, status, time, and support history.
Support records
Help pages may tell you how to reach us. This policy explains what happens to messages, attachments, chat logs, and identity checks once you contact bettekka about your account.
Security terms
Security wording may describe blocked access or account checks. The privacy page explains the data used in those checks, including device signals, login attempts, and fraud-prevention markers.
Regional access
Where access is available in supported regions, this policy applies to the bettekka account data we process. If local law changes, our access flow and privacy wording may be adjusted.
Request handling
Other pages may mention account closure or changes. This policy explains the privacy side: verifying your request, keeping required records, removing optional data, and confirming the action safely.
PRIVACY LAYOUT
Policy layout made easy
We arrange this Privacy Policy so you can find the data point that matters before you open or continue using your account. The page separates collection, use, sharing...
Collection blocks
Sections on collection identify the main data groups: account details...
Purpose markers
Each purpose is tied to a practical account task, such...
Sharing labels
Sharing sections separate service providers, payment rails, security tools, and...
Retention cues
Retention wording explains that not all data stays for the...
Choice paths
The request section sets out how you can ask to...
Update signals
When the Privacy Policy changes, we update the page wording...
Questions about your privacy
We collect account details such as name, contact data, login credentials, region signals, device data, and verification records where needed. We also keep support messages and payment references linked to your account activity.
We keep bettekka-side payment references to match wallet activity with your account, answer support questions, manage disputes, and check unusual activity. We do not need your wallet PIN or full private wallet credentials.
Yes. Contact us from your account inbox or email route and tell us what data you want to access. We may verify your identity before sharing records so the request is handled safely.
You can ask us to correct eligible account data if it is outdated or inaccurate. Some changes may require verification, especially if they affect login access, payment references, or account security checks.
We share limited data with service providers, security tools, payment rails, and legal or operational partners only where needed. Each sharing purpose is connected to running, protecting, or supporting your account.
Retention depends on the record type and reason. Support chats, security logs, payment references, and account details may follow different timelines, then be removed or reduced when no valid need remains.
We update this page when our data handling changes. If a change is material, we may highlight it through account messages or site prompts so you can read the new wording before continuing.