Faida Driver Privacy Policy

1. The services this policy covers

The current Driver app supports vehicle selection, account creation and sign-in, refundable security-deposit registration, payment-status recovery, profile management, launch information and driver support. Payment or registration does not by itself approve a person or vehicle to provide rides or deliveries.

Verification, bank settlement, incentives and operational ride or delivery features are subject to availability and eligibility. Sections below describing those features apply when you use an enabled feature. Before materially different data collection begins, we will provide the relevant notice and obtain permissions or consent where required.

2. Information you provide

Account and profile information. Your name, mobile number, receipt email, selected city, vehicle category, make, model, manufacturing year if supplied, registration number if supplied, and changes you make to your profile. Sign-in uses your account identifier and password. Our account service stores a salted password hash rather than a readable password, and stores session records to keep your account secure.

Registration and payment records. The deposit and currency, accepted terms and policy versions, registration and order references, payment-provider transaction references, payment status, timestamps, refund or closure requests, receipts, reconciliation records and the limited payment-method details returned by the provider. A payment callback alone is not treated as proof of a captured payment.

Support and privacy requests. Messages you send, associated account or guest-conversation references, selected city, message times, case status, and information you choose to include when requesting help, data access, correction, deletion or a refund. Guest chat can work before signup using a randomly generated conversation identifier; we may link that conversation to your account when you sign in. Do not send passwords, OTPs, UPI PINs, complete card details or unnecessary identity documents in chat.

Verification or payout information, when available. Information and documents you submit for driver, vehicle or bank verification may include licence and vehicle details, insurance, permits, expiry dates, identity evidence, bank-account or payout-destination details, and review results. We collect these through the relevant process when enabled, rather than treating a paid deposit as verification. Do not submit documents that the process has not requested.

Offline pre-registration information. If you register your interest through an authorized offline campaign, we may record the name, mobile number, city and vehicle category provided with permission. We match mobile numbers to avoid duplicate records when you later register online. Public campaign counters show aggregate figures, not individual contact details; company-reported figures are distinguished from verified paid registrations.

3. Technical information and local preferences

Our services process technical information needed to deliver and protect them, such as IP/network information, request and session identifiers, request times, error information and security or administrative audit events. Payment providers may process additional device, transaction and fraud-prevention information under their own notices.

The app keeps preferences such as language, appearance and reduced-motion choices on your device. It also stores session or guest-support identifiers needed to restore access and conversations. Signing out or uninstalling can remove local access, but does not itself delete your server account or financial records.

To offer UPI payment choices, the app checks compatible UPI handlers and displays their names and icons. Faida's local icon bridge does not send a complete inventory of installed device apps to our backend. The selected payment app and PayU can process information needed for the payment under their own policies.

4. Location, notifications and permissions

The current registration journey uses the city you select; it does not start continuous driver-location tracking as part of signup. If active ride, courier or other location-based work becomes available, we will explain its purpose and request the relevant location permission before collecting location for that feature. You can manage permissions in Android Settings. Refusing an optional permission does not remove rights over your existing account or deposit.

Where remote service notifications are enabled and you choose to allow them, device notification tokens and preferences may be processed to deliver registration, verification, support or service updates. Disabling remote notifications does not delete account records. Features that are unavailable are not represented as currently collecting operational location or notification data.

5. How we use information

We use information to create and secure accounts; manage registration, vehicle profiles and eligibility; create and verify payment orders; maintain refundable-deposit, receipt, refund and settlement records; answer support and privacy requests; prevent duplicate accounts, abuse and fraud; operate and troubleshoot the app; communicate relevant service changes; and meet applicable legal and recordkeeping obligations.

If you use an enabled verification, payout or transport feature, we also use the information required to review that application, fulfil the requested service, handle safety or dispute cases, calculate approved entitlements and reconcile the relevant financial records. Advertising or unrelated marketing is not a condition of opening a Driver account. Any optional marketing or materially different analytics collection will be subject to a relevant notice and choice where required.

6. Payments and independent payment providers

PayU currently processes Driver registration payments. We share the information needed for checkout, including the registration/order reference, amount, name and receipt contact information. PayU, your selected bank or UPI app, and the relevant payment networks process payment credentials and authentication within their payment flows.

