Privacy Policy for GFC Dost
Last updated: 16 November 2026 | App: GFC Dost | Android package: com.gfcpakistan.gfcdost
GFC Pakistan (referred to as “GFC”, “we”, “our”, or “us”) provides the GFC Dost mobile application for authorized field sales agents, dealers, sales and operations personnel, administrators, Happy Call personnel, and other approved business users. The app supports product QR verification, retail-sale registration, customer warranty workflows, dealer relationships, sales review, incentives, and related GFC operations.
1. Scope and responsible organization
This policy applies to personal data handled through the GFC Dost Android application and its supporting GFC systems for the functions described below. GFC Pakistan is the application publisher. Business records may also be administered in connected GFC inventory, sales, dealer, warranty, and operational platforms. This policy does not replace any separate notice GFC provides for other services.
Customer information may be supplied to GFC Dost by an authorized sales agent or dealer, even when the customer does not personally install the app. Users entering another person's data should inform that person of the relevant processing and only provide information authorized for the transaction.
2. Information we handle
Depending on the feature and role, the following data may be collected, generated, displayed, or processed:
| Category | Examples | Main purpose |
|---|---|---|
| Account & identity details | Full name, mobile number, login/account identifiers, role, registration/application status, password credentials, OTP verification status, device information, acceptance of terms; CNIC for applicable field-agent onboarding. | Registration, identity verification, account approval, authentication, and access control. |
| Dealer & work assignment data | Dealer name/code, province, city, sell-out location entered by the user, territory/area, assigned dealer, transfer requests and approval remarks. | Dealer linkage, operational authorization, sales attribution, transfers, and reporting. |
| Customer & warranty data | Customer name and mobile number; email/address where supplied; purchase or sale date; product, model, unit/QR/unique code; warranty status, registration/reference number, relevant service records. | Product verification, retail-sale validation, warranty registration, customer support, and duplicate/fraud prevention. |
| Sales & review records | Scanned product codes, submission dates, dealer selections, sales evidence notes, review decisions, corrections, reversals, timestamps, and responsible user IDs. | Verify sales, manage approvals, keep reliable transaction history, and investigate discrepancies. |
| Happy Call & contact verification | Contacted person's name/number, call attempt details, date/time, outcome, verification answers, status, and written remarks. | Confirm retail sales, dealer transfers, and service-related interactions. |
| Incentive, wallet & payout records | Incentive amounts, ledger transactions, available balance, cash-out requests, payout status, account-holder name, bank name, account number/IBAN or mobile-wallet number, and payment-proof documents where submitted. | Calculate and administer incentives, payout requests, financial reconciliation, and fraud controls. |
| Technical & security data | Device/app information, operating-system/app version where provided, IP address, session/authentication tokens, access timestamps, request/response and error logs, and security/audit records. | Secure app access, troubleshoot issues, monitor reliability, and prevent unauthorized activity. |
| Messages & support submissions | Questions, feedback, support correspondence, submitted files/evidence, and related contact information. | Respond to inquiries, investigate issues, and keep a support trail. |
Not every category is required of every user. For example, CNIC is relevant to certain agent registrations, while payout details are applicable to authorized users using wallet or cash-out features.
3. How we receive information
- Directly from users: account forms, login, registration, sales entries, dealer selection, payout details, evidence notes, support requests and other submissions.
- From authorized GFC personnel: admin approvals, role/dealer assignment, reviews, corrections, Happy Call verification and transaction reconciliation.
- From product scanning: QR/unique codes scanned by the camera or entered manually, which are checked against GFC product and inventory records.
- Automatically in normal operation: session and security events, device information submitted during registration, and server logs needed to operate and protect the service.
- From connected GFC business systems: dealer master records, inventory/product data, warranty status, retail-sale integration results and incentive records.
4. How we use information
- Register and authenticate users, verify mobile numbers using one-time passwords, approve applications, assign appropriate roles, and manage access.
- Scan and verify GFC product codes, check authenticity/eligibility, and distinguish current inventory from older Pre-Nexus stock where supported.
- Record customer purchases, perform sales review and Happy Call verification, finalize or reverse sales when authorized, and administer warranty registration/status.
- Manage dealer relationships, transfers, territories, incentives, wallet balances, cash-out/payout approvals, and financial audit trails.
- Contact users or customers about account security, sale verification, warranty-related matters, support and necessary business updates.
- Maintain records needed to investigate suspected fraud, disputes, policy breaches, errors and legal or regulatory obligations.
- Provide technical support and improve application stability, security, usability and operational processes.
We aim to use personal information only for legitimate app-related business purposes and subject to applicable law and required notices/permissions.
5. Device access and permissions
Camera and QR scanning
GFC Dost requests camera access to scan product QR codes and verify individual product units. Camera access is requested when needed for scanning and can be refused or changed in Android settings. The scanned product identifier, not a continuous camera feed, is used for the product/sale workflow. If a separate feature permits image or evidence uploads, those files are processed only when selected or submitted by the user.
Internet connectivity
The app connects over the internet to GFC systems for login, product lookup, sales, warranty, dealer verification, incentives and related functionality. Some features cannot operate without connectivity.
Files and images
Where a feature allows an authorized user to attach payout evidence or other documents, the selected file and relevant metadata may be uploaded to GFC systems. Access is limited to the files selected through the relevant Android feature.
Phone, SMS, location and other access
Verification codes may be sent through SMS or other approved communication channels. Providing an OTP does not mean the app needs to read your SMS inbox. Dealer area, city, province or sell-out location may be entered or assigned as operational data; this is different from continuous or background GPS tracking. The core product-scanning workflow does not require contacts, microphone or background location access. If future functionality requires additional sensitive permissions, we will update our disclosures and request any permissions required by the platform.
6. Verification calls and messages
GFC may use phone calls, SMS, email, WhatsApp or other approved channels where enabled and appropriate to confirm account registration, verify product sales, handle warranty inquiries, administer dealer transfers and provide necessary service notifications. Communications providers may receive the telephone number or other details necessary to deliver a message or facilitate a call.
Happy Call workflows may store call attempts, timestamps, outcomes, notes and contact verification details. Such records do not, by themselves, mean telephone audio is being recorded. If audio recording is introduced, GFC will provide any additional notice and consent required by law.
Operational and security messages may be necessary to use the service. Promotional messaging, if introduced, will be handled subject to applicable preferences and consent rules.
8. Data security
GFC applies technical and organizational safeguards appropriate to the data and operational risks, including authenticated access, role-based permissions, controlled administrative functions, encrypted internet connections where configured, and security/audit logging. Supported mobile sessions use secure operating-system-backed storage for authentication tokens. Sensitive access should be limited to authorized personnel.
No method of electronic transmission, storage or security control can guarantee absolute protection. Users should keep passwords and OTPs private, lock their devices, sign out of shared devices and promptly report suspected unauthorized activity.
9. Data retention and deletion
We retain information only for as long as reasonably needed for its stated purpose, the continuing business relationship, product-warranty obligations, transaction reconciliation, security, fraud prevention, dispute resolution and applicable legal, accounting or recordkeeping duties.
- Accounts and profiles: retained while needed to administer the account and role; when a valid deletion request is completed, personal details not otherwise required are deleted or anonymized.
- Sales, warranties, QR traceability and Happy Call history: may need to be retained to preserve proof of a legitimate transaction, warranty eligibility, anti-fraud controls and legally required audit records.
- Incentive, cash-out and financial records: may be retained for payout reconciliation, tax/accounting requirements and dispute handling.
- Security and technical logs: retained for limited operational and security needs and removed or anonymized when no longer necessary.
Where records must legally or operationally be preserved following an account deletion request, GFC limits their use to the necessary purposes and restricts access where practicable. Mere account suspension is not treated as account deletion.
10. Your choices and privacy requests
Subject to applicable laws, legitimate verification and recordkeeping obligations, you may ask GFC to access, correct or update inaccurate information, withdraw consent where processing is based on consent, or request deletion of your app account and applicable personal data. You may change Android camera permissions in device settings, but QR-scanning features will not work without camera permission unless a manual entry method is available.
To protect the requester, GFC may ask for limited proof of account ownership. Never send your password, OTP, or full bank credentials by email. Requests relating to a customer purchase may be verified against the product/transaction reference.
11. How to request GFC Dost account deletion
If you have created a GFC Dost account, you may request deletion of the account and associated personal data through our dedicated public GFC Dost Data & Account Deletion page or by emailing gfc@gfcfan.com with the subject “GFC Dost Account Deletion Request”. Please provide only the minimum account-identifying details needed to locate your account, such as its registered mobile number, and do not email passwords, OTPs or full CNIC images.
GFC will verify the request, remove or anonymize eligible account-linked data, and explain any specific transaction or statutory records that must be retained. If account creation is available within the app, an accessible in-app path to initiate deletion must also be provided.
12. Children's privacy
GFC Dost is designed for authorized business and field-service use and is not directed to children under 13. Children should not independently register for or use business accounts. If we learn that a child's personal data was collected improperly, we will take appropriate steps to delete or otherwise handle it in accordance with applicable obligations.
13. Data storage and international processing
Information is handled in connection with GFC operations in Pakistan. Technical hosting, communications or service providers may process information in other locations depending on the services GFC uses. Where cross-border processing occurs, GFC should apply appropriate contractual, access and security safeguards and comply with applicable legal requirements.
14. Third-party services and links
GFC Dost may depend on third-party technology, including Android/Google Play services, camera/barcode-scanning components, mobile messaging/OTP providers, and infrastructure or payment-related processors. Such providers may handle limited data necessary to deliver the services they supply, subject to their own terms where applicable. GFC will review the data handling of third-party SDKs and align its Google Play Data safety disclosures with the actual released app.
The application may include links to websites not managed by GFC. The privacy practices of those sites are governed by their own policies.
15. Changes to this Privacy Policy
We may update this policy when GFC Dost features, data practices, service providers or applicable requirements change. The current version will be available at this public page with a revised “Last updated” date. Material changes may also be communicated through the app or other suitable channels where necessary.
16. Contact GFC Pakistan
GFC Pakistan — GFC Dost
G.T. Road, Gujrat, Punjab, Pakistan
Privacy and account deletion inquiries:
gfc@gfcfan.com
Official website:
https://gfcfans.com/
Account deletion guidance:
GFC Dost Data & Account Deletion
When contacting us, please describe your request and provide only the information necessary for us to identify the relevant account or transaction.