Privacy Policy for Auto Driver

Effective date: 11 June 2026
Last updated: 18 October 2026

1. Who We Are

This application, "Auto Driver" (the "App"), is developed and published by Binaryscript Private Limited ("Binaryscript", "we", "us", "our"). This Privacy Policy explains what data the App processes, what leaves your device, what stays on your device, and the rights you have over your data.

If you have any questions about this policy or your data, write to us at support@binaryscript.com.

2. Scope

This policy applies to the Auto Driver Android application distributed through the Google Play Store. It does not apply to the ride-hailing platforms the App works alongside (Uber, Ola, Rapido, inDrive), or to any other application on your device. Those services are operated by third parties and are subject to their own privacy policies.

The App serves two groups of users, decided from your Google Play billing country:

• Users in India create an account by verifying their phone number, either with Truecaller one-tap verification or with a one-time password (OTP) sent over SMS by MSG91, at their choice, and subscribe through UPI AutoPay (PhonePe).
• Users outside India do not create an account and do not sign in. They subscribe through Google Play Billing.

We do not ask for your email address, postal address, or your ride-hailing platform credentials, and we never request, store, or transmit your Uber, Ola, Rapido, or inDrive password.

3. Summary in Plain Language

• Your trip history, the screens the App reads from ride-hailing apps, your preferences and any video or audio recorded by Secret Camera stay on your phone. They are never uploaded to us.
• Trip Offers Picker uses the Android Accessibility Service, after you accept a prominent disclosure in the App, only to read the ride-offer screens of Uber, Ola, Rapido and inDrive. The text is read on your device with Google ML Kit, offline.
• We send app usage events, crash reports and performance data to Google Firebase so we can understand which features are used and fix problems. Offer details (fare, distance, duration, pickup and drop-off, passenger rating and screen content) never leave your phone: analytics only counts detected offers by platform and currency, and trip cards by platform, grade and currency (Section 5.1).
• Users in India sign in by verifying their phone number (via Truecaller one-tap or an MSG91 SMS OTP). Our server stores the phone number, basic device information, an approximate location of your network address and your subscription status. Users outside India have no account.
• Subscriptions are paid through PhonePe UPI AutoPay (India) or Google Play Billing (outside India). We do not receive your card, UPI PIN, bank account, or wallet details.
• The App shows no ads, and we do not sell your data.

4. Data Processed on Your Device Only (Not Transmitted)

4.1 Trip Offers Picker and the Accessibility Service

Before Trip Offers Picker can be turned on, the App shows a prominent disclosure explaining what the Accessibility Service accesses and why. The service is enabled only if you accept that disclosure and then switch it on yourself in Android Settings.

When Trip Offers Picker is on, the App's Accessibility Service detects when Uber, Ola, Rapido or inDrive shows a ride offer, and reads that offer screen: its window content, and screenshots of the offer screen taken through the Android accessibility API. The service configuration does not at the operating-system level restrict which apps it receives events from; however, the App's code processes events only from these four ride-hailing apps. Events from all other apps are discarded immediately and are never read, stored, or transmitted.

The App does not use MediaProjection screen recording. Screenshots are held in memory only for as long as it takes to read the offer, are never saved to storage, and never leave your device.

The Accessibility Service is used for nothing else. It does not read other apps, and it does not read passwords, messages, what you type, or payment screens. You can turn it off at any time in Android Settings; Trip Offers Picker then stops working until you turn it on again.

4.2 On-device text recognition

The text on an offer screen is read on your device by Google ML Kit text recognition, which is bundled with the App and works offline. No image or text is sent to Google or to us for this.

4.3 Trip cards and trip history (local database)

From each ride offer, the App keeps only: the platform, the time of the offer, the fare, the distance, the duration, the passenger rating, and the pickup and drop-off text as shown on the offer. It uses them to show a trip card over the ride-hailing app with your earnings per km and per hour, and saves them in a trip history on your device. GPS coordinates are not captured or stored.

This database is stored only on your device and is never uploaded to us or to any third party. It is deleted when you use Clear history in the App, when you delete your account in the App, or when you uninstall the App.

4.4 Secret Camera recordings

