This policy explains how Gulberg Digitalization handles information when you use the Gulberg Digitalization mobile application. It reflects the features and integrations present in the application as of the date above.
1. Introduction
Gulberg Digitalization ("we," "us," or "our") provides the Gulberg Digitalization application to support resident registration and authentication, complaints and alerts, property-related services, bills, wallet features, payments, promotions, and administrative status tracking.
By using the application, you acknowledge the practices described in this Privacy Policy. Some features require certain information or device permissions to work; where the operating system provides a permission prompt, you may choose whether to grant it.
2. Information We Collect
Account and identity information
Depending on the feature used, we may collect your name, mobile number, Computerized National Identity Card (CNIC) number, user or member identifier, username, password, one-time password (OTP), application PIN, and authentication tokens.
Property, complaint, and safety information
We may process property or inventory identifiers, plot details, complaint category and department, complaint descriptions, complaint dates, complaint history and status, alert category, and information you submit with a complaint or alert. The app can let you select images from your photo library for complaint-related use.
Location information
When you use location-based complaint, alert, map, or payment/QR features and grant permission, we may process precise or approximate coordinates and a formatted address. Search text and coordinates may be sent to Google Maps Platform services to display maps, search for places, or obtain an address.
Wallet, billing, and transaction information
When you use wallet or payment features, we may process your email address, CNIC issuance date, mobile network, wallet PIN, payment OTP, bill and transaction identifiers, reference numbers, payment amounts, credits, wallet balance information, bill history, and payment status. Payments are facilitated through the integrated payment providers described below.
Technical and locally stored information
The application uses internet connectivity checks and may process ordinary network information such as request metadata, service responses, connection status, and error details. Login state or credentials may be stored in SharedPreferences, while access and refresh tokens are stored using the device's secure storage facilities. Biometric matching is performed by the device operating system; the app does not receive or store your fingerprint or facial biometric template.
3. How We Use Information
- Register, verify, authenticate, and secure user and administrator accounts.
- Provide resident, property, complaint, alert, promotion, dashboard, and status-tracking functions.
- Display maps, locate or search for places, and associate a location with a complaint, alert, QR request, or supported transaction.
- Open, link, manage, or unlink a supported wallet and facilitate bill inquiries, bill payments, payment verification, and transaction history.
- Maintain authenticated sessions, refresh access tokens, check connectivity, and deliver real-time application updates through a WebSocket connection.
- Generate and, at your request, save QR-code or receipt images to your device's photo library.
- Prevent misuse, troubleshoot errors, maintain security, comply with legal obligations, and enforce applicable terms.
4. Advertising
The application does not include an advertising SDK and does not display third-party targeted advertisements based on the project configuration reviewed for this policy.
5. Google AdMob Disclosure
Google Mobile Ads / AdMob is not integrated into the application. Accordingly, the application does not use AdMob to collect advertising identifiers, personalize ads, or measure ad performance.
6. Firebase Services
No Firebase SDK or Firebase configuration was found in the application. In particular, the application does not integrate Firebase Analytics, Firebase Crashlytics, Firebase Cloud Messaging, or Firebase Remote Config.
7. Analytics
No third-party analytics SDK was found in the application, and Firebase Analytics is not used. Operational network logs and error information may still be processed by us or our application backend as necessary to provide, secure, and troubleshoot the service; these are not used by an in-app analytics SDK.
8. Third-party Services
Information is shared only as needed to provide the feature you request, operate the service, or meet legal and security obligations. Relevant service providers may process information under their own terms and privacy policies.
The application does not contain RevenueCat or an in-app purchase SDK. Payments described here concern service bills and wallet/payment-provider functions, not Apple App Store or Google Play digital in-app purchases.
9. Permissions Used
The platform configurations declare only the sensitive capabilities listed below. Availability and permission wording vary by operating system and app version.
No contacts or notification permission is declared in the reviewed Android or iOS application configuration.
10. Children's Privacy
The application is intended for residents, account holders, and authorized administrators and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided information through the application, contact us so we can review and, where appropriate, delete it.
11. Data Retention
We retain information for as long as reasonably necessary to provide and secure the application, maintain account, complaint, bill, wallet, and transaction records, resolve disputes, and comply with legal, regulatory, accounting, and fraud-prevention requirements. Retention periods vary with the type of record and applicable obligations.
Authentication tokens and local login state remain on your device until they expire, are replaced, you sign out, application data is cleared, or the app is removed, subject to operating-system behavior. Images saved to your photo library remain there until you delete them.
12. Security
We use reasonable administrative, technical, and organizational safeguards appropriate to the information processed. The application uses secure device storage for authentication tokens and supports operating-system biometric authentication. However, no electronic transmission or storage method is completely secure, and we cannot guarantee absolute security.
13. Your Rights
Subject to applicable law, you may have the right to request access to, correction of, or deletion of your personal information; object to or restrict certain processing; withdraw consent where processing relies on consent; and lodge a complaint with a competent authority. Some records may need to be retained for legal, security, payment, or recordkeeping reasons.
You can manage location, camera, photo-library, microphone, and biometric permissions in your device settings. Revoking a permission may prevent the corresponding feature from functioning. To exercise a data right, use the contact method below. We may need to verify your identity before completing a request.
14. Changes to this Privacy Policy
We may update this Privacy Policy when the application, our practices, or applicable requirements change. We will post the revised policy with a new "Last Updated" date. Material changes may also be communicated through the application or another appropriate channel.
15. Contact Information
If you have questions, concerns, or a privacy-rights request, contact Gulberg Digitalization through the official support or contact channel provided in the Gulberg Digitalization application or on Gulberg Digitalization's official website. Please include enough detail for us to understand and respond to your request, but do not send passwords, OTPs, wallet PINs, or other authentication secrets.