Privacy Policy

Brand Ownership

Pdrs is property of Seekaa Communications Private Limited.

Information We Collect

We may collect name, email, mobile number, business details, GST details, login records, device identifiers, IP address, user agent, app version, push notification token and permission state, one-time signup location if the user allows location permission, selected contact, selected SIM phone number, or phone number details entered for login, signup, recharge, and bill payment, transaction details, wallet ledger entries, API request logs, and support communication.

Location Data

Location permission is optional and is requested only during account signup for security, fraud prevention, and account audit purposes. If allowed, we store the signup latitude, longitude, approximate accuracy, and capture time. PDRS does not collect background location and does not track live movement after signup.

Contacts and Phone Number Helpers

The Android app may let users select a single phone number from the device contact picker or choose from active SIM cards on the device to fill login, signup, recharge, or bill payment forms. PDRS does not request full contact-book access, does not upload the contact list, and receives only the phone number the user selects or confirms.

Phone and SIM Permissions

For SIM selection, PDRS may request Android phone permissions such as READ_PHONE_STATE and READ_PHONE_NUMBERS. These permissions are used only after the user taps the mobile number field and chooses to continue, so the app can show available SIM slots, carrier labels, and SIM phone numbers when the device or carrier exposes them. SIM slot and carrier details are used locally to display the picker. PDRS does not access call history, does not make calls, does not monitor phone activity, and does not upload SIM details unless the user selects or confirms a phone number in a form. Users can decline the permission and type the number manually.

SMS OTP Auto-Fill

During SMS OTP login, signup, or mobile verification, the Android app may use Google Play services SMS User Consent to ask the user for permission to read one incoming OTP SMS message. If the user allows it, the app receives that single SMS message, extracts the 6-digit OTP, fills the OTP field, and submits or verifies only the OTP code as needed for account security. PDRS does not request full SMS inbox access, does not read other SMS messages, does not store the full SMS message body, and users can decline the prompt and enter the OTP manually.

Push Notifications and Device Data

For transaction, wallet, account, security, and service updates, the app may register a Firebase Cloud Messaging token together with platform, app version, notification permission state, user agent, and an Android device identifier. This information is used to deliver notifications, maintain login reliability, prevent fraud, and support account security.

App Lock and Biometrics

If a user enables App Lock, the Android app uses the device biometric or screen-lock authentication system on the device. PDRS does not receive, collect, store, or transmit fingerprint, face, PIN, pattern, or biometric template data.

How We Use Information

Information is used to create accounts, verify users, process payments, send and verify OTPs, deliver notifications, maintain wallet and transaction records, prevent fraud, review referral and signup activity, provide support, comply with law, and improve platform reliability.

Sharing of Information

Transaction and service data may be shared with payment gateways, banks, UPI apps chosen by the user, operators, billers, API providers, Firebase or notification service providers, SMS/email providers, regulators, or law enforcement where needed to process services or meet legal obligations.

Security

We use access controls, OTP verification, IP restrictions for API users, audit logs, and reasonable technical safeguards. No system can be guaranteed completely secure, so users must also protect their credentials.

Data Retention

Records may be retained as required for accounting, dispute handling, audits, compliance, fraud prevention, and legal obligations.

Account and Data Deletion

Users can request account deletion from https://pdrs.in/account-deletion or by emailing support@pdrs.in. Eligible account data will be deleted or anonymized after verification, except records that must be retained for accounting, dispute handling, fraud prevention, security, or legal compliance.

User Requests

Users may contact support to request correction of account information or raise privacy-related concerns, subject to legal and operational recordkeeping requirements.