DA

DriverAccept

درايفر أكسبت

Privacy Policy · v3

Legal document · v3

Privacy Policy

Effective: 25 August 2026 · Last updated: 25 August 2026 · Package: com.driveraccept

By using DriverAccept you acknowledge this Policy. You understand what we process, why we process it, that Accessibility may read trip-offer screens in driver apps you enable, and how to request deletion. Use of the App remains governed by the Terms of Use (v3), including your sole responsibility for how you use it.
Not a safety or liability warranty. This Policy explains data practices. It does not make the Developer responsible for your driving, your settings, third-party platform actions, or any harm that may result from using the App. Those matters are addressed in the Terms of Use.

This Privacy Policy explains how DriverAccept (“the App”, “we”, “us”; Android package com.driveraccept) collects, uses, stores, and shares information when you download, activate, or use the App. DriverAccept is an independent productivity tool for adult professional drivers. It is not affiliated with, endorsed by, sponsored by, or operated by Jeeny or any other ride-hailing / delivery platform.

1. Who we are (controller)

DriverAccept is developed and operated by an independent developer. For privacy questions, data-deletion requests, or Google Play–related inquiries, use the support channel in Section 21. We determine the purposes of processing described here. Infrastructure providers such as Supabase act as processors on our instructions for hosting.

2. Scope

This Policy applies to the Android app com.driveraccept, related backend services used for subscription licensing and optional earnings reporting, and these hosted legal pages. It does not cover third-party driver apps (for example Jeeny Driver or any other captain app you enable), Google, WhatsApp, your mobile carrier, or device maker — those have their own policies. We are not responsible for how those parties collect or use your data.

3. Data we collect

3.1 Device identifier. To bind trial and subscription status to one device, the App reads Settings.Secure.ANDROID_ID. If that value is missing or unreliable, the App generates a random UUID stored in app-private storage and uses it as the device ID. This identifier is sent to our backend over HTTPS for subscription checks and activation-code redemption.

3.2 Subscription / activation data. When you redeem an activation code, the App sends the code and your device ID to our servers over HTTPS. Servers return whether the subscription is active and an expiry time. A short offline cache of subscription status may be stored on the device so the App can continue briefly when the network fails. We may also keep records needed to prevent fraud, shared codes, chargebacks, and abuse.

3.3 Accepted-trip earnings (server sync). When a trip offer is accepted through the App’s automation, the App may upload a minimal earnings report over HTTPS, including: a local trip ID generated by the App, fare amount, currency code, acceptance timestamp, and device ID. This supports subscription-related reporting and product operation. It is not sold for advertising. Fare figures come from on-screen fields the App reads; we do not guarantee they match the platform’s final payout.

3.4 Local trip history and settings. Trip history, acceptance rules, language, theme, enabled driver apps, overlay preferences, and other settings are stored locally on your device (Room database / DataStore). Local history retention follows your in-app retention setting. Uninstalling the App or clearing App storage removes local data. We cannot recover local data after you delete it.

3.5 Support communications. If you contact us (for example via WhatsApp), we process the information you choose to send (messages, screenshots, device details, logs) solely to provide support, investigate abuse, and defend legal claims. Do not send passwords or other people’s personal data.

3.6 Accessibility screen content (on-device processing). With your explicit permission in Android Settings and after an in-app disclosure, the App’s Accessibility service may read on-screen trip-offer fields (such as fare, distance, time, and rating) inside a supported driver app package you enable, solely to apply rules you configure and to tap Accept or Reject. That screen content is processed on the device for automation decisions. Fare and related fields for accepted trips may also be stored locally and, as in 3.3, synced in minimal form to our servers.

Android Accessibility is a powerful permission. We design the service to monitor supported driver packages you enable — not banking apps, chat apps, or password fields. The operating system may still expose additional window content in some situations. We do not intend to collect that extra content, we do not sell it, and we are not responsible for OS-level behavior outside our reasonable control. You can revoke Accessibility at any time.

3.7 Legal consent metadata. The App stores locally that you accepted the Terms and this Policy and which document version you accepted, so we can re-prompt after material updates.

4. Android permissions (why they exist)

You can deny or later revoke optional permissions. Core licensing still needs network access.

5. Data we do not collect

6. Why we use data (purposes)

7. Legal bases (where applicable)

