Privacy Policy

FareWise is an independent driver-assistant app. It is not a rideshare company, delivery company, or payment processor. It is not affiliated with, endorsed by, or sponsored by Uber, Lyft, DoorDash, Uber Eats, Grubhub, Instacart, Careem, DiDi, Talabat, inDrive, Apple (except as the App Store distributor), or any other gig-economy platform (collectively, “Platforms”).

Controller / operator: Adam Nassef, doing business as FareWise. Contact: farewisedev@gmail.com.

FareWise is a calculator. You set earning conditions (for example a per-mile and per-hour floor, plus your costs). You voluntarily start an iOS Broadcast session with FareWise’s capture extension. You then choose what sits on the screen. The extension reads payout, time, and distance when those figures appear, scores them against the conditions you set, and posts a local notification with a verdict. You decide whether to accept or decline in whichever app you were using. FareWise does not tap buttons, log into third-party services, call their APIs, or act on your accounts.

Named gig apps on the first-run “who do you drive for” screen are optional and conversational. That choice is not used to limit capture or scoring. Apps that are not on the list still work if they show the same kind of numbers.

This is the part Apple, Platforms, and you should care about most.

What is captured

iOS Broadcast captures whatever is on your screen while the session is running — not only the gig app. If you switch to Messages, banking, photos, maps, or anything else, those pixels can pass through the capture pipeline. FareWise is built to look for offer-style figures (payout, distance, time). It is not a general-purpose screen recorder, and it does not keep a video of your shift. You choose which app is in the foreground.

What happens to a frame

• Frames are processed on your device, in memory, by FareWise’s broadcast-upload extension.
• We run on-device text recognition (OCR) and lightweight image analysis to decide whether a frame looks like an offer.
• We do not save screen frames, screenshots, or video to disk, iCloud, Photos, or any server of ours.
• We do not upload or share frames with FareWise, with Platforms, or with anyone else.
• When a frame is no longer needed for the current recognition pass, it is discarded.

App audio (not the microphone)

ReplayKit can deliver the recorded apps’ audio along with video. FareWise may inspect that audio in memory (for example, loudness) to help notice an offer chime. We do not record the room. The system Broadcast picker is configured without a microphone toggle. Microphone sample buffers, if iOS ever delivers them, are ignored. We do not store, upload, or play back captured audio.

Your responsibility while capturing

You start and stop Broadcast yourself. Do not share your screen if you are unwilling to have on-screen content processed on-device. Hide or leave apps that show secrets you do not want read. FareWise cannot promise that non-offer content never appears in a buffer we briefly inspect.

Platform risk is yours. Some Platforms restrict third-party tools, overlays, or screen recording. FareWise does not obtain, and cannot obtain, permission from those companies on your behalf. Account warnings, deactivation, suspension, or bans — and lost earnings — are addressed in the Terms of Use. This Policy does not make FareWise responsible for those outcomes.

FareWise does not require a FareWise account, email, or password. There is no FareWise user database of drivers. What exists is described below.

4.1 Information you enter

During onboarding and in Profile / Costs, you may provide:

• A display name
• How you work (car, electric vehicle, bike/scooter) and vehicle year, make, model, trim, and economy figures
• Cost inputs (for example financing, insurance, fuel or electricity prices)
• Offer goals (per-mile and per-hour thresholds) and an optional weekly earnings goal
• Which apps you drive for (optional; stored so onboarding can feel personal. Capture does not use this list.)
• Preferences such as appearance (light/dark/system), distance units, and whether you have finished the in-app tour

This is stored in a local database on your iPhone (Apple’s SwiftData / SQLite). It is used to personalize the App and to run cost and verdict math. It is not uploaded to a FareWise server. If iCloud is enabled for this App, Apple mirrors that private database to your iCloud account as described in Section 4.10.

4.2 Offer-related content extracted from the screen

