Privacy Policy for your zeus23 account
zeus23 keeps your account data, device signals and payment records under one Privacy Policy so you can see what we collect before you open an account. This page...
How our Privacy Policy works
Our Privacy Policy applies when you create a zeus23 account, sign in, contact us, upload verification material or make payment requests where local law permits. We collect only the data needed to run account access, protect sessions, process wallet records and answer privacy requests. Your name, mobile number, payment reference, device type, login time and support messages may be used to match
your account and reduce misuse. We do not sell your personal data. We share limited records with payment processors, verification partners and technical service teams only when they need them to handle your request. Retention periods are tied to account safety, legal duties and dispute handling, then records are removed or anonymised when they are no longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy contact paths for you
You can contact us about this Privacy Policy without sending public messages or repeating sensitive details in several places. We route privacy requests to the team that can check account ownership, locate the relevant record and reply with the next step.
Privacy email
Email us from the address linked to your zeus23 account and include your account name plus the privacy request type. Do not attach card images unless we ask through a secure reply.
Live chat handoff
If you start in chat, our support team can move a privacy request to email after confirming your account. This keeps identity checks, file sharing and final replies in one safer thread.
Account request form
For correction, access or deletion requests, use the form inside your account area. It pre-fills the account reference, helping us match your request without asking for extra personal details.
How we keep this policy accurate
A Privacy Policy is useful only when it reflects how the site really operates. We keep this page tied to account flows, payment record handling, verification checks and support practice, then update...
Local record mapping
We map Pakistan payment references from JazzCash, Easypaisa, SadaPay and Raast to account activity, then describe that mapping here so you understand why those records may appear in privacy requests.
Access controls
Internal access to account data is permission based. Support can see what is needed for your case, while deeper payment or verification records require a narrower role and logged access.
Policy change log
When this Privacy Policy changes in a material way, we update the date and adjust the relevant section rather than hiding the change in broad wording that does not match practice.
Verification handling
Identity documents and account screenshots are handled for verification, dispute checks and account protection. We avoid collecting extra files when a lower-risk account check can answer the privacy request.
Session security
Login time, device signals and IP region can help us spot unusual account access. The Privacy Policy explains this use so you know why security records may be retained.
Support audit trail
Privacy replies are linked to support records so we can show what was requested, who handled it and what answer was given. That trail helps avoid repeated identity checks.
Privacy consistency across our policy pages
Our legal pages should not speak in different voices about the same account record. We align this Privacy Policy with related pages so your rights, our data use...
Visible privacy cues on zeus23
This Privacy Policy is supported by visible cues across zeus23, not only by text on this page. You will see privacy signals near account forms, verification uploads, support...