1. Local-first handling
WheelWage does not require a username/password WheelWage account and does not upload your work records to its entitlement service. Location records, offers, earnings, expenses, vehicles, and retained receipts are kept in Android app-private storage unless you choose to export them. Saved records, expenses, tax-oriented records, and exports remain available without Offer Reader; new offer analysis and new shifts require current Pro access and Offer Reader consent.
Limited paid-access verification data, Google component data, ordinary network metadata, and geocoding requests can be processed off-device as described below, so WheelWage is not a fully offline or zero-telemetry product.
2. Location and mileage tracking
WheelWage accesses precise device location to calculate mileage during an active tracking session.
- After paid access and required setup are complete, and after you review and acknowledge the location disclosure, Track all driving is enabled by default. You can turn it off in Settings, and an explicit opt-out is preserved. While it is enabled, the location foreground service can continue while the app is minimized or the screen is locked.
- A standard calculated-offer popup may show Start mileage when paid access and setup are ready. Tapping it opens WheelWage; only after WheelWage is visibly resumed does the app start location tracking. Displaying or calculating an offer never starts tracking by itself.
- An ongoing private notification identifies WheelWage mileage tracking and provides a Stop tracking action.
- During an active, consented tracking session, a visible Walmart Spark offer may trigger one current precise-location fix to estimate travel from the device’s current location to the offer’s store.
- WheelWage does not use an accessibility event, calculated-offer popup, charging, Bluetooth, or activity-recognition event to silently start location tracking in this release.
Mileage totals and timestamps are stored locally. Exact route history is optional, off by default, and not required for mileage tracking. If you enable Settings → Save exact route history, WheelWage stores precise coordinates, times, accuracy, and speed for future confirmed vehicle movement. Turning route history off requires confirmation, deletes saved route points, and prevents new route points from being retained while preserving mileage totals, classifications, deductions, and trip times.
3. Offer Reader
Offer Reader must be enabled before a new shift can start. It must be separately enabled in Android Accessibility settings after WheelWage shows its prominent in-app disclosure and you agree. If the service is enabled directly in Android settings without current in-app consent, it disables itself before inspecting an accessibility event or app window. If you decline or revoke it, you can continue using non-shift tools and finish or recover an already-authorized shift, but WheelWage blocks new offer analysis and new shifts until access is restored.
When enabled, WheelWage reads offer text that these allow-listed driver apps expose on screen or in offer notifications: Uber Driver, Lyft Driver, DoorDash Dasher, Grubhub for Drivers, Instacart Shopper, Walmart Spark Driver, Amazon Flex, and Amazon Relay. It parses the text locally and extracts facts such as platform, payout, distance, duration, and pickup information to calculate an estimated verdict.
For Uber Driver only, if accessibility text is incomplete, WheelWage may take a temporary screenshot of the Uber Driver screen and process it with on-device OCR. The screenshot is held in memory only for processing and is never saved. WheelWage can observe a narrowly matched Accept or Match click made by you to record your decision. It never taps, accepts, matches, rejects, or declines an offer in a driver app.
Parsed offer facts and your decision may be stored in WheelWage’s private local database. Raw accessibility-node text is discarded after parsing. If you deliberately enable OCR debug text in Privacy controls, sampled text may appear in local device debug logs. WheelWage displays offer UI as an accessibility overlay and does not request Android’s general “display over other apps” permission.
4. Expenses, receipt images, and OCR
WheelWage accesses only receipt images you select through Android’s system picker. Google ML Kit performs text recognition on the device and WheelWage suggests details such as merchant, amount, date, and expense category for you to review.
A selected image is copied into WheelWage’s private storage only when you choose to keep that receipt, when receipt retention is enabled, or when you explicitly attach a receipt to an existing expense. Otherwise, it is used for the current OCR flow and is not retained by WheelWage.
5. Google Play paid access
WheelWage Pro is sold through Google Play as a weekly, monthly, or yearly subscription, or as a non-consumable lifetime purchase. Weekly has no trial. Eligible new monthly and yearly subscription customers may receive a 3-day trial. Google Play handles checkout, localized pricing, trial eligibility, payment details, renewal, cancellation, and refunds. Lifetime is one charge and does not auto-renew. WheelWage does not receive your card or bank-account details.
To verify, restore, transfer, or release Pro access, WheelWage may process a Google Play purchase token and purchase or subscription state; product, base-plan, purchase-option, and offer identifiers; a pseudonymous purchase-lineage value; a derived installation identifier and public key backed by a non-exportable private key; signed request and replay-prevention identifiers; Play Integrity verdict categories; transfer and release timestamps; server timestamps; and ordinary network metadata. Purchase tokens are encrypted at rest. WheelWage does not send work records, offer screenshots or OCR text, mileage, earnings, tax data, gig credentials, email addresses, advertising IDs, or hardware identifiers to its entitlement service.
For a pending Google Play chargeback review, WheelWage’s service may temporarily use Google’s order and review tokens to return a neutral preference without submitting work or usage evidence. Those review tokens are not retained in WheelWage’s database or logs.
6. Google components and geocoding
WheelWage uses Google Play services for fused location and related Android integrations, Google Play Billing and Play Integrity for paid access, and Google ML Kit for on-device text recognition. These Google components may process device, app, network, API-usage, diagnostic, performance, purchase, and—in accordance with device settings—location-related information under Google’s terms.
Google states that ML Kit may transmit device and app information, per-installation identifiers, performance metrics, API configuration, feature input/output sizes, feature versions, event types, and error codes for diagnostics and usage analytics. Google states that this operational data is encrypted in transit and that the bundled text-recognition SDK’s documented collection does not include receipt or Uber screenshot content. See Google’s ML Kit Android data disclosure and Google’s explanation of Play services data.
For a Spark pickup estimate, WheelWage may give your current precise-location fix and a public store or pickup address to Android’s configured geocoder. The geocoder may contact a network service and receive ordinary network metadata such as an IP address. WheelWage does not send your saved route as the geocoding query. A validated public store identity, pickup address, and store coordinate may be cached in app-private storage; that cache does not contain the driver’s location, customer or drop-off addresses, payouts, or route data.
7. Sharing and user-initiated exports
WheelWage does not sell personal or sensitive data, share it for behavioral advertising, or use it to serve ads.
When you request an export, WheelWage creates the file locally and hands it to Android’s system share flow. Tax CSV/PDF files, audit notes, and JSON backups exclude internal app-access and SDK state. Exact route coordinates are excluded by default and are added only when you separately select Include exact route coordinates and accept the warning. You choose the receiving app, person, or service, and that destination’s privacy terms apply after you send the file.
8. Retention and deletion
Local work records remain until you delete them or uninstall WheelWage. You must end an active shift before using Settings → Delete all local work data.
In-app deletion removes trips, mileage logs and route points, offers, expenses, vehicles, odometer readings, retained receipt files, local backup files, export cache files, learned Spark pickup-store records, and saved driver standards from WheelWage’s private storage. Basic app, privacy, and active purchase-verification data remain because deleting work records does not cancel or refund a Google Play purchase.
Request, replay-prevention, notification, diagnostic, and Integrity metadata is scheduled for deletion within about 30 days. Released or inactive installation metadata, and minimum records for terminal purchases, are scheduled for deletion or irreversible anonymization after about 90 days, subject to documented security, chargeback, tax, or legal needs. Release this installation frees the purchase binding but does not cancel a subscription, refund lifetime access, or delete local work records. The deletion control cannot remove files you previously exported, Google Play billing records, or operational data processed independently by Google or a geocoding provider.
Uninstalling WheelWage removes its Android app-private database, files, and preferences, subject to Android’s behavior on the device. WheelWage disables Android cloud backup for its app data. See the support page’s deletion instructions.
9. Security and your choices
WheelWage stores local records in Android app-private storage and limits accessibility events to its declared driver-app package allow-list. You can decline or revoke Accessibility access, continue using non-shift tools, and finish or recover an already-authorized shift; new offer analysis and shifts remain blocked until required Pro and Offer Reader access is restored. You can also stop mileage tracking from the persistent notification, leave exact-route retention off, delete saved route points while keeping mileage records, decline receipt retention, export selected records, release this installation, cancel through Google Play, delete local work data, or uninstall the app.
No security method is perfect. Keep your device and Android security updates current, and review destinations before sharing an export.
10. Changes to this policy
We may update this policy when WheelWage’s features, SDKs, or legal obligations change. The effective date above will be updated when the policy changes.
11. Contact
Privacy questions and requests: support@lakeeffectlogic.com.
Developer: Lake Effect Logic LLC, Buffalo, New York, United States. Product support is available at wheelwage.com/support.