Depending on your location, we rely on one or more of: (a) performance of a contract (providing the subscribed App under the Terms of Use); (b) your consent (Accessibility permission, legal-document checkbox at activation, optional features — withdrawable in Android settings or by uninstalling); (c) legitimate interests in operating licensing, preventing abuse, securing the service, and defending claims — balanced against your rights; (d) legal obligation where disclosure or retention is required by law.

8. On-device processing vs server

Offer detection and most Automation decisions happen on your device. We do not receive a live video of your screen. Server-side processing is limited to licensing/activation, optional accepted-trip earnings fields described above, and information you send in support messages. You remain responsible for what appears on your screen and for any third-party app’s own collection.

9. Sharing and processors

Subscription and earnings data are processed on our hosted backend (Supabase) over HTTPS. Supabase acts as a data processor / infrastructure provider for us. We do not sell personal data. We may disclose information if required by applicable law, court order, or to protect rights, safety, and integrity of the App, users, or the public, or in connection with a merger or transfer of the product (the successor must honor this Policy or give notice).

WhatsApp is a separate service; messages you send there are also subject to Meta/WhatsApp policies. We are not responsible for WhatsApp’s processing.

10. International transfers

Our backend infrastructure may store or process data in data centers outside your country (including regions used by Supabase). By using the App you understand that such transfers may occur as needed to operate the service, with industry-standard transport encryption (HTTPS). Where a transfer law requires extra safeguards, we rely on the processor’s published terms and standard contractual mechanisms they offer, to the extent applicable.

11. Security

Network traffic to our backend uses HTTPS. Device identifiers and subscription caches are stored in app-private storage. No method of transmission or storage is 100% secure. You use the App understanding residual risk, including risk from a lost/stolen/unlocked device, malware, or a compromised support chat. We are not liable for unauthorized access that occurs despite reasonable measures, to the extent permitted by law (see also the Terms of Use).

12. Retention and deletion

Deleting data does not undo actions already taken on a Third-Party Platform (accepts, rejects, bans). Those are between you and that platform.

13. Your rights

Subject to applicable law (including GDPR/UK GDPR where they apply), you may have rights to access, correct, delete, restrict, or object to certain processing, to data portability, and to withdraw consent where processing is consent-based (for example by disabling Accessibility or uninstalling). Withdrawal does not affect prior lawful processing. To exercise rights, use Section 21. You may also lodge a complaint with a supervisory authority where you live or work.

We may refuse requests that are unfounded, excessive, or that would prevent us from enforcing the Terms, detecting abuse, or complying with law.

14. Children

The App is intended only for adult professional drivers 18 years of age or older. It is not directed to children. We do not knowingly collect data from children. If you believe a minor used the App, contact us so we can delete related data we control. You must not allow a minor to use the App on your device.

15. Automated processing

Automation applies your rules to trip-offer fields on device. That is not profiling used to grant or deny a legal right vis-à-vis us, other than checking whether a subscription is valid. We do not make automated credit or hiring decisions about you.

16. Third-party apps and platforms

When the App reads a driver app’s screen or taps Accept/Reject, that driver app and its company continue to process your account, location, trips, and payments under their privacy notices. We do not control them. Enabling the App does not make us the controller of that platform’s data, and we are not responsible for their practices, data breaches, or account actions.

17. Google Play Data Safety

Disclosures in Google Play Console (Data safety) are intended to match this Policy: device or other IDs; financial info limited to trip fare amounts for accepted trips; encrypted in transit; deletion available via support; no advertising ID / no third-party ads. If a Console label is ever shorter than this Policy, this Policy controls the detail.

18. These legal web pages

The hosted Terms and Privacy pages may store a language preference in your browser (localStorage) so English or Arabic stays selected. We do not use advertising cookies on these pages. Server logs of the host (for example GitHub Pages) may record standard technical data (IP, user agent) under that host’s policy; we do not use that for ads.

19. Relation to the Terms of Use

This Policy is incorporated into the Terms of Use. Nothing in this Policy limits the disclaimers, assumption of risk, release, limitation of liability, or indemnities in the Terms, except where privacy law gives you a non-waivable right. Providing the App, or processing data as described here, does not create a duty of care for driving, earnings, or third-party accounts.

20. Changes

We may update this Policy. Material changes bump the in-app legal document version (currently v3) so the App may ask you to review and accept again before continued activation/use of gated features. If you do not agree, uninstall the App and disable Accessibility and overlay.

21. Contact

WhatsApp support: +962 77 671 3289
Product: DriverAccept (com.driveraccept)

English is the original language of this Policy. Arabic is provided for convenience. If the two versions conflict, English prevails except where mandatory law requires otherwise.