If recognition succeeds, we may derive values such as payout, distance, duration, a Platform label, pickup or drop-off text that appeared on the card, a rider name if the navigation screen showed one, and FareWise’s verdict. Those values may appear in a local notification on your device. The App also keeps a history of offers, rides, and shifts on the phone so Home, Insights, and Costs can show your own numbers.

While you are capturing, those events are first appended to a small on-device journal, then folded into the same local database. We do not sell this content. We do not send it to FareWise servers (the App has none for this purpose). If iCloud is on, Apple syncs that history as part of your private CloudKit database (Section 4.10).

Apple’s privacy nutrition label for FareWise lists this category as “Other User Content,” used for App Functionality, not tracking.

4.3 Notifications

If you grant notification permission, FareWise posts banners and Notification Center items locally (offer verdicts and related shift messages). Notification delivery is performed by iOS. We do not use notifications to advertise third-party products. You can disable notifications in iOS Settings; the capture extension may still read the screen, but you will not be alerted.

4.4 Purchases

Access to FareWise is sold as auto-renewable subscriptions through Apple In-App Purchase / StoreKit (weekly, monthly, or annual; monthly and annual include a 5-day free trial). Apple processes the payment. Card data stays with Apple. Apple’s privacy policy governs payment data: apple.com/legal/privacy.

We use RevenueCat as the subscription backend, alongside StoreKit. The SDK is configured with our Apple public key. We alias RevenueCat’s anonymous ID to our opaque CloudKit user UUID — not your name, email, or Apple ID string. RevenueCat may process: that opaque app user ID; product IDs (FareWise_Weekly / FareWise_Monthly / FareWise_Annual); entitlement, trial, and renewal status; App Store transaction identifiers; and ordinary SDK device / OS / IP metadata they need to run subscriptions. They do not receive screen frames, offer history, or vehicle costs. RevenueCat’s policy: revenuecat.com/privacy.

Apple’s privacy nutrition label lists “Purchase History” and “User ID” for App Functionality (restoring and unlocking FareWise), not tracking.

4.5 Vehicle image request (optional network call)

If you pick a car, the App may request a studio-style image from a third-party vehicle-image service (currently carimagesapi.com) by sending make, model, year, and a requested image width — not your name, not your location, not your offer history. If the request fails, the App shows a silhouette. You can use FareWise without a successful image load.

4.6 Website

If you visit farewise.dev, the host and any content-delivery network may log standard technical data (IP address, browser type, date/time, referring URL, pages requested). We do not use the site to run advertising pixels or to track you across other companies’ apps. Do not send sensitive personal data in a support email unless needed to help you.

4.7 Diagnostics that stay on the device

The capture extension may write unified logs on the device (for example that a broadcast started or finished). FareWise does not operate a crash-analytics or telemetry backend. If you later choose to send Apple a sysdiagnose or similar, that is your choice and Apple’s processing.

4.8 Referrals

If you invite another driver, FareWise stores an opaque user ID and a short referral code in iCloud (private identity, public code lookup). No name, email, or Apple ID string is stored in those records. A Cloudflare Worker we operate (farewise-referrals.ayhnassef.workers.dev) receives RevenueCat webhook events (initial_purchase, renewal, product_change, transfer) so a reward is created only after Apple is actually paid — not when a free trial starts. The worker may receive an opaque FareWise user ID, a redeem secret, and a transaction ID. It does not receive your name, email, offer history, or screen content. Delete all data removes your driving history and profile, not your invite identity, so reinstalling cannot mint extra rewards.

Apple’s privacy nutrition label lists “User ID” for that opaque identifier, used for App Functionality, not tracking.

4.9 In-progress ride cache

While a broadcast is running, the capture extension may keep a short-lived local file of the ride in progress (so stopping capture to take a call does not orphan the trip). That cache is not synced to iCloud and expires after a few hours.

4.10 iCloud (CloudKit) — your private database, not a FareWise account

