Privacy
Privacy at ApnaTask
How ApnaTask is designed to handle account, task, location, messaging, provider, and support information.
What the product needs
ApnaTask uses account and phone-verification information, customer task details, map-selected locations, private offers and messages, provider service details, and support records to operate the marketplace.
- Provider KYC documents are separated from ordinary business data.
- Analytics must exclude raw addresses, messages, phone numbers, CNIC data, photographs, and search text.
- Payment and credit records are kept as auditable ledger entries when charging is enabled.
Location privacy
Before a customer selects a provider, eligible providers see only a privacy-displaced task location or approximate locality. The selected provider receives the exact task address and customer phone only when required to perform the work.
Use, access, and retention
Information is used to authenticate users, match relevant tasks, moderate abuse, deliver notifications, support transactions, resolve disputes, and meet legal obligations. Access must be limited by role, recorded for sensitive data, and removed when no longer required.
- Raw KYC documents use separate encrypted storage and narrow reviewer access.
- Support or legal holds may delay deletion of specific records.
- Cross-border processing remains subject to legal approval and disclosed service regions.
Your choices
Users can manage consent, report or block another user, request an account export, and request account deletion. Contact support for a privacy request while the in-app controls are being prepared.
- Email: privacy@apnatask.pk
- Do not email CNIC images, completion codes, passwords, or payment credentials.