This policy applies to the app and the privacy page published at `/privacy`.
Privacy Policy — UrbanCarriers
This Privacy Policy explains how the UrbanCarriers mobile app collects, uses, stores, and shares personal data. UrbanCarriers is operated by Speedloop Auto Private Limited, Pune, India. The app supports shippers, drivers, and fleet aggregators on a shared EV cargo delivery platform.
Overview
UrbanCarriers collects data so the app can create accounts, verify users, complete bookings, track active deliveries, settle payments and payouts, and support safety and dispute handling.
This policy is written in plain English. It is designed to cover what the app actually collects, including data that must be disclosed for Google Play Data Safety and Indian privacy compliance.
What we collect
Some data is collected from all users. Other data depends on whether you sign up as a shipper, driver, or fleet aggregator.
| Data type | Collected from | Why we collect it | Legal basis | Shared with |
|---|---|---|---|---|
| Phone number | All users | OTP login and account access through Supabase Auth with Twilio SMS delivery. | Consent and service delivery. | Supabase and Twilio. |
| Full name | All users | Onboarding, account profile, support, and booking identity. | Consent and service delivery. | Stored in Supabase; shared internally as needed for operations. |
| Profile photo | All users who upload one | Profile display and account identification. | Consent. | Stored in Supabase avatars bucket. |
| User role | All users | To set up the right app experience for shipper, driver, or fleet aggregator accounts. | Service delivery. | Stored in Supabase. |
| Email address | Shippers | Optional profile use and PayU payment flow. | Consent and transaction processing. | May be shared with PayU for payments. |
| Business name and GST number | Shippers | Optional business profile details, invoicing, and records where applicable. | Consent and lawful business purpose. | Stored in Supabase; may be used in invoicing or payment records. |
| Booking details | Shippers | Pickup and drop addresses, cargo details, distance, price, and booking fulfilment. | Service delivery and legitimate operational need. | Relevant drivers, fleet partners, support teams, Supabase, and maps services. |
| Payment transaction ID | Shippers | Payment reconciliation, support, refunds, and records. | Transaction processing and legal recordkeeping. | PayU and internal finance or support workflows. |
| Aadhaar number | Drivers | Driver KYC and identity verification. | Explicit consent and lawful safety or compliance purpose. | Stored in Supabase with restricted internal access. |
| Driving licence number | Drivers | Driver identity and eligibility verification. | Consent and lawful safety or compliance purpose. | Stored in Supabase with restricted internal access. |
| Precise foreground location | Drivers | Address suggestions and location-aware delivery workflow while using the app. | Consent and service delivery. | Google Maps Platform and operational delivery flows. |
| Precise background location | Drivers with an active delivery | Real-time trip tracking during active deliveries only. | Explicit consent and service delivery. | Operational delivery tracking workflows and relevant users for the active booking. |
| Proof-of-delivery photos | Drivers | Delivery confirmation, records, and dispute handling. | Service delivery and legitimate operational need. | Stored in Supabase deliveries bucket with private access controls. |
| Bank account number, IFSC code, or UPI ID | Drivers | Payout requests and settlement. | Explicit consent and payment processing. | Stored in Supabase and used for payout workflows. |
| Push notification token | Drivers | Booking alerts and service notifications. | Consent and service delivery. | Expo and Firebase Cloud Messaging. |
| Earnings data | Drivers | Booking earnings, platform fee calculation, and payout records. | Service delivery, accounting, and lawful business purpose. | Stored in Supabase and used in finance or payout workflows. |
| Company name, GST number, and PAN number | Fleet Aggregators | Business KYC, account setup, tax records, and operational verification. | Consent and lawful business purpose. | Stored in Supabase and used in support or compliance workflows. |
| Driver invitation records | Fleet Aggregators | Invite drivers to join a fleet and link them to aggregator operations. | Service delivery and legitimate operational need. | Stored in Supabase and used in invitation flows. |
Shippers
Shippers can create bookings, pay for deliveries, and track service activity.
- We collect phone number, full name, profile photo, and role for account setup.
- Email is optional and used mainly for payments through PayU.
- Business name and GST number are optional profile fields.
- Booking data includes pickup and drop addresses, cargo type, weight, distance, and price so a delivery can be created and fulfilled.
- We store payment transaction IDs returned by PayU for reconciliation, support, and records.
Drivers
Drivers need additional verification and delivery workflow data because they complete trips and receive payouts.
- Aadhaar number and driving licence number are collected for KYC and driver verification.
- Foreground location is used for address suggestions and in-app delivery workflow.
- Background location is used only while a driver has an active delivery and only for real-time trip tracking.
- Proof-of-delivery photos are captured and stored privately for delivery records.
- UPI ID, bank account number, and IFSC code may be collected for payout requests.
- Push notification tokens are used for booking alerts and service notifications.
- Earnings data includes booking value, platform fee, and net payout.
Fleet Aggregators
Fleet aggregators can manage business identity and invite drivers into fleet operations.
- We collect company name, GST number, and PAN number for KYC and business records.
- We collect driver invitation records, including invited driver phone numbers.
Sensitive Personal Data
Certain data needs stronger protection. For UrbanCarriers, this includes Aadhaar number and bank or UPI payout details. We treat this information as sensitive and collect it only when it is needed for KYC, payouts, or compliance.
Explicit consent
Before we collect driver Aadhaar details or payout details, we should clearly ask for explicit consent and link to this policy.
Limited use
We use sensitive data only for the purpose explained at the time of collection. It is not used for marketing.
If you do not want to provide sensitive data, some driver features such as KYC approval or payout processing may not be available. You may also withdraw consent later, subject to records we must retain for legal or operational reasons.
Background and precise location
UrbanCarriers uses location in two different ways, and this is important for Google Play disclosure.
Precise foreground location
Used when a driver is actively using the app for address suggestions, map display, and trip workflow.
Precise background location
Used only for drivers, only during an active delivery, and only so the shipment can be tracked in real time.
On Android, this may run through a persistent foreground service while an active delivery is in progress. A driver can stop background location by going offline, ending the active delivery flow, or changing device location permissions. If location access is denied, some app features may not work properly.
Contacts permission
The app can read device contacts only to help users fill pickup or drop contact name and phone fields faster.
- Contacts are read only on the device.
- Contacts are never uploaded to any UrbanCarriers or third-party server.
- Contacts are not used for advertising or marketing.
- You can deny or remove this permission from your device settings at any time.
How we use data
- Create accounts and log users in through OTP verification.
- Match bookings with drivers and fleet operations.
- Show maps, search addresses, and support booking flows.
- Track active deliveries in real time where needed.
- Verify driver and fleet identity and eligibility.
- Process payments, payouts, and transaction records.
- Store proof-of-delivery records and handle disputes.
- Send booking alerts, updates, and other service notifications.
- Support fraud prevention, safety, compliance, and customer support.
- Improve app reliability and user experience.
Third-party processors
We use trusted service providers to operate the app. They receive only the data needed for their part of the service.
| Processor | Purpose | Country | Privacy policy |
|---|---|---|---|
| Supabase | Database, authentication, and storage. | India (AWS ap-south-1, Mumbai) | https://supabase.com/privacy |
| Twilio | OTP SMS delivery. Receives phone number only. | United States | https://www.twilio.com/en-us/legal/privacy |
| PayU India | Payment processing. Receives name, email, amount, and transaction ID. | India | https://payu.in/privacy-policy |
| Google Maps Platform | Address search, autocomplete, map display, and location queries. | United States / Global | https://policies.google.com/privacy |
| Expo / Firebase Cloud Messaging | Push notifications. Receives push notification token. | United States | https://expo.dev/privacy |
Data retention
We keep personal data only as long as needed for the purpose it was collected for, unless the law requires a longer period.
- Account profile data: while the account is active and up to 24 months after inactivity.
- Booking and delivery records: up to 8 years for support, accounting, disputes, and compliance.
- Payment and payout records: up to 8 years for finance, tax, and reconciliation.
- Driver KYC records: for the period of active onboarding or engagement and up to 5 years after closure where needed for compliance or disputes.
- Proof-of-delivery photos: up to 24 months unless a dispute or legal hold requires longer retention.
- Push tokens: until logout, uninstall, token refresh, or reasonable inactivity cleanup.
- Contacts from the contact picker: not retained by us because they are not uploaded.
Your rights and choices
Under the DPDPA, you can ask us to help you understand, correct, or erase your personal data, subject to legal and operational limits.
- Ask what personal data we hold about you.
- Request correction of inaccurate or outdated information.
- Request erasure of personal data that is no longer needed.
- Withdraw consent for future processing where consent is the basis.
- Raise a grievance if you are not satisfied with how your data is handled.
You can also control permissions such as location, camera, contacts, and notifications through your device settings.
Security
We use reasonable security measures to protect personal data, including authentication controls, role-based access, secure cloud storage, private storage controls for delivery photos, and encrypted connections where applicable.
No system is perfectly secure, so we cannot promise absolute security. We review access and handling practices regularly and limit internal access to people who need it.
Children
UrbanCarriers is not intended for children under 18 years of age. We do not knowingly allow children to create driver, shipper, or fleet aggregator accounts.
Policy changes
If we update this policy, we will change the effective date and version number on this page. For material changes, we will also notify users in the app before or when the updated policy takes effect.
Grievance Officer
If you want to exercise your rights, withdraw consent, request deletion, or raise a grievance, contact:
Address
Speedloop Auto Pvt Ltd
Plot 296, Sector 10, PCNTDA
Pune 411039
Google Play Data Safety summary
This summary is provided in a format that is easy to compare against the app’s Google Play Data Safety disclosures.
| Data type | Collected | Shared | Purpose |
|---|---|---|---|
| Phone number | Yes | Yes | OTP login and account access. |
| Name and profile details | Yes | Limited | Account setup and identity within the service. |
| Photos | Yes | Limited | Profile setup and proof of delivery. |
| Location | Yes | Limited | Address suggestions and real-time delivery tracking. |
| Financial information | Yes | Limited | Payments, payouts, earnings, and transaction records. |
| Government ID and KYC data | Yes | Limited | Driver and fleet verification. |
| Contacts | Read on device only | No | Contact picker convenience. Not uploaded to our servers. |
| Push token | Yes | Yes | Booking alerts and service notifications. |