LEGAL REFERENCE

How We Handle Your Personal Data

This Privacy Policy explains how s55 amg collects, uses, stores and protects personal data when you open an account or contact us from Pakistan. We keep the policy...

Clear data purposesPakistan account contextSecurity-led handlingContact choices
Explore The Lobby Read FAQ
s55 amg How We Handle Your Personal Data

Our Privacy Position For Pakistan

We collect details you provide when creating or maintaining an account, such as your name, contact details, date of birth, address, login credentials and verification records. We also receive technical data including IP address, browser type, device identifiers, language settings, session times and pages opened. Transaction records may show a selected Pakistani rail, including JazzCash, Easypaisa, SadaPay, Raast or NayaPay, together with

status and reference details supplied by the relevant service. We use this material to provide account access, confirm identity, process requests, detect misuse, answer support messages, maintain security and meet applicable legal duties where local law permits. Access is limited to personnel and service partners who need it for these purposes. We retain records for a period suited to the purpose, legal

duties and dispute handling, then remove or de-identify them when practical.

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

PRIVACY CONTACTS

Reach Our Data Support Team

Questions about your personal data can be raised through the account support channel or the contact route displayed on s55 amg. Tell us which account detail or request you are asking about, and we may ask for reasonable proof that you control the account. We use those checks to avoid disclosing private records to the wrong person.

Team online

Account chat

Use the signed-in support chat for access, correction or deletion requests. We can connect your message with the right account record while limiting unnecessary details in the conversation.

Email request

Send a privacy question through the listed support email when you need a written response. Include your registered contact detail and a short description so we can locate the relevant record.

Verification help

If an identity check affects your request, our team will explain the next step without asking for sensitive credentials in chat. Never send a password, one-time code or full card number.

DATA SAFEGUARDS

Controls Behind This Policy

Our privacy approach follows the actual points where account data moves: registration, sign-in, identity checks, local transaction confirmation, device sessions and support handling. We separate operational access from ordinary account viewing, apply...

Purpose control

We connect each data field to a practical reason, such as account access, identity confirmation, security monitoring, support handling or legal record keeping. We avoid collecting extra details without a stated need.

Access control

Account records are available only to authorised personnel and service partners whose work requires them. Permissions are managed around job needs rather than giving every team the same visibility.

Session signals

IP, browser, device and session signals help us recognise unusual access patterns, protect sign-in activity and investigate account concerns. These signals are assessed alongside account events, not as a standalone identity decision.

Identity checks

When verification is needed, we compare submitted details with the request and retain a decision record. We do not ask you to share passwords or one-time access codes as proof of identity.

Transaction records

For JazzCash, Easypaisa, SadaPay, Raast or NayaPay activity, we retain confirmation details needed to reconcile an account request. Full credentials belonging to those services are not requested by us.

Policy changes

If our data practices change, we will update this page and show the revised date or notice where appropriate. The current wording explains the handling that applies to your ongoing account relationship.

What You Can Ask Us To Do

Privacy requests differ from ordinary account support because they concern the records we hold and the way we use them. Depending on the request, we may need to...

Access
Ask what personal data we hold about your account and how it is used. We may provide a structured summary after confirming that the request comes from the account holder.
Correction
Tell us when a contact detail or account record is inaccurate. We can update suitable fields, while some verified records may require an explanation before any change.
Deletion
You may ask us to remove personal data where retention is not needed. Certain records can remain temporarily when required for security, disputes, accounting or legal duties.
Restriction
You can ask us to pause a particular use of your data while a concern is checked. Account access may be affected if the paused activity is essential to security.
Objection
If you object to a stated use, contact support with the reason. We will assess the request against account operation, security needs and any applicable requirement.
Portability
Where technically practical and legally applicable, we can discuss providing certain account details in a usable format. This does not include confidential security controls or another person's data.
Withdrawal
You may withdraw a permission where processing relies on it. Withdrawal does not undo processing already completed and may limit features that depend on the relevant permission.
PAGE HIGHLIGHTS

Privacy Details Made Easy To Scan

We designed this policy page so you can find the parts that matter during an account decision without searching through unrelated service copy. The opening sets the scope...

Plain opening The first section states what this page covers, including account...
Local context Pakistani rails appear only where transaction records affect privacy. JazzCash...
Practical contacts Support routes are separated by purpose so an access request...
Security wording The safeguards section describes access controls, session signals and identity...
Choice summary Access, correction, deletion, restriction, objection, portability and withdrawal are presented...
Current page Changes to our privacy practice are reflected on this page...

Privacy Questions Answered Clearly

We may collect registration details, contact records, verification material, login events, device signals, support messages and transaction references. The exact fields depend on the account action you take and the checks required.

Identity details help us create and protect an account, investigate unusual access, answer requests from the correct person and meet applicable duties where local law permits. We request only what the step requires.

No. We may receive a transaction status, reference or account-related confirmation from the selected rail, but you should not send us a JazzCash, Easypaisa, SadaPay, Raast or NayaPay password.

Yes. Contact support through the listed route and describe the records you want to access. We will confirm account control first, then respond with the data or explanation permitted by applicable rules.

Retention depends on the record, its purpose, security needs, dispute handling and legal duties. When continued retention is no longer needed, we aim to delete or de-identify the material where practical.

You can ask us to correct inaccurate contact or account details. Some verification records cannot be edited directly because they document a completed check, but support can explain the available route.

We will update the wording on this page and may display a notice when a change materially affects your account relationship. The updated text applies from the stated effective point, subject to local law.