Privacy Policy for your auiator account
We explain how auiator collects, uses, stores and protects the data linked to your account, device and transaction history in Pakistan. Before you open your account, this policy...
How we handle your account data
This Privacy Policy applies when you access auiator from supported regions where local law permits, create an account, contact our team or use payment routes connected to your profile. We collect only the data needed to run account access, verify transactions, secure sessions and answer your requests. That may include your name, mobile number, email address, device signals, login records, wallet references
and support chat content. We use this data to operate the account flow, detect unusual access, process lawful requests and keep records required for finance and security checks. We do not sell your personal data. We share limited records only with service providers that help us run hosting, payments, verification, fraud checks, analytics or customer care under access controls.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep this policy accurate
We maintain this Privacy Policy as an operating document, not a generic legal page. Product, support and risk teams check the wording against the way auiator actually handles account records, payment references...
Data mapping
We map account fields to real systems, including registration forms, wallet references, support tools and login security logs, so this policy reflects where your data is actually handled.
Payment record scope
JazzCash, Easypaisa, SadaPay and Raast references are treated as financial records. We keep only what is needed to reconcile transactions, answer disputes and meet record duties.
Access controls
Staff access is limited by role, with sensitive account and payment records available only to teams that need them for support, finance checks or security investigation.
Version control
When we update this Privacy Policy, we keep the current wording aligned with live forms and account screens, so you can compare the page with what you see.
Provider checks
Service providers that process account data for hosting, verification, analytics or support are assessed for purpose, access need and retention before data is shared with them.
Request handling
Privacy requests are logged with time, channel and outcome. This helps us respond consistently while keeping your identity check separate from the content of your request.
Consistency across our legal pages
This Privacy Policy works with our other legal pages, but it has one role: explaining personal data handling. Where another page discusses account rules, promotions or platform access...
Visible privacy cues on this page
We designed this Privacy Policy so you can scan what matters before opening an account or sending a request. The layout separates collection, use, sharing, retention...
Clear section order
The page starts with collection and use, then moves into sharing, retention and contact rights. That order follows how your account data moves through our systems.
Local context
Pakistan payment names appear only where transaction records are relevant. This helps you see when JazzCash, Easypaisa, SadaPay or Raast details become privacy records.
Plain wording
We avoid legal clutter where plain English works. If a term affects your account data, we explain the practical effect and the reason we need that record.
Request focus
Contact routes are placed near the policy detail so you can ask about access, correction or deletion without searching through account or lobby pages.
Retention cues
Where records must be kept for security, finance or dispute handling, we say why. Where retention is not needed, we aim to remove or anonymise data.
Sharing limits
The policy names the types of providers that may receive limited data. We describe their purpose instead of using broad wording that hides processing details.