InCab Privacy Policy
Effective date: 7 October 2026
INCAB RIDES PRIVATE LIMITED, CIN U49224PB2025PTC065267 (“InCab”, “we”, “us”), operates the InCab rider app and InCab Driver app. This policy explains how we handle personal data for account access, ride booking, driver operations and support. It also covers related account and support web services. Privacy requests may be sent to support@incabrides.in. Our registered office is H No. 40B, Guru Fateh Town, Daun Majra, Kharar, Rupnagar – 140301, Punjab, India. Privacy and grievance requests are handled by the InCab Support and Grievance Team at support@incabrides.in and our registered office.
1. Information we collect and why
| Information | Source and purpose |
|---|---|
| Phone number, account identifier, name and authentication/session information | Supplied by you or generated during sign-in; used to verify accounts, maintain sessions, contact you and prevent abuse. OTPs are delivered through configured WhatsApp or SMS providers. |
| Google account information when you choose Google sign-in | Google identity identifier and available name/email are used to verify and link the Google identity to your phone account. We do not request your Google password. |
| Pickup, destination, searched/saved places and journey details | Your selections and bookings; used for search, routing, fare guides, matching, journey history and dispute resolution. These addresses can reveal personal routines. |
| Location coordinates and related accuracy/movement information | Device location when you allow it; used for pickup/map assistance and, for online drivers, nearby requests and trip tracking. The driver-location behavior is explained separately below. |
| Driver identity, eligibility and vehicle information | Submitted profile and documents, including licence, identity proof, registration, photographs and insurance where requested; used to assess and maintain driver eligibility. |
| Offers, accepted fares, status events, ratings and platform conduct indicators | Generated through journeys; used to run bookings, resolve disputes and assess service quality and account health. “Driver health” is a platform indicator, not medical information. |
| Wallet and payment records | Amounts, provider order/payment identifiers, transaction status and ledger entries; used to credit driver top-ups, account for commission and reconcile disputes. Razorpay processes payment credentials in its payment flow. |
| Notification and device information | App-generated installation/device identifiers, push tokens, platform/app details and notification settings; used for ride notifications, delivery and security. |
| Support and safety information | Messages, attachments, issue references, SOS events and trusted-contact details you enter; used to respond to requests and operate safety features. Enter another person's details only with their permission. |
| Operational and security logs | Request metadata, network/IP information, timestamps, errors and access events generated by our services; used for availability, abuse prevention, troubleshooting and audit. |
We do not sell personal data. The current app does not include a targeted-advertising feature. Any new advertising, analytics or materially different data use requires an updated disclosure and any necessary consent before it begins.
2. Location and device permissions
InCab rider app: With your permission, device location helps identify pickup and centre the map. You can choose or edit a location manually where supported. Ride pickup/destination coordinates are sent to our service when you search or book. This policy does not describe the rider app as continuously tracking you when it is closed.
InCab Driver: While you deliberately remain online or on an active trip, the app collects and sends location to InCab for nearby ride requests, pickup ETA and trip tracking. A location foreground service can continue while the app is in the background or the screen is off, with an ongoing Android notification. Relevant location is shared with riders as described below. Going offline stops online availability reporting; an active trip may need to be ended through the trip flow. Turning off location permission affects these features. Do not treat closing the screen as going offline.
We require permission for device location. You can manage permissions in device settings; permission-dependent features may be unavailable if you decline. This policy explains location use but does not replace any separate in-app disclosure or consent required for the feature.
Camera/photo selection supports uploading requested driver documents and photographs. Notification permission enables booking and safety alerts. Call buttons open the phone dialler; this feature does not record calls or read call history. Trusted contacts are entered for safety purposes; this is not permission to upload your entire address book. Permissions can be managed in device settings. Some functions cannot operate without their necessary permissions.
3. Who receives information
- Ride participants: Eligible drivers receive journey information needed to consider and fulfil requests. Riders comparing offers may see driver name, approved display photograph, vehicle details, rating, platform-health indicator and estimated pickup distance/time. Assigned participants may receive phone contact details to coordinate the trip and relevant driver location. Contact details must not be used for unrelated purposes.
- Authorized InCab personnel: Staff who need information for verification, operations, support, fraud prevention or safety may access relevant records. Identity documents are not displayed to riders as public profile information.
- Service providers: Hosting/storage providers process service data; Google Maps/Places and any configured search/routing provider process relevant queries and coordinates; Google/Firebase provide sign-in or push delivery; Razorpay processes driver top-ups; WhatsApp/Meta through our OpenWA integration and configured SMS providers such as MSG91 deliver authentication messages. Provider selection may vary by deployment. Their processing may also be governed by their own policies.
- Safety recipients: Trusted contacts or support personnel may receive safety information through the feature you choose. An SOS action does not necessarily notify emergency services or guarantee dispatch.
- Authorities and legal recipients: We may disclose proportionate information when required by applicable law, a valid legal request, or to protect rights and safety in accordance with law.
- Corporate changes: If ownership or operations change, personal data may transfer subject to applicable protections and required notice.
We do not publish private KYC documents, financial credentials or trusted-contact information as public content. Information may be processed outside India where our service providers operate, subject to applicable law and appropriate contractual and security safeguards. We do not represent that every service provider processes all data exclusively in India.
4. Security
We use measures intended to protect data, including authenticated access, restricted document access and encrypted transport for production app/API communication. No system can guarantee complete protection. Keep your phone and credentials secure, and report suspected misuse to support. Never send OTPs, UPI PINs, passwords or full payment-card details in a support message.
5. Retention
We retain data only for the time justified by its purpose and applicable obligations. Account/profile records support an active account; booking, payment and commission records support transactions, accounting and disputes; driver documents support eligibility and required records; security/support records support investigation and issue handling. Specific records may need longer retention for a legal obligation, unresolved claim or documented fraud-prevention need. Retained information must remain access-restricted and must not be reused for unrelated purposes.
Retention is determined by these criteria: account information and saved preferences are needed while an account remains active; driver eligibility documents are needed while the driver is approved and for an applicable verification or legal record requirement; booking and financial records are kept for the applicable accounting, tax, transport or claims period; safety and support records are kept until the case and any associated claim are resolved; operational logs are kept only as necessary for security or diagnosis. Where deletion is requested, records with no continuing justified purpose are deleted or anonymized. Where a legal hold or specific obligation requires retention, we identify the affected categories and duration when responding. Backup copies may remain until their scheduled secure rotation; we explain the applicable expiry when responding to a deletion request and restrict their use to recovery and security.
6. Account deletion and privacy requests
You may contact support@incabrides.in to request deletion of your InCab account and associated personal data. Include the app name and registered phone number so we can identify the account. Do not send an OTP or identity-document attachment unless a justified secure verification step specifically requires it. We will verify that the request is authorized before deleting an account.
Deletion ends account access and removes associated data except records that must be retained for a specific lawful purpose. Those exceptions, retention duration and expected processing time must be explained when handling the request. Logout, suspension and uninstalling the app are not account deletion. Shared historical records may need to retain another person's transaction information while your unnecessary identifying information is removed or anonymized.
You can start a request in either app through Legal & account deletion → Request account deletion → Email deletion request, or visit incabrides.in/delete-account. These options open a support email; you must send the email to submit the request. We aim to complete verified requests within 30 days. If a legal obligation or unresolved matter requires retaining particular records, we explain the exception and expected duration. These request options do not perform immediate automated deletion.
You may also request access, correction or information about use of your data, withdraw relevant consent, and raise a grievance through the privacy contact, as applicable under law. Withdrawal affects future consent-based use and may make a feature unavailable; it does not erase obligations to retain particular records. We may ask for proportionate verification. Statutory complaint rights are not excluded.
7. Children
Accounts are intended for adults aged 18 or older. We do not intend to collect personal data from children operating independent accounts. If you believe a child has created an account, contact us so we can investigate and take appropriate action. Accompanied travel remains subject to safety and legal requirements.
8. Changes and contact
We will update this policy and its effective date when our practices change, and give additional notice or obtain consent where required. Privacy and account-deletion requests: support@incabrides.in. General support: +91 85568 68095.
INCAB RIDES PRIVATE LIMITED · CIN U49224PB2025PTC065267
Registered office: H No. 40B, Guru Fateh Town, Daun Majra, Kharar, Rupnagar – 140301, Punjab, India.
Recognized as a startup by DPIIT, Ministry of Commerce & Industry, Government of India (Certificate No. DIPP216857).
Support hours: 24 hours a day, every day.
Privacy and grievance contact: InCab Support and Grievance Team · support@incabrides.in · the registered office above.
© 2025 InCab Rides Private Limited. All Rights Reserved.