Samvahana TRUST & SUPPORT
Draft preview — business details and operating policies require confirmation before publication.
SAMVAHANA · TRUST CENTRE

Privacy for our partners.

How Samvahana Driver uses information to support bookings, communication and driver earnings.

SAMVAHANA DRIVER Updated: 5 October 2026

Account and verification

We process your registered phone number, profile details, vehicle information and documents submitted for verification and service operation.

Location and availability

With location permission, Samvahana Driver uses your location while you are online or handling an active booking to match nearby requests, support navigation and share relevant trip progress with the customer. Location updates depend on device permissions, connectivity and operating-system restrictions. Continuous tracking while the app is closed is not guaranteed. You can manage location permission in your device settings; restricting it may prevent location-dependent features from working.

Bookings and communication

We process booking offers, accepted work, trip progress and in-app messages to coordinate services with customers.

Earnings and withdrawals

We process earnings, commission, wallet transactions and withdrawal information to administer driver payments.

Sharing with customers

Relevant driver, vehicle and trip-location information is shared with customers to identify their assigned driver and follow their booking.

Who operates the service

Samvahana and Samvahana Driver are operated by DKBN INFRA PRIVATE LIMITED. Our correspondence address is Plot No. 5/22, South Part, Indraprasth Colony, Kamla Nehru Nagar, Jaipur, Rajasthan 302006, India. For privacy questions, email dkbninfra@gmail.com or call +91 8000503718.

Payments and wallet information

We process booking charges, payment status, wallet balances and transaction records to provide payments, refunds and related support. Payment processing involves our payment service providers.

Notifications and operational information

We use notification tokens to send booking and account updates. Our services record operational information such as request times, response status and identifiers associated with requests for troubleshooting and service operation.

Service providers and processing

The service integrates Amazon Web Services for hosting and, where configured, uploaded-file storage; Firebase Cloud Messaging for notification delivery; Mapbox for map display, address search and routes; Google Maps Directions for configured route and pricing calculations; and Razorpay for payment processing. Hosting processes account and booking data. Notification delivery uses device tokens and notification content. Mapping requests can include addresses, coordinates and network information. Payment processing uses relevant payment, transaction and contact details. MSG91 provides OTP/SMS delivery using the registered DKBNSH sender. App-based OTP delivery has been confirmed using the installed release build. Provider processing locations and production configuration are being verified; this draft does not claim that all processing stays within India.

Additional data practices

Accounts are intended for people aged 18 or older. Driver partners must also satisfy the applicable licence and vehicle requirements. Age confirmation still needs to be implemented in onboarding. The reviewed app code uses audio for playback and notification sounds; no microphone-recording feature was identified in that review, but microphone permissions remain in the app configuration and must be resolved before release. No dedicated advertising or marketing-analytics integration was identified in the reviewed source. This does not by itself establish the behaviour of every SDK or any off-platform business arrangement. The intended launch policy is no advertising and no sale of personal data; the final disclosure will reflect the verified production build and business practices.

Data retention

Account information supports your account and bookings while you use the service. The proposed deletion procedure removes unnecessary profile details, photos, saved addresses, emergency contacts, saved UPI identifiers and notification tokens, revokes sessions, and deletes or anonymises associated personal information unless a documented exception applies. The current software is configured to make ordinary closed chats eligible for cleanup 30 days after closure, and detailed order-location points eligible 30 days after collection, excluding records on a retention hold. These periods do not automatically delete booking addresses, invoices or all location-related records. Production cleanup has not yet been verified. Payment, wallet, invoice and dispute records require a separate approved schedule limited to their accounting, refund, fraud-prevention or legal purpose. Driver documents require a separate verification and applicable-obligation review. Exact financial, document, security-log and backup retention periods remain under review. These draft statements must be finalised against the deployed deletion and retention processes before launch.

Your choices

Contact our privacy team to request access to, correction of, or deletion of your personal information, or to raise a privacy concern. We may verify ownership before acting. You can manage permissions through your device settings. Restricting a permission may affect its associated feature. Use our account deletion page to request account and associated data deletion.

Account deletion process

Request deletion of your Samvahana or Samvahana Driver account by emailing dkbninfra@gmail.com. Include the app name and registered phone number with country code. You can submit a request without reinstalling the app. Requests are accepted for manual review; deletion remains blocked until account ownership is securely verified. We will explain the verification steps in our reply. Never send an OTP, password, UPI PIN or payment-card details. Our proposed service target is completion within 7 working days after verification and within 15 calendar days of the initial request, including verification. This timetable is not yet an operational guarantee. If verification cannot be completed, we will explain the outstanding requirement instead of deleting an unverified account.

Policy updates

We will reflect changes to this policy in the updated date shown on this page. Contact support with questions about its contents.