Offer Screener

Privacy Policy

Effective 9 September 2026 · Last updated 9 September 2026

The short version

Offer Screener reads ride offers on your device to help you decide whether to accept them. Those offers never leave your phone. We do not have accounts, we do not use analytics or advertising, and we do not collect your location. Our server does two things: it hands your app updated pattern rules for reading offer screens, and it accepts an anonymous signal when that reading fails. Neither one involves anything that identifies you or your riders.

1. Who we are

Offer Screener is an Android application operated by Casey Vigus. For any privacy question, contact admin@athrides.com.

2. What the app reads on your device

To evaluate an incoming ride offer, the app reads the offer screen displayed by your rideshare app. Depending on what that screen shows, this can include fares, distances, estimated durations, pickup and destination areas, and rider details such as a name, rating, or photograph.

All of this is processed on your device, in memory, for as long as it takes to score the offer. It is not written to our servers, not stored in an account, not sent to any third party, and not retained after the offer is gone. The app is built so that it cannot transmit it.

Some of that information belongs to riders, who are not our users and have not agreed to anything. That is precisely why it stays on your device.

3. What our server actually receives

The app makes two kinds of network request, and no others.

a. Fetching pattern rules

Rideshare apps change their screen layouts. When they do, the rules for reading those screens have to change too. Your app periodically asks our server for the current rules — at most once every six hours. This request is unauthenticated and carries no identifier. It tells us only which platform's rules are wanted, your app version, your language, and a rollout number (see section 5).

b. Reporting that a reading failed

If the app cannot make sense of an offer screen, it may send a short signal so we know a layout has changed and can publish a fix. That signal contains exactly four values and nothing else:

FieldExampleWhat it is
platformuberWhich rideshare app's screen failed to read
profileVersion2.0.9Which version of our rules was in use
appVersion1.4.2Which version of the app you are running
failureKindNO_FARE_MATCHWhich part of the reading failed

Our server rejects any report containing anything beyond these four fields, and it does not write the contents of these reports to its logs. Reports are counted, not stored individually: we keep a daily tally per app version and failure type, never a record of separate events.

4. What we never collect

The following never reaches our servers, is never stored by us, and is never written to our logs:

We do not use analytics services, advertising networks, crash reporters that collect personal data, or tracking of any kind. We do not sell or share personal information, because we do not have any.

5. The rollout number

New pattern rules are released gradually, so that a mistake reaches a few people rather than everyone at once. Doing that normally requires identifying each device. We deliberately do not.

Instead, the first time you open the app it picks a random whole number between 0 and 99 and keeps it on your device. That number is sent when your app asks for rules, so the server can decide whether you are in the current release group. It is not derived from your phone, your account, or anything about you; roughly one in every hundred installations holds the same number. It identifies nobody. It stays the same so that you do not flip back and forth between rule versions.

6. IP addresses

Like any internet service, our server sees the IP address a request arrives from. We use it only, and briefly, to enforce rate limits that protect the service from abuse. IP addresses are not written to our stored logs, are not linked to anything else, and are not retained.

7. Technical logs

We keep basic operational logs for up to 30 days: the time of a request, which URL was called, the response status, how long it took, and which rules version was served. These logs are used to keep the service running and to notice when a rideshare app has changed its layout. They do not contain request contents or IP addresses.

8. Accounts, payments and children

The app currently has no user accounts and no subscriptions, so we hold no account records. If that changes, this policy will be updated before any such feature ships, and the change will be described here.

Offer Screener is a tool for working rideshare drivers and is not directed at children. We do not knowingly collect information from anyone under 18.

9. Where data is processed

Our servers are operated on infrastructure located in the United States and the European Union. Because the app sends us no personal data, no personal data is transferred between countries by using it.

10. Your rights

Privacy laws including the GDPR and the CCPA give you rights to access, correct, delete, or export the personal data a service holds about you, and to complain to a regulator.

We want to be straightforward about how this applies here: we do not hold personal data about you, so in practice there is nothing for us to retrieve or erase. You can remove everything the app keeps — including your rollout number — by uninstalling it or clearing its storage. If you would like to exercise a right or simply ask what we hold, write to admin@athrides.com and we will respond within 30 days.

11. Security

All communication between the app and our servers uses HTTPS. The narrow boundary described in this policy is our main security measure: data we never collect cannot be breached.

12. Changes to this policy

If we change this policy we will update the date at the top of this page. If a change is significant — particularly one that widens what we collect — we will say so clearly in the app before it takes effect.

13. Contact

Questions, requests, or privacy concerns: admin@athrides.com.