FareWrangler — Privacy Policy

Last updated: October 14, 2026

This policy explains what the FareWrangler apps for Android and for iPhone do with information. They are made by Billet Studios, LLC ("we", "us"). Where the two apps differ, it says which one. "iPhone" below also means an iPad running the iPhone app.

The short version

• FareWrangler reads the offer card that Uber, Lyft or DoorDash shows on your screen (on an iPhone: Uber or Lyft), works out your real dollars-per-hour, and tells you by voice and an on-screen badge (on an iPhone, a banner). On Android, if you switch on Amazon Flex blocks, it also reads a Flex block's details screen and shows that block's dollars-per-hour.
• It keeps a record of each offer on your phone — the numbers, the time, a picture of the card and, on Android if you allow location, where you were — so it can show your ride log, insights, hotspots and map. We never receive that record. There is no FareWrangler server and no account.
• Two things are looked up online through services you already use: the area of a pickup or drop-off (your device's built-in address lookup: Google's on most Android phones, Apple's on an iPhone or iPad) and map tiles (OpenStreetMap on Android, Apple Maps on an iPhone or iPad). Details below.
• Anything else leaves your phone only when you send it — a report, an export, a share with a driving partner — or when your own devices sync with each other, directly, over your Wi-Fi.
• No analytics, no advertising, no tracking. It never taps, accepts, declines or acts inside your driver app.

1. What FareWrangler reads

• The offer card on your screen — Android (Accessibility service). When an offer appears in a supported driver app, FareWrangler captures the screen and reads the card's text on the phone: pay, time, distance and the type of offer. The card can also show pickup and drop-off addresses.
• The offer card on your screen — iPhone (screen broadcast). iOS does not let one app look inside another, so you start a screen broadcast with FareWrangler's Start reading button, and iOS shows its red indicator for as long as it runs. While it runs, iOS hands FareWrangler every frame of your screen, whichever app is showing. FareWrangler reads each frame on the iPhone with Apple's built-in text recognition, looks for an offer card or a driver app's banner, and drops the frame. Frames are never uploaded. What is kept is listed in section 2. The card can also show pickup and drop-off addresses.
• Amazon Flex (Android; optional, off unless you switch on Amazon Flex blocks). FareWrangler reads the text of a block's details screen through the same Accessibility service — the window, the pay, the day — with no screenshot, shows that block's dollars-per-hour, and keeps nothing.
• Driver-app notifications — Android (notification access, optional). If you turn on reservation alerts or Amazon Flex blocks, FareWrangler looks at notifications posted by the supported driver apps — never any other app's — to recognise a reservation, scheduled-ride or reserved-block offer and alert you.
• Driver-app banners — iPhone. An iPhone does not let any app read another app's notifications, and FareWrangler does not try. When an Uber or Lyft reservation banner crosses your screen while the broadcast is running, FareWrangler reads it from the picture of the screen, as it reads the rest of the frame. It ignores every other app's notifications.
• Your location — Android (optional). Only if you allow it, and only at the moment an offer is being read (the phone's last known position). Never in the background; FareWrangler does not request background location.
• Your location — iPhone. None. The iPhone app does not ask for your location and records none when it reads an offer.
• The camera — iPhone (optional). Only to scan the pairing code that one of your other devices, or a driving partner's phone, shows. It records nothing: no photo and no video.
• A screenshot you pick — iPhone. Read a screenshot (Settings > Advanced settings > Reader) opens the iPhone's own picture picker. FareWrangler gets only the picture you pick, never your photo library.

2. What it keeps on your phone

All of this lives in FareWrangler's own storage on your phone. Uninstalling the app deletes it (on an iPhone, see "Backups" in section 7 for copies in a backup).

• Ride log — for each offer: date and time, platform, pay, minutes, distance, dollars-per-hour, whether it cleared your line, the offer type, the merchant for deliveries and, on Android, your location if you allowed it. A ride the iPhone reads itself has no location; a ride that came from your Android phone keeps the position that phone recorded.
• Card pictures — a picture of each offer card. Nothing around the card is kept: the picture is cropped to the card, or shows the card on a small margin painted one plain colour (your choice in Settings > Advanced settings > Saved cards & storage). The card itself is kept as shown, which can include the rider's pickup and drop-off addresses. You choose how long pictures are kept there (older ones are then deleted automatically). On Android, if you pick a folder for your cards, copies are also written to that folder.
• Areas — the town and an approximate position for each pickup (and for where you were), worked out from the card and used by Hotspots and Map.
• Driver-app notification log — Android — the most recent notifications from the supported driver apps (up to about a thousand lines), kept so the reservation alerts can be tuned from real wording.
• Driver-app banner log — iPhone — the words (title and text) of the Uber and Lyft banners the reader saw on your screen, the most recent few hundred lines (about 64 KB), kept so the reservation alerts can be tuned from real wording.
• Diagnostics — app health events, crash details, and, if a rate looks wrong, a stripped-down record of what the reader saw (numbers and the reader's own keywords only; street names and rider names are removed before it is written). On an iPhone that includes the reader's run history (when each run started and stopped, and how many frames and reads it had) and its short logs, each kept under about 64 KB.
• Pairing keys — iPhone. If you pair devices, the keys are kept in the iPhone's Keychain, marked for this iPhone only.

3. What leaves your phone, and when

Automatically, to services you already use:

• Address lookup. To name the area of a pickup or drop-off, FareWrangler passes the address lines from the saved card — and, on Android, if you allowed location, your position — to the device's built-in address lookup, which returns a town and approximate coordinates. On Android that is the Geocoder, on most phones a Google service; on an iPhone or iPad it is Apple's geocoder, and FareWrangler also gives it a rough search area, a circle about 100 miles in radius around where you drive (centred on the position stored with that ride when it has one, such as a ride that came from your Android phone, and otherwise on the middle of the places already found), so that a street name is looked up in the right town. We do not receive this; Google's or Apple's privacy policy governs it.
• Map tiles. When you open the Map, its background is downloaded from OpenStreetMap's servers on Android, or from Apple Maps on an iPhone or iPad, which reveals the map area you are viewing to that provider. No name or identifier of yours is attached.

Between your own devices, and a driving partner's phone, over your Wi-Fi:

• Sync and partner pairing. If you pair two of your own devices, or your phone with a driving partner's, with a code, they swap ride data directly with each other on the same Wi-Fi or hotspot, encrypted with a key that only the pairing code gave them. It does not go through the internet or any server of ours. While FareWrangler is running it looks for its paired devices on the local network and announces itself there under a random number, never your name; only a device you paired can connect. Between your own devices that carries your rides, map spots, reservation history and, if you choose, saved card pictures. With a partner it carries ride numbers and pickup areas only, as described under "A share with a driving partner" below. On an iPhone this is why FareWrangler asks for the camera (to scan the code) and the local network.

Only when you choose to send it:

• A problem or misread report. Shown to you in full first. It contains your app and phone version, the settings that shape how offers are read, recent app health events (on an iPhone, the reader's recent runs and its log), any crash report, your last few logged offers without locations, and the stripped-down reader records described above. A switch lets you also add the newest saved card pictures, which can show a rider's pickup place, and the driver-app notification or banner log with its words reduced to numbers and the app's own words; it is off every time the screen opens. If you email it to us, we use it only to fix the problem, and delete it on request.
• Exports and backups you make from the Ride Log or Settings, which go wherever you send them.
• A share with a driving partner (Drive with a partner): your ride numbers and pickup areas — locations rounded to about a block, no drop-off locations, no card pictures — as a file you send yourself, or directly to a paired partner's phone as described above.
• Purchases are handled by Google Play on Android and by the App Store on an iPhone; we never see your payment details.

4. What FareWrangler does not do

• It does not upload your ride log, card pictures, notifications or location to us or anyone else.
• It does not perform actions in your driver app. It never taps, accepts, declines or swipes. The reservation alert's Open button only brings the driver app to the front, the same as tapping that app's own notification; on Android, with the duplicate-clearing option on, it may dismiss earlier copies of the same offer from your notification shade, never a different offer.
• It contains no analytics, advertising or tracking SDKs, and no third-party crash reporting.
• It does not ask you to sign up, and it does not ask for your phone number, email or any rideshare login. The one name it asks for is a first name you choose for Drive with a partner, which labels your rides on your partner's phone.
• It is not affiliated with, endorsed by, or connected to Uber, Lyft, DoorDash or Amazon.

5. Permissions and why

On Android:

• Accessibility service — to read the offer card on your screen, hands-free, while you drive.
• Notification access (optional) — to recognise reservation offers in the driver apps' notifications.
• Display over other apps (optional) — only for the reservation alert's Open / Dismiss bar. The rate badge does not use it.
• Full-screen notifications — so a reservation alarm can open its page over a locked phone.
• Location (optional) — while an offer is being read, for the map and hotspots.
• Notifications, foreground service and battery exemption — to keep the reader running during a shift, show its status, and alert you if the phone switches it off.

You can revoke any of these in your phone's Settings. The reader stops if Accessibility is turned off; reservation alerts stop if notification access is turned off.

On an iPhone:

• Screen broadcast — you start it yourself with Start reading, each time, and stop it from the red indicator or Control Center. It lets FareWrangler read the offer card while you drive.
• Notifications — so FareWrangler can show the rate banner and the reservation alerts. It posts them itself, and marks them Time Sensitive so that a Focus such as Driving can let them through.
• Camera (optional) — to scan a pairing code. Nothing is recorded.
• Local network (optional) — to find your other devices, and a partner's phone, on the same Wi-Fi or hotspot.

The iPhone app does not ask for your location, contacts, photo library or microphone. You can revoke any of the permissions above in your iPhone's Settings. The reader stops when the broadcast ends. An iPhone has no notification access, so reservation alerts work only while the reader is running.

6. Children

FareWrangler is a tool for working drivers and is not directed to children under 13 (or the minimum age in your jurisdiction).

7. Your choices

• Stop reading: on Android, turn off the Read offers switch, or the Accessibility service, or uninstall. On an iPhone, stop the broadcast (from the red indicator or Control Center), turn off Read offers, or delete the app.
• Delete your data: on Android, uninstall the app, or clear its storage (your phone's Settings > Apps > FareWrangler > Storage > Clear data). On an iPhone, delete the app (Settings > General > iPhone Storage > FareWrangler > Delete App). Either removes everything FareWrangler stored; copies in a folder you chose, a file you exported and any card samples saved to your Download folder (Android) stay until you delete them. Card pictures can also be aged out automatically in Settings > Advanced settings > Saved cards & storage.
• Backups (iPhone): FareWrangler does not leave its data out of iPhone backups. If you back up your iPhone, to iCloud or to a computer, the ride log and the saved card pictures are in that backup, as most apps' data is. We never see your backups. Deleting the app does not delete an earlier backup. The pairing keys are the one thing that does not move to a different iPhone: they are marked for this iPhone only, so a new iPhone pairs again. You can leave FareWrangler out of your iCloud backup in your iPhone's iCloud settings.
• Questions or requests: support@farewrangler.com. We hold nothing about you unless you have sent us a report.

8. Changes

If this policy changes, the new version is posted at this address with a new "Last updated" date.

9. Contact

Billet Studios, LLC — support@farewrangler.com