Privacy Policy for probo app Pakistan
Our Privacy Policy explains what account data we collect, why we collect it, and how you can ask us about it before you open an account. It covers...
How we handle your account data
Privacy Policy is where we explain our data posture for probo app, including account creation, login activity, identity checks, payment record matching, device security, and support messages. We only ask for details needed to operate your account, verify access, process requests, keep fraud controls active, and meet legal duties where local law permits. Pakistani payment rails such as JazzCash, Easypaisa, SadaPay and
Raast may create transaction references that we match to your account record; we do not use those references for unrelated profiling. Cookie data helps us keep your session stable, remember language choices, and detect unusual access. You can contact us about access, correction, deletion, or questions about how a privacy choice affects your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact us about privacy choices
Privacy requests need a clear route, so we separate them from general account help. When you contact us, we may ask for enough account detail to confirm that the request belongs to you. We aim to answer in plain Pakistani English and explain any lawful reason if a request cannot be completed exactly as asked.
Privacy email
Send us your account email, the privacy request you want handled, and any transaction reference only if it supports your request. We use the message to verify ownership and reply with clear next steps.
In-account help
When you are logged in, you can raise a privacy question through account help. That route attaches basic account context, so our team can check identity without asking you to repeat sensitive details.
Security concern
If you think your account data was viewed without permission, contact us quickly with the time, device, and any alert you saw. We check access logs and explain what we can confirm.
How we keep this policy current
We write this Privacy Policy from the way probo app actually handles account data. Changes in login flow, payment record matching, cookies, or customer support are reflected here before we rely on...
Policy check rhythm
Our team checks the Privacy Policy when account screens, verification steps, cookies, or payment record fields change. That keeps the wording tied to real data handling rather than generic legal language.
Local wording
We write for Pakistan in clear English, naming JazzCash, Easypaisa, SadaPay and Raast when those records matter. That helps you understand how local transaction references connect to account privacy.
Access control
Privacy requests are handled by trained support and compliance staff only. Internal tools limit which account fields can be seen, and activity is logged when a request requires deeper checking.
Cookie accuracy
Cookie wording is checked against the scripts we actually use for session stability, analytics, and security signals. If a cookie purpose changes, the policy text is updated to match that use.
Payment record clarity
We explain payment data as account matching data, not as public activity. References from local rails are used to reconcile requests, verify withdrawals, and support lawful checks linked to your account.
Change visibility
When the Privacy Policy changes in a meaningful way, we update the page date or provide a clear account message. You can then read what changed before continuing with your account.
How privacy stays aligned across pages
Our Privacy Policy connects with other legal pages, but it stays focused on data handling. If a term page explains account rules, this page explains the data behind...
How the policy is laid out
We structure the Privacy Policy so you can scan key data points without losing the legal meaning. Headings separate collection, use, sharing, security, retention, and your...
Plain headings
Each heading names a privacy action, such as data collected, data used, or data kept. We avoid vague labels so you can move straight to the part that affects your account.
Local chips
Short chips identify Pakistan context, including JazzCash, Easypaisa, SadaPay and Raast references. They are placed near privacy wording so you can see why a local record may be mentioned.
Account moments
Cards describe privacy moments you recognise: account opening, login, identity checks, withdrawals, support messages, and cookie choices. Each card explains what data is involved and why it is used.
Choice markers
Where you can ask for access, correction, deletion, or a privacy explanation, the layout marks that clearly. We also explain when legal duties may limit the exact result.
Security labels
Security labels separate fraud checks, device signals, and account access logs from general account data. That makes it easier to see which records protect access and which support service.
Date placement
The policy date is kept where you can see whether the wording is recent. When a material change happens, the layout helps you compare the new privacy wording with your account choices.