LEGAL REFERENCE

Privacy Policy For Your 11icads Account

This Privacy Policy explains how 11icads collects, uses, stores and protects details connected with your account in Pakistan. We keep the wording practical, so you can understand what...

Clear data purposesPakistan account contextContact routes includedChoice-led controls
Explore the Lobby Read FAQ
11icads Privacy Policy For Your 11icads Account

How We Handle Personal Details

We collect details you provide when creating an account, completing account checks, contacting us or changing your preferences. We may also receive technical details such as device type, browser signals, login time, approximate location and security events needed to protect access. Transaction records can include the selected rail, reference number, amount, status and related account identifiers for JazzCash, Easypaisa, SadaPay or Raast.

We use this material to provide account access, process supported requests, detect misuse, answer enquiries, meet applicable legal duties and improve page performance. We keep records only for as long as needed for these purposes or for a lawful retention period. Where local law permits, you may ask about access, correction or deletion, subject to identity checks and limits that apply to

financial or security records.

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

PRIVACY HELP

Contact Us About Your Data

Questions about this policy should receive a clear answer rather than a generic reply. Tell us which account detail, device event or...

Privacy enquiries Use the support channel linked from your 11icads...
Access assistance If you cannot reach your account, contact support...
Transaction questions For a JazzCash, Easypaisa, SadaPay or Raast record...
SECURITY PRACTICE

Controls Behind This Policy

Privacy depends on daily handling, not only on wording. Our account flow separates sign-in details from support conversations, records security events for account protection and limits access to operational records according to...

Account checks

When a request concerns your account, we may compare registered details, recent activity and a verification step. This helps prevent private records being released to the wrong person.

Payment references

Our payment records can show a rail, reference and status without asking you to disclose a JazzCash, Easypaisa, SadaPay or Raast secret code.

Device signals

Browser, device and session signals help us identify unusual access patterns, keep sessions safer and investigate account events without treating every device detail as an account message.

Support handling

Support conversations may be retained so we can resolve an issue, track a request and prevent repeated account harm. Sensitive credentials should never be placed in chat.

Retention decisions

We retain records according to their purpose, operational need and applicable legal duties. When a record is no longer needed, handling follows our internal retention process.

Policy changes

If this policy changes materially, the page will show a refreshed version. Checking the date and wording here helps you understand the terms applying to continued account access.

What This Policy Covers

This page is designed to sit alongside account terms and other brand policies without changing their purpose. Privacy questions belong here: collection, use, storage, sharing, security and your...

Collection
This policy explains the account, contact, technical and transaction details that may be gathered when you use 11icads services in supported regions.
Purpose
We connect each data category to a practical reason, such as access, security, support, transaction matching, legal duties or service maintenance.
Sharing
Limited sharing may support hosting, security, payment processing or legal requests. Partners should receive only material relevant to their assigned task.
Your choices
You can ask about access, correction or deletion where applicable. Some records may remain when security, dispute or legal requirements require retention.
Account terms
Account conditions concern how access operates; this page focuses on personal details. These subjects work together but should not be treated as the same policy.
Payment records
A payment rail can create its own records and processing rules. Our policy explains the 11icads records connected with a supported request.
Policy date
The current page wording is the reference point for privacy handling. Revisit it after a material change or when preparing a data request.
PAGE FEATURES

Privacy Details At A Glance

The privacy layout is arranged to help you find a useful answer quickly. The opening panel states the purpose, the legal notice sets the scope, and the support...

Plain opening The first panel states why this page exists and identifies...
Scope panel The central notice brings collection, use, retention and local access...
Direct support Contact cards point you towards practical routes for account access...
Security signals The security section describes checks, device signals and payment references...
Policy links Comparison points separate privacy handling from account conditions and payment-rail...
Question cards Common questions cover deletion, cookies, support records, payment references and...

Privacy Questions Answered Clearly

We may collect registration details, contact details, account activity, device and session signals, support messages, security events and transaction references connected with supported account activity.

References help us match a request, confirm status, investigate disputes and maintain an auditable account record. They do not require you to send a wallet PIN or one-time code.

Where local law permits, you can contact support to ask what personal details are held about your account. We may verify your identity before releasing protected material.

You may ask us to correct inaccurate details or consider deletion where applicable. Security, dispute, transaction or legal duties may require certain records to remain.

Yes, limited device, browser and session signals can help protect sign-in, identify unusual activity, maintain page performance and connect a support request with the correct account.

Use the support route available within your 11icads account and describe the request briefly. Do not include passwords, PINs, one-time codes or complete payment credentials.

A changed version will be published on this page with refreshed wording. We encourage you to check the page when a material change affects collection, use, retention or your available choices.