DDD Cabs

Privacy Policy

How DDD Cabs collects, uses, protects, and manages customer and authorized Google account information.

Last updated: October 12, 2026

DDD Cabs provides cab booking, travel, and business-management services. This Privacy Policy explains how DDD Cabs handles information on dddcabs.com, our booking services, and the DDD Cabs business-management and marketing tools.

Information We Collect

We may collect information you provide when you request a quote, book a ride, contact us, create an account, or use our services. This may include your name, mobile number, email address, pickup and drop details, booking details, communications, and payment or transaction status information. We may also collect limited device, browser, security, and service-usage information needed to operate, secure, and improve our services.

Location Data

DDD Cabs may access and collect location information from your device when you use location-based features in the DDD Cabs mobile application. Depending on the permission you grant, this may include approximate or precise location information.

Current-location pickup is optional. When you choose it, DDD Cabs may collect a one-time approximate or precise device location and send its coordinates to DDD Cabs and relevant mapping services to resolve the pickup address. Google Maps Platform is used for applicable server-side place and route operations. You can enter a pickup address manually without granting device location permission.

For an Outstation booking, the resolved pickup coordinate may be used to calculate the route and fare. The resolved pickup and drop coordinates are stored with that booking’s route details. This is different from the one-time device-location lookup itself: retained booking-route coordinates are not subject to an immediate-deletion promise.

Live Trip Sharing is an optional, customer-activated feature. While sharing is active, DDD Cabs may collect precise location, transmit it through the DDD Cabs backend, and let up to two people the customer chooses to invite with the sharing link view the latest shared trip location. A browser can retain its viewer slot for up to two minutes after a short interruption; the two-viewer limit does not verify a viewer’s real-world identity.

Location access is controlled by the permissions you grant through your device settings. You can change or disable location permission at any time, although some location-based features may not work correctly if permission is disabled. DDD Cabs does not sell users’ precise location data.

Background Location for Live Sharing

DDD Cabs uses background location only when a customer actively starts the Live Location Sharing feature.

While Live Location Sharing is active, the app may continue to collect the customer’s precise location in the background so that the shared live trip location can remain updated even when the app is minimized, closed, or not actively in use. Sharing starts only after the customer chooses the feature and grants the required device permissions. When background tracking is running on Android, the app uses a visible service notification; if Android ends the app or service, location updates stop.

Background location is not used for normal cab searches, booking, fare calculation, account use, or other standard app activity. DDD Cabs does not continuously track a customer’s location when Live Location Sharing is not active.

The customer can stop Live Location Sharing at any time. Stopping stops location updates on the phone and asks the DDD Cabs backend to revoke the sharing link. If the phone is offline or the backend cannot be reached, the last stored location may remain accessible through the link until revocation succeeds or the sharing session expires. DDD Cabs retains only the latest point, not a point history, and schedules the live-sharing record for deletion seven days after sharing ends.

DDD Cabs does not send the device’s one-time current-location reading or live-sharing coordinates to advertising or analytics SDKs.

The public live-trip viewer uses OpenStreetMap map tiles. DDD Cabs does not send the customer’s raw device GPS coordinates directly to OpenStreetMap. After the viewer receives the shared location from the DDD Cabs backend, the viewer’s browser requests map tiles for the area being displayed; those tile requests can reveal an approximate map area to the tile service.

How We Use Customer Information

DDD Cabs uses customer information to provide and support bookings, communicate about rides and account activity, process payments through applicable payment providers, prevent fraud and misuse, provide customer support, meet legal obligations, and improve our services. We use only the information reasonably necessary for these purposes.

Google OAuth and Google User Data

Authorized DDD Cabs administrators may choose to connect a Google Account to the DDD Cabs AI Marketing module. We request Google OAuth permissions only when an administrator starts that connection and only for the Google services and features enabled in the module.

Google user data is accessed and used only to provide the authorized DDD Cabs business-management and marketing functionality. DDD Cabs does not sell Google user data.

DDD Cabs’ use of information received from Google API Services adheres to the Google API Services User Data Policy, including the Limited Use requirements where applicable.

Google Business Profile Data Access

When an administrator authorizes Google Business Profile access, DDD Cabs may access the selected business account and location identifiers, Business Profile posts, reviews, review-reply information, and permitted performance or Search Console information. The module uses this information to let the authorized administrator select a location, review business activity, prepare post or reply drafts, and publish or synchronize approved content when the administrator enables those features.

Google Ads Data Access

When an administrator authorizes Google Ads access, DDD Cabs may access the selected Ads customer identifier and permitted reporting information such as campaigns, search terms, keywords, performance, and conversion-action diagnostics. This information is used to provide the authorized reporting, recommendations, campaign-draft, and business-management functions. Any Ads changes remain subject to the module’s configured approvals and explicit administrator action.

How Google User Data Is Used

Google user data is used only to operate the administrator-visible Google Business Profile, Search Console, or Google Ads feature that the authorized administrator requested. We do not use Google user data for unrelated advertising profiles, surveillance, creditworthiness decisions, or to train generalized models. We request the minimum relevant OAuth access and do not use Google data for a purpose not disclosed in this policy.

Sharing of Information

DDD Cabs does not sell personal information or Google user data. We share information only when needed to provide the service you request, with service providers acting on our behalf (such as payment, hosting, communications, mapping, or analytics providers), when required by law, to protect the security of our services, or in connection with a lawful business transfer. Google user data is not transferred to third parties except as necessary to provide the authorized user-facing functionality, with the user’s consent, for security, to comply with law, or as otherwise permitted by the Google API Services User Data Policy.

Data Storage and Security

We use reasonable administrative, technical, and organizational safeguards designed to protect information from unauthorized access, alteration, disclosure, or destruction. OAuth refresh tokens used by the AI Marketing module are stored server-side in encrypted form; they are not included in public pages or ordinary API responses. Access is limited to authorized systems and administrators, but no internet transmission or storage method can be guaranteed completely secure.

Data Retention

We retain customer and service information only for as long as reasonably necessary to provide services, maintain required records, resolve disputes, enforce agreements, prevent misuse, and meet legal obligations. Resolved Outstation route coordinates are retained as part of the relevant booking record; DDD Cabs does not set a separate retention period for those coordinates in this policy. Google connection information and encrypted refresh tokens are retained only while the connection is active and needed for the authorized functionality, unless a longer period is required by law. We delete or de-identify information when it is no longer needed, subject to lawful retention requirements.

Your Deletion and Revocation Rights

You may request deletion of your DDD Cabs account or applicable personal information by contacting us using the details below. We will handle valid requests in accordance with applicable law and our legal record-keeping obligations. Disconnecting a Google integration in DDD Cabs ends future access through that integration and removes the stored connection credentials used for it.

You can also revoke DDD Cabs’ access to your Google Account at any time through your Google Account’s Third-party apps and services permissions page. Revoking access may prevent connected Google Business Profile or Google Ads functionality from continuing until an authorized administrator reconnects it.

Contact Us

For privacy questions, Google data requests, deletion requests, or help with revoking access, contact DDD Cabs at support@dddcabs.com or call +91 9090 404005.

Updates to This Privacy Policy

We may update this Privacy Policy to reflect changes in our services, legal requirements, or Google API practices. We will post the revised policy on this page and update the “Last updated” date. Where required, we will provide additional notice or obtain consent before using information for a materially different purpose.