If you turn on the Secret Camera feature, the App records video in the background and, only if you enable it, audio, using your device camera and microphone. Recordings are stored only on your device, in the App's own storage. They are never uploaded to any server, not synced to any cloud, and not shared with us. You can view and delete them in the App. They are removed when you delete them, when you delete your account in the App, or when you uninstall the App.

4.5 Floating button, notifications and battery optimisation

The floating Copilot button is drawn over other apps so you can control the App while you drive. The App also shows the notifications Android requires for its foreground services, and asks to be exempted from battery optimisation so Android does not stop it while you are driving. These are device permissions only; no data is collected through them.

4.6 User preferences

Your in-app settings, such as trip filter thresholds, overlay position and size, Secret Camera options, app language and onboarding state, are stored on your device using Android DataStore. They are not transmitted.

5. Data Transmitted Off Your Device

5.1 Google Firebase Analytics

The App sends product-usage events to Google Firebase Analytics so we can understand which features are used and improve the product. The events include screen views, onboarding progress, permission grants, settings and filter changes, Trip Offers Picker, Copilot and Secret Camera starting and stopping, Secret Camera session details (such as the camera, quality, duration and whether audio was on), and subscription and login steps.

When Trip Offers Picker detects an offer, the event carries only the platform and the currency, and the trip card event carries only the platform, the grade the App gave it and the currency. The offer's details (the fare, the distance, the duration, the pickup and drop-off, the passenger rating, screenshots or other screen content) never leave your phone, and analytics events never include your recordings.

Firebase Analytics automatically attaches an app-instance identifier, coarse device information (model, operating system version, language, country), and limited network information. If you sign in (users in India), the App also sets your account identifier as an analytics user property, so your usage events are linked to your account. If you never sign in, they are not linked to your identity. See the Firebase privacy documentation for full details.

5.2 Google Firebase Crashlytics

If the App crashes or hits an error, a report is sent to Google Firebase Crashlytics so we can diagnose and fix the problem. Crashlytics collects the stack trace, the device model, the Android version, the App version, and related technical information. It does not collect your trip history, your recordings, or your preferences.

5.3 Google Firebase Performance Monitoring

The App sends performance traces to Google Firebase Performance Monitoring, such as how long the App takes to start and how long network requests take, together with the device model, operating system version and country. They do not include your trip history, your recordings, or the content of your requests.

5.4 Google Firebase Remote Config

The App fetches settings from Google Firebase Remote Config, such as the latest App version and feature switches. Firebase receives the app-instance identifier and basic device information to answer.

5.5 Google Consent Mode

The App shows no ads. We use Google Consent Mode to control the advertising signals Firebase Analytics may pass to Google Ads, which we use to measure our own advertising (for example, installs and subscriptions that came from our ads). For users in the European Economic Area, the United Kingdom and Switzerland, all advertising signals (ad storage, ad user data and ad personalisation) are denied, so analytics data is not used for advertising. Elsewhere, these signals are granted.

5.6 Account and login (users in India only)

Users in India create an account by verifying their phone number, either through Truecaller one-tap verification or through an OTP sent over SMS by MSG91, at their choice.

• Truecaller: if you choose Truecaller, the Truecaller SDK handles the verification and our server receives a verified phone number and, where available, your name and basic profile information from Truecaller. Your use of Truecaller is also subject to Truecaller's own privacy policy.
• MSG91: if you choose SMS OTP, your phone number is sent to MSG91, our SMS provider, so it can deliver the one-time password on our behalf.

Our backend (api.binaryscript.com) stores, with your account: your phone number, your name if Truecaller provides it, a device identifier (Android ID), device model and operating system information, the App's language, your country, the referral code you joined with (if any), the approximate location described in Section 5.7, and your subscription status. It also issues authentication tokens to keep you signed in. This account is used to sign you in and to activate and restore your subscription. We do not collect your email address or postal address.

Users outside India have no account, and the App sends none of this data to our backend for them.

5.7 Approximate location (users in India only)

• When the App starts, for users in India, it asks BigDataCloud (a geolocation service, through its reverse-geocode-client service) to estimate your approximate location from your network (IP) address: state, city, country and the coordinates of that area. No GPS and no location permission are used for this.
• Once you are signed in, the App sends this approximate location to our backend with your account once, and we store it once. We do not update or overwrite it as you move. It is not sold and not shared with advertisers.
• For users outside India, the App makes no location lookup.

