Accessibility access
FareWorth uses Android Accessibility to detect visible text and app-state changes in supported driver apps. On supported Android versions, FareWorth may capture the foreground supported driver-app window and perform on-device text recognition so it can read information such as the fare, service, pickup time and distance, and passenger-trip time and distance.
FareWorth uses this information to calculate and display live fare analysis and to recognise offer and journey-state transitions. FareWorth does not automatically accept or reject trips or press driver-app buttons on your behalf.
Information stored on your device
FareWorth may store structured economic and operational information such as offer timestamps, platform and service type, fare, pickup/trip time and distance, calculated rates, estimated fuel or energy cost, online-session timing, capture reliability, journey lifecycle timing and a rider rating when it is visible and the feature records it with an offer.
FareWorth offer history is designed not to store passenger names, pickup addresses, destination addresses or a GPS trail.
Locally captured Android history is stored in FareWorth's local database. Verified remote Driver Day history, described below, is a separate data source and may be stored in a separate encrypted cache on the device.
On-device processing
Live offer text recognition and profitability calculations are performed on the device. FareWorth does not upload the screenshot, raw Accessibility text or OCR result used for live analysis to operate the public Play build.
FareWorth account, authentication and product access
The current controlled Android product is account-gated. A user signs in with an email address and password through Amazon Cognito. Cognito processes the credentials and issues account identity and access tokens. FareWorth uses the Cognito subject and access token to identify the signed-in account and authorise encrypted network requests to FareWorth account and history APIs.
To register and authorise a copy of FareWorth, the app processes a generated registration-instance identifier, the canonical FareWorth installation ID and app version. FareWorth account operations return account status, installation ownership and activation information. The app also requests an Access Lease containing the installation and account authority, decision, revision and validity timestamps used to allow or block current product access.
FareWorth may also process your country of operation and Primary Working Area: the city, metro or area where you mainly work. It does not have to be where you live. Your selection resolves to a canonical FareWorth working-market identity and effective account context. The search text you enter is not saved as the market identity. Working Market information may be used for onboarding, personal analytics and market coverage. Future aggregated FareWorth Network Intelligence is not currently live.
Remote Driver Day history
After product access is authorised, Dashboard, Analytics and History can make authenticated read requests for verified remote Driver Day summaries and content associated with the signed-in account and installation. Remote history may contain structured economic and operational records such as Driver Day and session timing, offer and journey counts and outcomes, fares, calculated values, capture results, app/schema versions, working-market context and pseudonymous installation and record identifiers.
Remote responses are validated before display. Verified remote history may be cached on the device using AES-GCM encryption with keys held by Android Keystore. FareWorth keeps local Android history and remote history distinct and labels remote data as cloud history in the relevant views.
After product access is authorised, the app can automatically select eligible completed local Driver Day records on a bounded foreground schedule and sync them to FareWorth services using encrypted, authenticated network requests. The sync contains structured operational and economic information, including installation and app context; Driver Day, currency and online-session data; offer timestamps, platform, service and economic values; pickup and trip time and distance; fuel, after-fuel, profitability and guidance values; completed-journey information; and aggregates and counts.
Local Android history and remote Driver Day history remain distinct data stores. Dashboard, Analytics and History may read remote history associated with the authenticated account and installation. Driver Day sync does not upload live offer screenshots, raw Accessibility text, raw OCR output, passenger names, pickup or dropoff street addresses, GPS trails or driver-platform credentials as payload fields.
Android backup and device transfer
FareWorth's Android backup rules include driver settings and the stored Accessibility disclosure-consent version. Depending on Android, Google account and device settings, Android cloud backup or device transfer may copy those preferences off the device. FareWorth's local history database and encrypted remote-history cache are not included by the submitted app's explicit backup rules.
Diagnostic tools
Limited-release builds may contain diagnostic and parser-fixture tools used by registered customers with authorised product access. Those tools upload diagnostic information only after the customer explicitly chooses to capture or send a diagnostic sample. The public Google Play flavour does not contain FareWorth's private diagnostic upload receiver credential.
Website account registration
FareWorth does not currently collect account registrations through this website unless the reviewed registration gate has been explicitly enabled. When registration is enabled, the form collects an email address, country, optional city or region, Android device model, optional Android version, driver platforms used, and account contact or diagnostic-sample preferences.
This information is used to create and continue a customer account, prioritise market and platform validation, and communicate operational participation. Registration does not guarantee immediate support for a market or platform.
FareWorth will not sell registration data. Any later request for screenshots or privacy-safe diagnostic samples would be separate and based on the customer's explicit choice.
Support reports and diagnostic information
If you choose Report a problem in FareWorth, you can send FareWorth Support a short description together with a bounded diagnostic attachment after confirming that you want to include diagnostic information.
The diagnostic attachment is a structured troubleshooting copy covering the exact last 60 minutes frozen when you enter the Report a problem flow. It may include information such as offer economics, capture timing and outcomes, online-session timing, sanitised lifecycle and completion information, and bounded app or device technical information.
The diagnostic attachment is designed not to include passenger names, pickup or destination addresses, GPS data, raw OCR text, screenshots, passwords, password-setup or security codes, authentication tokens, installation secrets or reusable upload secrets. Please do not include passwords, security codes or passenger personal information in the problem description you type.
Your report is associated with your authenticated FareWorth account and the verified FareWorth installation involved so that Support can investigate the problem.
FareWorth keeps the diagnostic attachment for up to 30 days from the time the server accepts the report, unless it is deleted earlier. The diagnostic attachment is a temporary, nonauthoritative troubleshooting copy. It is not the source of truth for your FareWorth offer history, journey history, Driver Day records, analytics, personal intelligence or network intelligence. Deleting or expiring the Support attachment does not delete or shorten the retention of those underlying records, which are governed separately.
A request to delete your FareWorth account or personal data is a separate process governed by FareWorth's account-deletion and privacy rules.
Diagnostic reports are sent over encrypted connections and stored in private FareWorth cloud systems with access restricted to authorised operational or Support use. FareWorth does not place a reusable cloud-storage or upload credential in the Android app for this Support flow.
Website analytics and campaign measurement
FareWorth uses Google Analytics 4 on this website only after you choose Accept analytics. Before that choice, FareWorth does not load the Google Analytics script or send Google an analytics request or consent ping. Rejecting analytics does not affect registration, sign-in, account continuation, Dashboard, Support, the Google Play handoff or normal navigation.
When enabled, analytics measures sanitised page visits, reviewed acquisition campaign identifiers and a small allowlist of website funnel actions. FareWorth does not send form values, names, email addresses, account or installation identifiers, working market, driver metrics, fares, journeys, dashboard values, Support content or references, tokens, payment identifiers, passenger data, addresses, GPS, OCR text, free text or promo codes to Google Analytics. FareWorth does not set a Google Analytics user ID or user properties.
Google may process browser, device, coarse location, page and campaign information as FareWorth's analytics provider. FareWorth disables Google signals, advertising personalisation and ad storage, does not link Google Ads, and limits Google Analytics cookie persistence to 180 days. You can reject, change or withdraw consent at any time. See Cookie information.
Google operates servers in multiple countries, so Google Analytics information may be processed on Google servers outside the UK. Where that processing involves a restricted international transfer, the applicable Google data protection terms provide recognised safeguards, such as adequacy mechanisms or standard contractual clauses, as applicable. Read Google's privacy policy and data protection terms.
Service providers, data sharing and sale
FareWorth uses Amazon Web Services, including Amazon Cognito and hosted FareWorth API and storage infrastructure, to provide authentication, account, installation, access-authority and remote-history services. These services process the information needed to perform those operations on FareWorth's behalf.
FareWorth uses the bundled Google ML Kit text-recognition SDK. Google states that ML Kit processes input images, text and results on-device and does not send that input or output to Google. Google also states that ML Kit may send device and app information, per-installation identifiers, performance and API configuration metrics, feature input/output sizes, feature versions, event types and error codes to Google over HTTPS for diagnostics and usage analytics.
FareWorth does not sell user data, provide advertisers with FareWorth history, or use ML Kit's operational metrics for advertising. Website registration data, if that reviewed gate is enabled, will not be sold.
Retention and deletion
Local FareWorth history remains on your device until you clear it in the app, clear app data, or uninstall FareWorth. The app includes a Clear FareWorth history control for locally stored history and analytics.
Account, installation, Access Lease and remote Driver Day records are administered separately from local history. Current authoritative remote Driver Day records do not have an automatic expiry in the controlled service. A replaced, non-current technical Driver Day object becomes eligible for coordinated cleanup after 30 days; this does not delete the current authoritative Driver Day record.
The current controlled release does not expose a self-service account deletion or data-export flow. For access, correction or deletion questions about account or remote information, contact privacy@fareworth.app. Unlinking an installation does not itself delete local Android history or authoritative remote Driver Day history. Android/Google controls the lifecycle of copies created through Android cloud backup or device transfer.
Security
We aim to minimise the data FareWorth processes and to keep live analysis local wherever practical. No software can guarantee absolute security, and users should keep Android and FareWorth updated. Private account APIs require authenticated access, and administrative account operations are authorised by the FareWorth service rather than by whether an admin page is visible in a browser.
Children
FareWorth is intended for working drivers and is not designed for children.
Contact
For privacy questions, contact support@fareworth.app.
Changes
We may update this policy as FareWorth adds features. The current version will be published at fareworth.app/privacy/.