There is still no FareWise login. When iCloud is turned on for this App, Apple’s CloudKit copies your private FareWise database — profile, costs, goals, preferences, and offer / ride / shift history — to iCloud under your Apple ID. FareWise cannot browse other drivers’ databases. Storage counts against your iCloud quota, not a FareWise server. Sync needs a network; capture and scoring keep working offline on the phone.

Debug builds and App Store / TestFlight builds use Apple’s Development and Production CloudKit environments respectively. Records written in one are not visible in the other.

You can also manage iCloud data in iOS Settings → [your name] → iCloud. Signing out of iCloud on a device stops new mirroring from that device; copies already on other devices you own may remain until you delete them there or use Delete all data (Section 9).

FareWise is not designed to collect or request:

• A FareWise login, password, or government ID
• Platform usernames, passwords, session cookies, or API tokens
• Precise or coarse location (the App does not use location services; any maps in onboarding are demonstration graphics)
• Microphone recordings of you or your vehicle
• Camera, Contacts, Calendar, Health, or Motion permission
• Advertising identifiers (IDFA) or App Tracking Transparency prompts — we do not track you across other companies’ apps or websites
• Analytics, attribution, or crash-reporting SDK data sent to FareWise
• Screen recordings stored as files

Our privacy manifest declares NSPrivacyTracking as false and lists no tracking domains.

We use the information described above only to:

• Provide App functionality: onboarding, verdicts, costs, offer history, preferences, subscriptions, and iCloud restore across your devices
• Verify subscription, trial, and restore status, and run referral rewards after a paid conversion
• Show a vehicle image if you selected a car
• Respond to support requests you send us
• Comply with law, enforce the Terms of Use, or protect rights, safety, and integrity
• Improve the App based on feedback you choose to give — not based on silent behavioral tracking

We do not sell personal information. We do not use your data to train public AI models. We do not serve third-party ads in the App.

We do not sell, rent, or trade your information. We share information only as follows:

• Apple. iOS, the App Store, StoreKit, notifications, Broadcast, and iCloud / CloudKit are Apple systems. Your private FareWise database and referral records are stored and synced by Apple under Apple’s terms and privacy policy. FareWise does not receive a copy of your offer history on our own servers.
• RevenueCat. Subscription and entitlement processor, as described in Section 4.4. We do not share driving history, screen frames, or vehicle costs with them.
• Cloudflare. Hosts the referral worker described in Section 4.8. We do not share driving history with them.
• Vehicle-image provider. Make, model, year, and size, as described above.
• Service providers who host farewise.dev or our email, solely to operate the site and support inbox, under an obligation to use the data only for that work.
• Legal. If required by law, regulation, legal process, or government request, or to protect FareWise, users, or the public from harm, fraud, or abuse.
• Business transfer. If FareWise is merged, sold, or transferred, information reasonably necessary to continue the Services may transfer, still bound by this Policy or a successor notice.
• With your direction. If you email us a screenshot or logs, that is you sharing, not the App uploading.

We do not share your information with Uber, Lyft, DoorDash, or other Platforms. They may still observe that you are using screen recording or a third-party tool through their own apps, devices, or policies. That is outside FareWise’s control.

Platforms have their own terms, community guidelines, and privacy policies. FareWise does not control them. Using FareWise does not change your contract with a third-party service. Read the Terms of Use before you broadcast a screen that shows someone else’s app.

Subscription status is also processed by RevenueCat and, for referral rewards after a paid conversion, by the Cloudflare Worker we operate. Those parties do not receive your offer history or screen content. Their processing is described in Sections 4.4 and 4.8. RevenueCat’s privacy policy: revenuecat.com/privacy.

Links in the App (Privacy, Terms, Support, manage subscriptions) open Apple or FareWise pages. External sites are not governed by this Policy.

Profile, costs, goals, preferences, and offer history remain on the device (and in your iCloud private database, if sync is on) until you delete them or remove the App.

