Terms connection
The Terms page explains your account duties, while this Privacy Policy explains the data used to operate those duties, including identity checks, login records and security flags.
LEGAL REFERENCE
Privacy Policy For Your base64 Account
base64 gives you one clear Privacy Policy for account data, verification checks, device signals, support chats and payment-related records used in supported Pakistan regions. Read it before you...
Account data useCookie choicesPakistan contextSecurity records
How We Handle Your Data
This Privacy Policy explains how base64 collects and uses data when you create an account, sign in, pass verification, contact support, set preferences or make transactions where local law permits. We use your details to run account access, protect balances, process requests, detect misuse, meet record duties and answer privacy questions. Payment references may include confirmation data linked with JazzCash, Easypaisa, SadaPay
and Raast, but we do not ask you to place wallet passwords or one-time codes inside support messages. We keep records only for business, security and legal reasons, then remove or anonymise them when retention is no longer needed. If a local rule requires a different handling period, we apply that rule to the relevant record set.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Reach Us About Privacy
Privacy questions deserve a direct route, not a maze of generic replies. We keep separate contact paths for data access, correction requests, account security concerns and consent choices. When you contact us, include your registered phone or email and a short description of the request, but never send wallet passwords, card secrets or one-time codes.
Team online
Privacy email
Use our privacy email for access, correction or deletion requests. We may ask for account confirmation first, because we need to know the request comes from you before changing records.
Live chat handoff
If you start in live chat, our agents can route privacy matters to the correct team. Chat is useful for status checks, but deeper data requests move to email.
Security contact
Tell us quickly if you think account data, login access or payment references were exposed. We check session history, device signals and recent changes before replying.
ACCURACY SIGNALS
How This Policy Stays Accurate
We write this policy from the way our own account, support and risk systems actually work. Each update is checked against the data we collect, the reasons we use it and the...
Operational wording
The policy names real account steps, including sign-in logs, verification records, support messages and transaction references. We avoid vague language where a clear data category explains the purpose better.
Local payment references
Pakistan rails are described as context for record handling, not as extra permissions. JazzCash, Easypaisa, SadaPay and Raast references help explain why transaction records may exist.
Access controls
Internal access is limited by role, so support, payments and security staff only see the data needed for their task. Sensitive changes leave audit records.
Retention checks
We separate short-term session data from records needed for account, security or legal reasons. Deletion timing depends on the record type and applicable duties.
Plain language
We write for clear Pakistani English and avoid legal clutter where simpler wording works. If a term has a specific meaning, the surrounding sentence explains its use.
Change tracking
When we revise this Privacy Policy, the new wording reflects process changes such as added verification steps, cookie changes or different support routing for data requests.
PAGE ALIGNMENT
Privacy Across Our Legal Pages
Our privacy wording connects with the rest of the legal area, so you do not have to guess where a rule sits. Account terms explain acceptable use, cookie wording covers browser storage...
Cookie connection
Cookie wording covers browser storage and similar tools. This page adds why those signals may support session safety, preference memory, analytics and fraud detection.
Support connection
Support pages explain how to reach us. This policy clarifies what data support may use, such as contact details, chat history and account status.
Security connection
Security content focuses on access protection. The Privacy Policy explains the related records, including device signals, login attempts, password reset history and account change logs.
Payments connection
Payment pages describe available rails. This policy explains why transaction references, wallet names, verification outcomes and payout checks may be stored with your account.
Promotions connection
Promotion pages may describe account offers. This policy explains how eligibility data, consent choices and message preferences are handled when you choose to receive updates.
Complaints connection
Complaint handling may require account history and message records. This policy explains how we use those records to investigate, respond and keep an audit trail.
Layout Cues That Clarify Privacy
The policy page is arranged so you can scan important privacy points before reading every clause. Headings separate collection, use, sharing, storage and contact rights. Short...
Section anchors
Each privacy topic has its own anchor, so you can move from collection to retention or contact rights without searching through unrelated account material.
Short chips
Chips call out local context and common data areas, such as account records, cookies and transaction references, without turning legal wording into a long wall.
Readable cards
Cards separate support routes, policy checks and related pages. The format helps you see which privacy action fits your question before contacting us.
Direct wording
We use active sentences that say what base64 collects, why it is used and when it may be shared with service partners or authorities.
Update placement
Policy updates appear near the relevant section rather than being buried elsewhere. This helps you notice changes to data handling, cookies or contact routes.
Mobile reading
The page is built for phone screens, with short paragraphs and clear spacing. You can read privacy points without pinching, zooming or opening another file.
Privacy Policy Questions Answered
We collect details needed to set up and protect your account, such as contact data, login credentials, device signals and verification results. Extra records may appear when you contact support.
We keep transaction references to confirm account activity, process withdrawals, resolve disputes and meet record duties. JazzCash, Easypaisa, SadaPay and Raast records are handled as privacy-covered data.
Yes. Send a privacy request with the account detail you want corrected. We may verify your identity first, then update records where the change is accurate and allowed.
We may share limited data with partners that help operate verification, payments, hosting, analytics, security or support. They receive only what is needed for the assigned task.
We use access controls, session monitoring and audit logs to protect account data. Device and login records help us detect unusual activity and secure your account access.
Use the privacy email or ask live chat to route your request. Include your registered contact detail, but never send wallet passwords or one-time security codes.