Faida does not ask you to disclose a UPI PIN in a Faida form, and our backend is not designed to store raw card numbers, CVVs or UPI PINs. We keep the provider references and status evidence needed for receipts, deposit liabilities, refunds, fraud review and reconciliation. A future payment or payout provider will be disclosed when introduced; the presence of an unused SDK is not a statement that all providers are active.

For PayU's own processing, see its PayU Payments Privacy Statement. The bank or UPI application's notice also applies to its own handling of payment information.

7. Who can receive information

Authorized Faida personnel may access information needed for their assigned support, finance, verification, safety, security or privacy role. Access to private records is restricted; ordinary public visitors do not receive driver contact lists, verification documents or private conversations.

We use payment, banking, hosting, network-security, communications and technical service providers as needed to operate the relevant feature. Cloudflare provides network delivery and security for the public API and these policy pages, which are served by FAIDA's backend. Notification, mapping, verification or other processors receive information only where their associated service is enabled and used. These providers may process technical information required to deliver and protect their services.

We may disclose information where reasonably required by applicable law, a valid legal process, fraud or security investigation, or the protection of people and legal rights. If a business reorganization affects the service or its data controller, we will provide any notice required by applicable law. We do not sell driver personal information.

8. Security and processing locations

We use HTTPS for public service connections, salted password hashing, session controls, role-based access and financial audit records. No security measure eliminates every risk. Protect your account credentials and report suspected unauthorized access through the privacy contact or in-app support.

Information is processed on our service infrastructure and by the providers needed for the relevant feature. Provider infrastructure may operate in locations outside your city or India. This policy does not claim that every provider stores all information only in India. Where applicable, we assess and apply the safeguards and restrictions required for those arrangements.

9. Retention

We retain account and registration information while needed to provide the account, administer the deposit or requested service, resolve requests and maintain necessary records. We review deletion requests and remove or de-identify information that is no longer needed, subject to legitimate retention requirements.

Some payment, refund, tax/accounting, fraud, security, consent, dispute, safety or verification-review records may need to be kept for applicable legal obligations, outstanding claims or a documented legal hold. Support messages and offline intake records also require review before erasure where they relate to an unresolved request or required record. We do not promise that closing a screen, uninstalling the app or submitting a request immediately erases every historical record.

When responding to a deletion request, we will explain any information retained, its purpose or legal basis, and the relevant duration or criterion. A refundable-deposit membership period does not override statutory privacy rights. The deposit-refund process and account/data deletion are related but separate requests.

10. Access, correction and choices

You can edit supported profile fields from Driver Portal → My information. To request access, correction or deletion, use Driver settings → Privacy & account rights, or the same privacy-rights option within My information. The app records your request for review; it does not label that action as completed erasure.

You may also contact us outside the app using the email below. We may ask for proportionate information to verify account ownership or understand the request. We will not ask for a password, payment PIN or bank OTP to process a privacy request. Requests involving another person's information, required financial evidence or an active legal hold may require additional review. Applicable rights and statutory timelines continue to apply.

11. Request account and associated-data deletion

You do not need to reinstall the app to request deletion. Email hello@azuriyatech.com with the subject Faida Driver - account deletion request. Include the mobile number or receipt email associated with your Driver account, whether you request account deletion or a specific correction/removal, and a safe way to contact you. Do not include a password, UPI PIN, card number or bank OTP.

If you cannot access the original mobile number or email, explain that in your message so we can arrange an appropriate ownership check. You can also submit Request account deletion from the in-app Privacy & account rights page when signed in.

We will review the request, verify ownership where needed, and communicate the result or any outstanding steps. Removing eligible account data, settling a refundable deposit and retaining records required for legal or dispute purposes are handled separately. We will tell you if a record must be retained and why. An ordinary voluntary membership-closure waiting period is not a requirement to submit a statutory privacy request. Deleting the app alone does not submit a deletion request.

12. Adult drivers

Faida Driver is intended for adults who are legally eligible to register for the applicable driver or carrier category. It is not directed to children. If you believe a child has provided information without appropriate authority, contact us so we can review and handle it.

13. Updates and privacy contact

We may update this policy when the service or its data practices change. The published page will show the effective or updated date. For a material change requiring notice or renewed consent, we will provide the relevant notice or request before applying that change as required.

Privacy contact: Azuriya Technologies Pvt Ltd — Faida Driver · Email: hello@azuriyatech.com · Website: azuriyatech.com