In Profile, Delete all data wipes FareWise’s local database, capture journal, scoring snapshot, and related settings on that iPhone, and queues deletion of the mirrored CloudKit copy of that driving data. You return to onboarding. That is the complete “delete my driving data” path because there is no FareWise account to close. Invite identity (Section 4.8) is kept on purpose so a reinstall cannot mint extra rewards.

Deleting App data or the App does not cancel an App Store subscription. Manage or cancel in iOS Settings → your name → Subscriptions, or at apps.apple.com/account/subscriptions. Apple may retain purchase records as their policies require.

Support emails we receive are kept only as long as needed to handle the request and ordinary record-keeping, then deleted or archived in the ordinary course.

Uninstalling the App removes the App’s local data from that device (subject to iOS backups you control). If iCloud sync was on, a copy may remain in iCloud until Delete all data has synced, or until you remove FareWise data from iCloud in iOS Settings. Restoring a backup or signing into the same Apple ID on a new phone may bring FareWise data back.

We design the App so the sensitive work — screen frames — never leaves the device and is not written out as a recording. Your database sits in iOS storage and, if you use iCloud, in Apple’s CloudKit private database for your Apple ID. No method of transmission or storage is perfectly secure. You are responsible for the physical security of your iPhone, passcode, Face ID / Touch ID, who can start Broadcast on your device, and who can unlock your iCloud account.

The App is for adults who are legally allowed to drive or deliver on Platforms (typically 18+). It is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe we have, email farewisedev@gmail.com and we will delete it.

Because FareWise does not operate a driver account on our servers, the practical way to access or erase App driving data is on the device: review Profile, Costs, and History, or use Delete all data (which also syncs deletion of the iCloud copy of that data). Uninstalling without Delete all data may leave an iCloud copy.

Depending on where you live, you may have rights to access, correct, delete, or export personal information, to object to or restrict certain processing, and to lodge a complaint with a supervisory authority. For information we actually hold (for example a support email you sent), email farewisedev@gmail.com. We will not discriminate against you for exercising rights.

California (CCPA / CPRA)

We do not sell personal information and we do not share it for cross-context behavioral advertising. We do not use sensitive personal information for purposes that require a right to limit under CPRA beyond providing the App you requested. Categories of information are those in Section 4. Sources: you, your device, Apple, RevenueCat, and (for car images) the image API. Business purposes: App Functionality and support. Retention: Section 9.

EEA / UK / Switzerland

Where GDPR or UK GDPR applies to a given processing activity, we process on-device data and your iCloud-backed private database because you asked us to provide the App (contract / requested service) and, where needed, our legitimate interests in operating a secure product and responding to you. Vehicle-image requests are part of the vehicle-setup feature you chose to use. RevenueCat processes subscription identifiers as described in Section 4.4 because you asked us to provide paid access. The referral worker processes webhook events as described in Section 4.8. iCloud sync is Apple’s processing under Apple’s terms when you are signed into iCloud. You may withdraw consent for optional notifications in iOS Settings.

Do Not Track / ATT

The App does not track you across third-party apps or websites for advertising. There is no App Tracking Transparency prompt because we do not request permission to track.

The App’s core processing is on your iPhone, wherever you are. Apple, RevenueCat, Cloudflare, our website host, email provider, and the vehicle-image API may process data in the United States or other countries. iCloud data is processed by Apple according to Apple’s policies. RevenueCat’s processing is governed by their privacy policy. Those countries may have different data-protection laws than your own. By using the Services you understand that this can occur, subject to applicable law.

We may update this Policy. The “Last updated” date will change. Material changes will be posted at farewise.dev/privacy and, where required, noted in the App. Continued use after the effective date of a change is acceptance of the revised Policy.

Privacy questions, deletion requests for information we hold off-device, and complaints: farewisedev@gmail.com.

Support: farewise.dev/support
Terms of Use: farewise.dev/terms

© 2026 FareWise. Independent driver software. Not affiliated with Uber, Lyft, DoorDash, or any other gig platform.