Terms of use
Offer Filter terms of use
Beta terms, effective 29 October 2026 · for Offer Filter 0.6.48
What Offer Filter is
Offer Filter is independent software for Android phones. It is not made, endorsed, sponsored or supported by DoorDash, Inc. DoorDash and Dasher are trademarks of DoorDash, Inc., named here only to say which app Offer Filter works with.
Offer Filter is beta software: it is still being tested, it changes often, and it can fail in ways no one has found yet. These terms change with it (see Changes).
By tapping I understand and accept on the app's first screen, you confirm that you understand the acceptance-rate risk below, choose to use Offer Filter at your own risk, and accept these terms. If you do not accept them, do not use the app: tap Not now, turn off its screen reading and notification access, or uninstall it.
Acceptance-rate risk
Automatic declines may dramatically lower your DoorDash acceptance rate. This can affect DoorDash programs that depend on it. You must acknowledge this risk before filtering begins, including after an update that changes the notice. Continuing is your choice, at your own risk; the app makes no promise to preserve your acceptance rate. Autopilot's default goal, pay first, does not try to keep your acceptance rate up. An acceptance-rate goal you choose instead is a best effort, not a promise: Autopilot cannot accept offers for you, and your acceptance rate rises only when you accept offers. An offer you accept yourself can set higher Autopilot working minimums and hold its bar above what the goal allows for the next 24 offers; a newer acceptance replaces those levels and that hold. From 0.6.37, an offer you decline yourself can also raise the bar to just above that offer for the next 24 offers, even during an acceptance's hold, so more offers are declined automatically.
What it does
- Time-aware scoring (from 0.6.46) is optional and starts off, in How offers are judged. It compares the value of retained standalone offers near the current local time with offers overall, using the same current saved and enabled learned rules for every comparison. It can raise or lower a standalone score by at most 25%, and therefore change which offers are declined in either Strict or Area mode, with or without Autopilot. It uses up to the last 200 retained offers from the last 28 days, including declined offers, with more weight on recent days; add-ons, paused observations, skipped stores, apparent misreads and unread scores are excluded. It needs at least 30 eligible offers overall and 12 within 90 minutes of the local time across at least three dates. Until then it uses the normal score. Estimates use medians and are pulled toward no adjustment when evidence is sparse. Updates apply only between offers at the existing safe point. Saved minimums and learned bests are unchanged; the existing hard maximum stops, unknown-fact review, strict add-on checks and separate strict automatic-acceptance checks remain. Autopilot records the adjustment with a personal acceptance so reconstructing its working minimums preserves that acceptance's recorded score. Offer details show the applied factor, sample counts and score before adjustment. Turning the switch off restores scoring without this adjustment and, like a mode change, resets Autopilot's working references and holds. Local history is evidence of past offers, not a forecast or promise about earnings.
- It reads the Dasher app's screen and notifications on your phone, through Android's accessibility service and notification access, which you turn on yourself. With no rule set, it reads nothing of Dasher's screen. While auto-decline is paused (from 0.6.35), it still reads each offer on Dasher's screen and shows its score and what auto-decline would do, and taps nothing; offers read while paused teach no learning and do not count for Autopilot. Turning Offer Filter off in Android's Accessibility settings stops all reading of Dasher's screen.
- It compares each offer with your active minimums: pay per stop, pay per mile and pay per hour of Dasher's time estimate, plus an optional maximum number of stops. Pay per stop (from 0.6.12, when it replaced the minimum pay, keeping its number) is asked for each stop Dasher shows, the pickup included (from 0.6.14): twice for a single order, which Dasher counts as two stops, three times for three stops, four times for four, so $5 a stop asks $10 of a single order and $15 of three stops. When 0.6.14 began counting the pickup, your number was not changed, so a single order asks twice what it did under 0.6.12 and 0.6.13. When an offer's stops are not read, it stays for review unless its pay misses even one stop's worth or another minimum. Area mode is the default (from 0.6.27, and set once then for earlier installs, whose Strict could not be told from the earlier default): stronger pay or rates can compensate for weaker ones in the combined score. Strict mode checks every active minimum; choose it in How offers are judged, the word in the radar's middle on the homepage. Maximum stops remains a hard limit, missing required facts stay for review, and add-ons remain strict. An offer permitted by the filter is not an accepted delivery. When an offer fails the chosen rules, the app can tap Decline and Dasher's confirmation for you. With Decline after 10 seconds on in Settings (from 0.6.35; off unless you turn it on), an offer shown on Dasher's screen while Dasher is in front is declined only once it has shown for 10 seconds, or at once when its countdown has 3 seconds or less left; your touch on the screen or a tap on Dasher in that time leaves it to you. Offers it handles while you are in another app, from Dasher's notification or with Peek, are still declined at once. From 0.6.18 it confirms only a decline question worded as Dasher's usual one ("Are you sure you want to decline this offer?"), seen in the developer's own reports; any other question, or one saying declines are limited or that another decline would end your dash, is left to you and auto-decline pauses until you resume it. An offer already left to you stays yours if you change your rules while it shows; the new rules judge the next offer. Autopilot is on by default (from 0.6.2, and turned on once then for earlier installs), with pay first as its goal (from 0.6.18, when it replaced the suggested acceptance-rate goal of 70%: once, a 70% goal moved to pay first, since it could not be told from the suggested one, and a 50% goal stayed) until you choose a goal that protects your acceptance rate (70% or 50%); you can turn it off from its chip on the homepage. While it is on, Autopilot applies one bar, between 10% and 150% (from 0.6.32; between 50% and 150% before), using your recent offers, how often they come and the acceptance rate Dasher shows when you decline. It initially scales your resolved saved and enabled learned requirements. From 0.6.29, each positively confirmed standalone offer you accept yourself while Autopilot is on sets each readable active working minimum to that offer's own pay per stop, pay per mile or pay per hour, independently up or down. Every stop counts, the pickup included. From 0.6.31 that acceptance also sets a total-pay reference: its own whole pay, never its pay per stop times its stops. In area mode, a quarter of each Autopilot score weighs an offer's total pay against that reference at the current bar (the required pay is a weighted geometric mean, three quarters the rates' requirement and one quarter the reference at the bar), so a bigger offer a little under those rates can pass and a smaller offer at those rates can be declined. Strict mode, automatic acceptance and add-ons do not use it, and no radar spoke shows it. It is replaced and cleared with the working minimums; working minimums saved before 0.6.31 have no reference until your next such acceptance. Unknown or zero denominators do not set that measure; a disabled measure stays disabled, and a known implausible figure rejects the adjustment. Automatic acceptances, add-ons, skipped stores, ambiguous outcomes and offers merely permitted by the filter do not set these minimums. Acceptance learning may be off: Autopilot follows these acceptances separately. The change takes effect between offers at the screen reader's next safe point. From 0.6.40 the shared bar moves at the same time to that offer's own Autopilot score as it showed (held between 10% and 150%), so that offer keeps its score and an offer exactly like it meets the bar exactly; when that score was not worked out (a figure it needs unread), and before 0.6.40, the bar stays where it was and that offer then scores the bar. A standalone offer needs the same either way; add-ons and automatic acceptance, which ask your saved and enabled learned minimums at the bar, follow the bar to its new level. Later bar movements scale the independent working references together. The newest acceptance replaces earlier accepted levels. From 0.6.44, the latest eligible confirmed personal acceptance in the retained decision history determines the working minimums from its recorded numeric rules and offer facts, and holds the bar at its original recorded score for the next 24 counted offers, across dashes; a newer personal decline can hold it higher. The history can repair a missed update or an older incorrectly normalized adjustment at the next safe point, including after an app update or restart, without waiting for another acceptance. A history record must have a confirmed personal acceptance, its original score and numeric rules, and come from filtering with Autopilot on and auto-decline not paused. Merely passing, timing out or disappearing is not an acceptance. Records from before a goal or rules reset cannot restore the old adjustment, and Clear history removes the evidence. Existing decision snapshots are not rewritten, and acceptance learning is not replayed. During that hold, ordinary goal and offer-rate planning cannot move the bar away from the accepted score or a newer personal decline's higher hold. A change of your goal (turning Autopilot on with another goal included), minimums, max stops, mode or learning ends that hold and clears the working adjustments; a pause, turning Autopilot off and on again with the same goal, and Adopt keep them, including an already confirmed pending update. After the 24 offers the hold ends and the usual bar adjustment continues; the independent references remain until replaced or cleared. From 0.6.48 an offer whose pay the app did not read (Dasher's notification alone, or a screen read without its pay) does not count toward the 24 offers of any hold, an accept's or a decline's; it still counts as an offer Dasher sent for the acceptance-rate goal and Autopilot's pass share. From 0.6.37, a standalone offer you decline yourself while Autopilot is on and auto-decline is not paused (a Decline of yours, counted once Dasher goes back to waiting for offers or shows another offer; the app's own declines and an offer left to time out do not count) raises the bar to one point above that offer's Autopilot score, at most 150%, when that is higher, and holds it at least there for the next 24 counted offers, across dashes, even during an acceptance's hold and above what an acceptance goal allows, so offers that score no better are declined. It never lowers the bar and does not change the working minimums. Your next such acceptance replaces it, a decline from before your latest acceptance holds nothing, and the changes that end an acceptance's hold end it too. Add-ons, skipped stores' offers, offers with more stops than your maximum, and offers that look misread or whose pay or a needed figure was not read do not raise it. Autopilot can permit offers below your saved or learned minimums, or decline offers that meet them. Offers it permits only below your saved or learned minimums are left to you and never auto-accepted. Autopilot never changes your saved minimums or learned bests; it changes only its separate working requirements. Turning it off judges offers at exactly the saved and enabled learned minimums again. Acceptance learning keeps its separate best-ever rates. From 0.5.1 to 0.6.20 Autopilot also raised saved minimums, at most 10% at a time, with Let my minimums grow to turn that off; that growth and its switch were removed in 0.6.21. A growth made before 0.6.21 keeps its note on the homepage, with Undo, until you tap it or your minimums change another way. Auto-accept starts off. If you separately enable it in Settings, it can tap Accept on a complete standalone offer that strictly meets every active saved and enabled learned minimum at 100% or any higher Autopilot bar, and also meets Autopilot's independent working minimums wherever they ask more, even in area mode, committing you to that delivery. Automatic acceptance leaves add-ons and unclear offers to you. Add-on filtering stays strict against saved minimums at the current bar; standalone learned floors do not apply to add-ons unless adopted as saved minimums, and independent Autopilot adjustments do not apply to add-ons.
- It also declines a standalone offer from a store you put on your skip list (from an offer's details; Settings → Skipped stores removes one), whatever it pays, when it reads that store's name on Dasher's screen. An offer from two stores is declined when either is on the list; an offer whose store it cannot read is judged by your rules as usual. Store names can be misread. Autopilot can weigh your own cost per mile, off unless you set it in its details.
- Acceptance learning is separate from area mode and Autopilot, and is on by default; the Learn button on the homepage turns it off and on. While filtering and learning are on, each positively confirmed manual standalone acceptance (an offer you accepted yourself, including one you took back from the app's decline before it tapped Dasher's confirmation, when it came while you were waiting for offers) can keep your best accepted pay per stop (an offer with that offer's stops must then pay one cent more than it did, and other numbers of stops in proportion; an acceptance whose stops were not read teaches nothing on pay) and independent exact best pay-per-mile and pay-per-minute rates. When a new best asks more than a saved minimum, it raises the resolved learned requirement, which can mean more declines; Autopilot may apply its separate working adjustment while on. Your saved minimums stay as you set them. A note on the homepage says what rose, with Adopt, which makes those learned minimums your saved ones; OK closes the note. Undo of an adoption is in Learned minimums; it is conditional and cannot overwrite later changes. Readable short trips can teach new highs too: pay per mile needs at least half a mile and pay per minute at least five minutes. With Learn on, the dashed green triangle shows the calculated learned minimums: the higher saved or learned requirement on every active axis. Automatic accepts, declines, add-ons and ambiguous outcomes do not teach it. Unknown facts do not teach their axes; any known implausible figure rejects the lesson. Learned bests can activate an unset money minimum. Off or paused retains learned bests without new learning. Confirmed Reset clears active bests and Undo; prior decision snapshots remain until Clear history. Clear history clears both active learning and that history. Adopt raises only lower saved minimums, which then apply to add-ons too. Reset and Clear history keep your minimums as they are. Learning is local and makes no promise about earnings or future offers.
- If Dasher reports an error after that first Decline and leaves a recognized empty or map-only screen, it can press Back and retry the same offer, at most twice within the original attempt's time limit. It checks the offer again before retrying. Your touch, a new offer, locking the phone or leaving Dasher stops this recovery; an unknown loading screen alone never permits it.
- Peek is on by default after you accept the current notice. On an unlocked, quiet phone it can briefly open Dasher for a fresh background offer and apply your normal rules. It can return to the app you were using after completion evidence; while navigation is detected, it also returns for passing or unclear offers and leaves a card. Otherwise those offers stay in Dasher. If Dasher opens without showing the offer's details, Peek may tap Dasher's ⚙ button once when Dasher shows Finding offers, else Dasher's own offer notification once; if they still don't show, it leaves a card saying so and, while you navigate, returns to your map first. When Dasher is already on screen (in front or beside the app) still showing its wait for offers 5 seconds after an offer's notification, with none of that offer drawn, Peek may tap Dasher's ⚙ once the same way (on Finding offers, after 2 seconds without your touch), else that notification once; never over another of Dasher's screens or after you touch Dasher. Your touch on Dasher or an app switch ends that automatic return (a touch made before Dasher appeared, meant for the app you were in, still lets a completed automatic decline take you back). If the phone locks during Peek, Peek waits up to 60 seconds for you to unlock it; an offer that arrives while the phone is locked can be opened when you unlock within 40 seconds of it, unless you open Dasher yourself first. Within a minute of an offer's first notification, a re-post of it does not open Dasher again when you already had that offer in Dasher or may have accepted it. After repeated withdrawn offers or failed launches, Peek pauses itself until your next dash or for 15 minutes; after an error, until your next dash or until you tap Resume on the homepage. Peek never turns off its Settings switch. You can turn Peek off in Settings.
- When you tap one of its offer cards, it opens Dasher; if Dasher comes up without the offer, it may tap Dasher's ⚙ button once on its Finding offers screen (after 2 seconds without your touch), else Dasher's own offer notification once. After an offer that left you in Dasher from a navigation app ends without being accepted, a Back to map button can take you back; it opens your map only when you tap it.
- During an active dash with auto-decline on and a rule set, it keeps your unlocked screen from timing out, whatever app is in front, while it has seen something of the dash in the last 15 minutes or Dasher shows it, unless the dash is paused in Dasher, a call is under way, battery saver is on, or the battery is at 20% or less and not charging. It never wakes or unlocks the phone; the power button still turns the screen off. This uses more battery.
- While it declines an offer on screen, it can turn media and alarm sound down for a moment and then put them back. During Peek, a delivery or turn-by-turn navigation it touches only the alarm stream, leaving media and navigation audio alone. You can turn this off in Settings.
- A tap is a request to the Dasher app, not a confirmation from DoorDash. Hiding a notification does not decline an order.
- It updates itself from its public signed update feed without requiring an account. An update it finds by itself during a dash waits until the dash ends; if nothing of a dash is seen for 8 hours while Dasher is not in front and the screen is off, it installs then, after checking the update again.
- Use Feedback in Settings to send general feedback or choose a recent offer; Send feedback on an offer's ticket opens the same screen with that offer selected. Feedback and offer reports are accountless and are sent only when you tap Send. Masked diagnostics go only with Share anonymous diagnostics (off by default) turned on: after each dash and with the feedback you send. From 0.6.34 that one switch covers every diagnostic, the offer timing study included, and the update turns it off for everyone until they turn it on. A report the app offers after a stop sends them once, when you tap Send. The privacy text says what each sends, where it goes and how long it is kept: unsent submissions wait on the phone for at most 7 days, and the feedback service keeps them for 90 days. Sending feedback does not guarantee a reply, review or fix.
- Once a day it sends the feedback service one anonymous count, so the developer can see how many people use the app: its version, whether this install was counted before and a random code made new each day. It is on by default; turn it off with Send an anonymous daily count in Settings. The privacy text says what it sends and how the service keeps it (as daily totals for 400 days, and briefly what lets each count once).
Your responsibilities
- Your Dasher account and your agreements with DoorDash are yours. DoorDash's terms ban automated tools that read or collect data from its apps, and Offer Filter is one, so DoorDash could limit or deactivate your account. You decide whether to use Offer Filter, and you accept that risk.
- Obey traffic laws. Do not handle your phone while driving; set your rules before you drive and pull over to look at offers. Offer Filter is not a safety device.
- Check your Dasher history. Offer Filter can misread an offer, decline an offer you wanted, accept an offer you did not want, or fail to act. An automatic Accept request does not prove DoorDash accepted it; check the actual delivery state.
- You must be 18 or older to use Offer Filter.
No warranty
Offer Filter is provided "as is" and "as available", without warranties of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose, accuracy and non-infringement, to the extent the law allows.
Limitation of liability
To the extent the law allows, the author of Offer Filter is not liable for any loss or damage arising from your use of it or your inability to use it, including lost earnings, missed, accepted or declined offers, limits on or deactivation of your Dasher account, fines, or lost data.
Licence
Offer Filter is free and open-source software under the MIT License in LICENSE. That license grants the rights to use, copy, modify and distribute the software, subject to its copyright and permission notice. These terms do not limit the rights granted by the MIT License. Its source code is public, in the project's GitHub repository: https://github.com/Dillxn/dasher-offer-filter. Tips are optional gifts to the author and buy nothing.
Governing law
These terms are governed by the laws of the State of Ohio, United States. Where the law of the place you live gives you rights that an agreement cannot take away, these terms do not take them away.
Changes
These terms may change. When they change in substance, the app shows its notice again before it reads or acts on anything more.
Contact
For privacy, data-deletion and security requests only, email privacy@offerfilter.org. Send everything else through Feedback in the app's Settings.
Stopping
You can stop at any time: pause the filter, disable auto-accept, turn off the app's screen reading and notification access in Android's settings, or uninstall it.