5.8 Payments and subscriptions

• Users in India: subscriptions are paid with UPI AutoPay through PhonePe, via our backend. Our backend keeps the order, the plan and the payment and subscription status. We never see your UPI PIN, bank account or card details.
• UPI apps on your phone (users in India): on the subscription screen, the Razorpay SDK, provided by Razorpay Software Private Limited, checks which UPI apps on your phone support UPI AutoPay, so the App offers only those. The SDK sends the list of UPI apps it found to Razorpay, for Razorpay's own analytics. No payment goes through Razorpay: every payment is made through PhonePe. The App does not otherwise read the list of apps installed on your phone.
• Users outside India: subscriptions are paid through Google Play Billing. You do not need an account; Google handles the payment, and the App checks your subscription on your device with Google Play. Our servers receive nothing about it.

6. Data We Do Not Collect

• We do not collect your email address or postal address. (For users in India we store your phone number, and your name if Truecaller provides it, for your account — see Section 5.6.)
• We do not collect GPS or precise location coordinates. (For users in India we store an approximate location of your network address — see Section 5.7.)
• We do not upload your trip history, the screens the App reads, or your Secret Camera recordings.
• We do not read other apps, passwords, messages, what you type, or payment screens through the Accessibility Service.
• We do not collect your ride-hailing platform passwords or session tokens.
• We do not collect your contacts, calendar, SMS, or call logs.
• We do not collect the list of apps on your phone, apart from the UPI app check in Section 5.8.
• We do not use any advertising SDK and we do not show ads.
• We do not use any attribution SDK (such as AppsFlyer, Adjust, Branch, or similar).
• We do not sell or rent any data to anyone.

7. Permissions We Request and Why

• Accessibility Service: only if you turn on Trip Offers Picker and accept the in-App disclosure, to read the ride-offer screens of Uber, Ola, Rapido and inDrive (see Section 4.1).
• Draw over other apps (SYSTEM_ALERT_WINDOW): to show the Copilot floating button and the trip card.
• Notifications (POST_NOTIFICATIONS): to show the persistent notifications required by Android for our foreground services (Copilot, Trip Offers Picker, Secret Camera).
• Ignore battery optimisations: so Android does not stop the App's services while you are driving.
• Camera and Microphone: only if you enable the Secret Camera feature; the microphone only if you turn on audio (see Section 4.4).
• Run at startup (RECEIVE_BOOT_COMPLETED): to bring back the Copilot floating button after your phone restarts, if it was on.
• Foreground Service types (Camera, Microphone, Special Use): required by Android to keep the corresponding features running in the foreground.

Each permission is requested at the point where the feature requires it. You can revoke any permission at any time in Android Settings.

8. Third-Party Services

The following third parties receive limited data as described above:

• Google LLC — Firebase Analytics, Firebase Crashlytics, Firebase Performance Monitoring and Firebase Remote Config. Privacy: https://firebase.google.com/support/privacy and https://policies.google.com/privacy
• Google LLC — Google Play Billing for subscriptions (users outside India). Privacy: https://policies.google.com/privacy
• Google ML Kit for on-device text recognition. Processed entirely on your device; no data is sent to Google through this SDK.
• Truecaller (True Software Scandinavia AB) — one-tap phone-number verification, if you choose it (users in India). Privacy: https://www.truecaller.com/privacy-policy
• MSG91 (Walkover Web Solutions Pvt. Ltd.) — SMS delivery of one-time passwords, if you choose SMS login (users in India). Privacy: https://msg91.com/privacy-policy
• BigDataCloud — approximate location from your network address (users in India). Privacy: https://www.bigdatacloud.com/privacy-and-cookie-policy
• PhonePe Private Limited — UPI AutoPay payments for subscriptions (users in India). Privacy: https://www.phonepe.com/privacy-policy/
• Razorpay Software Private Limited — the Razorpay SDK, which checks which UPI apps on your phone support UPI AutoPay (users in India); no payments. Privacy: https://razorpay.com/privacy/

