Rider Privacy Policy

1.Scope

This policy covers the Doz rider mobile application, rider account services, scooter and ride operations, customer support, and the public pages that support those services.

It describes the data handled by the current product. It does not create a fixed retention period or a promise about infrastructure controls that are not stated below.

2.Information we handle

3.How information is used

• Create and secure accounts, complete phone or social sign-in, and maintain sessions.
• Show available vehicles, start and operate rides, calculate charges, enforce service and parking zones, and investigate ride or safety issues.
• Tokenize payment cards, fund wallets, process transactions, and maintain subscription, discount, and loyalty features.
• Answer support requests, deliver messages and notifications, diagnose failures, and operate or improve product features.
• Prevent misuse, enforce terms, resolve disputes, maintain required records, and respond to applicable legal or safety requests.

4.Recipients and transfers

Information is sent to the Doz API and the hosting, database, media, communications, and operational systems used to provide the service. Depending on the feature and deployed configuration, information can also be sent to the following recipients.

• Checkout.com for card tokenization, payment processing, and 3DS.
• Google and Apple for the sign-in flow you choose; Google Maps and configured geocoding or routing providers for map and address features.
• IP-geolocation providers for country suggestion during phone enrollment.
• Expo for push delivery and app updates, and Sentry for crash or performance monitoring when configured.
• Configured OTP, email, customer-support, media-storage, and infrastructure providers.
• Recipients required for a valid legal or safety request when the request applies to records held by the service.

The repository does not establish every provider contract, processing location, or provider retention setting. Those deployment details must be confirmed by the service owner.

5.Permissions and choices

• Location permissions can be changed in device settings. Core rental actions require location; background access is requested for active-ride operation, not general browsing.
• Camera and photo-library access are requested when scanning a vehicle or choosing parking or support media. Microphone access is requested only when recording a support voice message.
• Push notifications can be declined or changed in device settings. Some service communications may still be delivered by another configured channel.
• Saved places and payment methods can be managed in the app. Optional support media and an optional deletion reason do not need to be supplied.
• The reviewed Rider source contains no advertising SDK or personalized-ad feature. Provider practices still need to be assessed separately under store tracking rules.

6.Retention and account deletion

An authenticated rider can request deletion in the app. A request schedules account-identifier erasure after a 10-day grace period and can be cancelled during that period. An active ride or unsettled payment blocks the request, and processing is deferred if one of those blockers exists when the request becomes due.

When processing completes, direct account fields and sign-in credentials are erased or replaced, access is disabled, and selected saved-place, payment-method, device, push-token, session, and OTP records are purged. Subscription renewal, wallets, and loyalty activity are disabled.

Financial, ride, wallet, subscription, support, loyalty-history, audit, and marketing-suppression records are retained against the anonymized account where the current deletion process requires them. Support text or media, parking proof, ride locations, ratings, and suppression records may still contain information connected to the former account.

For Apple sign-ins with a stored current authorization record, Doz attempts to revoke the Apple authorization when deletion is processed. Older Apple-linked accounts without the stored revocation credential receive instructions to remove Doz from Sign in with Apple in iPhone settings.

No single fixed period for every retained database row, provider object, log, or backup is published in this policy. The accountable owner must approve the record and provider lifecycles that apply to the deployed service.

7.Security boundaries

The app stores selected credentials in platform secure storage. Release configuration requires HTTPS for the Doz API and configured Sentry endpoint, and Checkout-hosted payment fields use HTTPS. These controls do not prove encryption at rest for every database, object store, log, backup, or provider system.

No online or storage system can guarantee absolute security. Contact us if you believe your account or information has been exposed.

8.Age limits

The rider service is intended for people who meet the minimum age and other eligibility rules shown in the applicable terms and in-app requirements. Contact us if information may have been submitted by a person who was not eligible to create an account.

9.Privacy requests

Use the in-app controls for account deletion, permissions, saved places, payment methods, and notification settings. You can also contact us to ask about access, correction, or another privacy request. The available response and any limits depend on the request, retained record, account status, and applicable requirements.

10.Policy changes

This page may be updated when product behavior, providers, or legal requirements change. The date at the top identifies the version currently published.