How aq3d Handles Your Privacy
Before you open your account, this Privacy Policy explains what aq3d collects, why we need it, and how we protect it. You can check the data rules first...
Our Privacy Posture In Pakistan
This notice explains how aq3d handles personal data when you create an account, verify access, contact our team, or use local payment rails in supported regions of Pakistan. We collect only the details needed to run your account flow, confirm transaction records, protect sessions, and answer privacy requests. Payment names such as JazzCash, Easypaisa, SadaPay, NayaPay, and Raast may appear in records
so we can match your request with the right account event. Where local law permits access, we also use device and cookie data to keep sign-in checks consistent and to detect unusual activity. We do not sell your personal data, and we keep retention periods tied to legal, security, and account needs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep Policy Text Accurate
Our privacy wording is maintained by people who work with account access, payments, support, and security logs every day. Each check connects the wording on this page with what our systems actually...
Account-flow checks
We compare the policy against real account screens, including name fields, phone verification, password reset steps, and session prompts. If a field changes, the privacy wording is updated before the page is republished.
Payment record mapping
JazzCash, Easypaisa, SadaPay, NayaPay, and Raast records are mapped to the data fields we store. This keeps our wording clear about references, receipt checks, and support evidence.
Cookie control checks
Cookie purposes are checked against site behaviour, including sign-in memory, language choice, session security, and fraud signals. We avoid vague labels so you can understand why each category exists.
Support script checks
Support replies are checked against this policy so our agents do not request data that the privacy process does not need. Sensitive images are limited to cases where proof is required.
Retention clock checks
We connect retention wording to account, payment, and security timelines. Records are kept only while they serve legal, dispute, fraud, or account purposes, then removed or anonymised through scheduled processes.
Access control checks
Only trained aq3d staff with a work need can see restricted privacy records. Permission levels are checked regularly, and unusual access patterns are flagged for internal security action.
Consistency Across Our Legal Pages
Your privacy rights should not feel different when you move between legal pages on aq3d. We keep this page aligned with our cookie, account, and terms pages so...
Privacy Cues Across The Page
We design the privacy page so you can scan legal text without losing the details that matter. The layout points you towards data categories, choices, contact...
Plain section labels
Each privacy area uses a short label and a direct heading, so you can move from collection to storage, sharing, retention, and rights without sorting through generic platform copy.
Local context chips
Small chips show Pakistan payment names only when they help explain data handling. They are not offers; they simply point to the rail records linked with privacy requests.
Rights prompts
Where a privacy action is available, the layout separates the request from general support. This helps you ask for access, correction, deletion, or restriction without sending unrelated account messages.
Cookie clarity blocks
Cookie wording is grouped by purpose rather than technical vendor jargon. You can see which files help sign-in, security, preference memory, or analytics before deciding your browser settings.
Security callouts
Short security callouts explain why verification may be needed before data is shared or changed. They protect your account from someone using a copied phone number or partial payment receipt.
Date and change markers
When we edit the policy, visible change markers help you spot the section affected. We keep the wording direct so you can understand the effect on your personal data.