We do not embed the Google Maps SDK, advertising SDKs, or analytics SDKs other than Firebase. We do not sell, trade or rent your data, and we share it only with the service providers above, as needed to run the App, or when required by law. Razorpay also uses the list of UPI apps it receives (Section 5.8) for its own analytics.

9. Data Retention

• Data stored only on your device (trip history, Secret Camera recordings, preferences) is retained until you delete it in the App (Clear history, deleting recordings, or Delete Account), clear the App's data, or uninstall the App.
• Firebase Analytics event data is retained according to the retention period configured in our Firebase project (Google's default is 14 months for event-level data).
• Firebase Crashlytics and Performance Monitoring data is retained according to Google's default retention policy.
• Account data on our servers (users in India: your phone number, name if provided, device identifier and device information, language, country, referral code, approximate location, and subscription status) is retained for as long as your account is active. When you ask us to delete your account, we delete this data within 30 days, except where we must retain limited records, such as payment records, to comply with law. See How to Delete Your Account.
• Payment and subscription records held by PhonePe or Google Play are retained by those providers according to their own policies.

10. International Transfers

Google Firebase is operated by Google and may process data on servers located in the United States and other countries. By using the App you acknowledge that the limited data described in Section 5 may be transferred to and processed in those countries. Google relies on Standard Contractual Clauses and other lawful mechanisms for such transfers.

11. Your Rights

You have rights over personal data about you. For users in India, your account is identified by your phone number, so we can locate and act on data we hold about you. You can ask us to access, correct, or delete your account data at any time by writing to us, or by following the steps in How to Delete Your Account. Users outside India have no account with us; the data processed about them is held by Google Firebase and Google Play, and they can also exercise their rights directly through their Google account.

11.1 General rights

• Access: ask what data, if any, we hold about you.
• Correction: ask us to correct inaccurate data.
• Deletion: ask us to delete data we hold about you.
• Objection or restriction: ask us to stop or limit certain processing.

11.2 European Economic Area, United Kingdom, and Switzerland (GDPR / UK GDPR)

Our legal bases for processing are (a) our legitimate interests in understanding how the App is used and in diagnosing crashes and performance problems, for Firebase Analytics, Crashlytics and Performance Monitoring (advertising signals are denied for you, see Section 5.5); and (b) the performance of a contract, for subscription handling through Google Play. You have the rights of access, rectification, erasure, restriction, portability, and objection, and the right to lodge a complaint with your national data protection authority.

11.3 California, United States (CCPA / CPRA)

In the previous 12 months we do not sell or share personal information as those terms are defined under the CCPA. California residents have the right to know, delete, correct, and limit the use of sensitive personal information, and the right not to be discriminated against for exercising these rights.

11.4 India (Digital Personal Data Protection Act, 2023)

If you are a Data Principal in India, you have the rights of access, correction, erasure, grievance redressal, and nomination in respect of personal data we hold about you. Our Grievance Officer can be reached at support@binaryscript.com. We will acknowledge your grievance and respond within the time limits required by the DPDPA and its rules.

11.5 How to exercise your rights

Write to support@binaryscript.com with your request. We may ask you for information reasonably necessary to confirm your identity and locate any records.

12. Children

The App is intended for adults who work as ride-hailing drivers. It is not directed to children and is not intended for anyone under the age of 18. We do not knowingly collect data from children. If you believe a child has used the App, please contact us and we will take appropriate steps.

13. Security

We protect the App using standard Android application sandboxing. Data stored on your device is protected by the Android operating system and is accessible only to the App and to anyone with physical or administrative access to your device. Data in transit to Firebase and to our backend is transmitted over TLS. No method of transmission or storage is completely secure; we cannot guarantee absolute security.

14. Changes to This Policy

We may update this policy from time to time. When we do, we will update the "Last updated" date at the top of the document and, for material changes, we will give you notice inside the App or on the Play Store listing before the changes take effect. Your continued use of the App after a change becomes effective means you accept the updated policy.

15. Contact

Binaryscript Private Limited
Email: support@binaryscript.com

For questions about this Privacy Policy, to exercise your rights, or to raise a grievance, write to the address above.