Privacy

Offer Filter privacy

Beta privacy policy, effective 19 November 2026 · for Offer Filter 0.6.52

Offer Filter does not require an Offer Filter account and has no ads or mandatory analytics. It does not sell or rent your data. Offer reading and decisions happen on your phone. Update requests, feedback you send, the optional anonymous diagnostics, the anonymous daily count (on unless you turn it off), place-name lookups and links you choose to open can send information to the services described under What leaves the phone. The developer's public project identity is Dillxn. Offer Filter is beta software, and this text changes with it (see Changes).

What it reads on the phone

Before you accept the current first-run notice, it reads none of this and sends no feedback, diagnostics or daily count, with three exceptions that read no words: the channel a new notification of Dasher's came on, to post one reminder that the app is paused; after an update, which app is in front, to reopen Offer Filter only over its own screen or the home screen; and whether Android lets it install its own updates. It checks for updates only once you accept the current notice (from 0.6.18), and accepting it runs the first check.

Optional offer timing study

The offer timing study is part of Share anonymous diagnostics (from 0.6.34; before, Settings offered it as a separate choice, “Include future offer timing study in diagnostics I choose to share”). It records nothing while that switch is off. Turning the switch on starts a fresh study; turning it off, or Clear history, ends it and removes its data from this phone and from unsent reports. The update to 0.6.34 forgets the separate choice and removes what it kept. Accepting the notice never turns the switch on.

While it is on, new observations are processed locally to compare an estimate frozen before an outcome with subsequently observed waiting and numeric offer quality. This study uses a separate instance of the existing historical-mean estimator, trained only on observations made since the switch was turned on (and reset after a process, session or policy change); it is not a claim to capture DoorDash's algorithm or every homepage estimate. It stores no old waiting-history export. Records contain method/schema versions, the estimate or an unavailable marker, actual evidence counts and exposure, a last-complete-wait baseline when available, normalized filter score/bar, a local sequential policy epoch, UTC hour without date, numeric pay/miles/minutes/stops/items, fixed requested-action and observed-outcome categories, touch-takeover evidence and explicit unknown/censor reasons. It does not compute or invent prediction confidence. Hidden, locked, paused, disconnected and missing time is not counted as observed waiting; unfinished waits remain censored. Requested taps are not proof of acceptance or decline. Time, location, demand and unseen offers confound this observational comparison.

The study retains at most 32 result rows and up to 200 new numeric training samples, for at most 24 hours during use; training and live timers are not restored after restart. Its report section is at most 10,000 characters and ten recent rows, with omission counts, inside existing report limits. No customer/merchant text, address, coordinates, raw nodes/screenshots, account/device identifier, acceptance rate, Autopilot goal/plan, configured minimum amounts or free text is included. The feedback dialog's Preview shows the study section with the rest of what goes. Study data goes only with the diagnostics the switch sends: with feedback you send and in the capped summaries after each dash. It uses the same feedback recipient, queue limits and stated 90-day server retention below; this candidate does not establish that server retention has been verified. Existing automatic-summary exclusions remain unchanged.

Uncheck and save to stop new study collection/sharing and discard local study data and study sections in unsent reports. Other feedback and the automatic-report choice remain unchanged. An emptied study-only report part carries a fixed omission notice so the ordinary report can finish under its original submission token and part count. Clear history also removes study data and invalidates prepared study sections. A report already sent or a request already in flight cannot be recalled by these controls. No driving/filter/acceptance behavior changes. Review before sharing; numeric combinations can still be identifying in context.

What it keeps on the phone

Item counts on shopping offers are kept only as offer figures; no rule uses them. An unread declared count stays unknown; no quantity is inferred from product names, unique-item counts, stops or orders. These numeric item facts can appear in the reports and diagnostics you choose to send, like the other offer figures.

The historical 0.5.0 migration deleted the old learned minimums and the held hand-decline record from the phone the first time it ran: what older versions' adaptive minimum learned from offers you accepted or declined (their pay and rates, and when learning was on or reset), the record of offers you declined by hand, and the retired rules (per stop, per item, the hotspot distance, the minimums percentage and score by area), after building per stop and the minimums percentage into your minimums. Until you close the one-time note about this change, a summary of it (your old and new minimums, as numbers) stays with your rules. Decisions an older version recorded keep the reasons and notes they were recorded with, which can name an amount its adaptive minimum had learned (such as "must match best accepted $0.45/min"), until newer decisions replace them or you clear history; like the rest of the history, they can go in a report you share or send. Log lines it wrote about what it learned age out with the logs within 24 hours.

Decision and confirmation lines take priority over repeated scan timings within the existing log limits. Reports include numeric counts of discarded log lines, so missing evidence is visible. Atomic history writes keep a recovery copy only while replacing the same bounded history.

Screen text is masked before it is kept: customer names, your own name, street addresses, city, state and ZIP lines, apartment numbers, phone numbers, email addresses, delivery instructions, card numbers and their security codes/expiry/PIN, and streets in navigation become [name], [address], [phone], [email], [instructions], [card] and [street]. Store names, offer figures, buttons and shopping items stay. Offers are judged from what is on screen; only what is kept is masked. Click diagnostics retain the control shape and action category, never its text labels.

Masking is pattern-based and can miss unfamiliar wording. It is not a guarantee of anonymity or removal of every personal detail. Review what you send with Preview first. What you type in feedback, including notes about a selected offer, is not masked; do not include customer, payment or account details. Diagnostics and offer reports waiting to send are masked again with the current rules immediately before sending.

Versions before 0.5.0 could connect to GitHub and file problem reports and diagnostics there, as issues in the project's GitHub repository (https://github.com/Dillxn/dasher-offer-filter). That repository is public, so what was filed there could be read by anyone; earlier versions of this text wrongly called it private. This version sends nothing to GitHub. The first time it runs, it deletes any stored GitHub connection, its history, the old report queue and its scheduled jobs, once. A one-time privacy cleanup also clears older diagnostic logs if it has not already completed on this installation. Neither cleanup can remove copies that were already sent.

Android backup is turned off for this app, so none of this goes into your phone's cloud backup.

Autopilot and your acceptance rate

Autopilot is on by default (from 0.6.2, and turned on once then for earlier installs) until you turn it off. It uses your decision history, the wait-estimate records above and the acceptance rate Dasher shows to move its shared bar between 10% and 150% (from 0.6.32; between 50% and 150% before). From 0.6.29 it also follows each new positively confirmed personal standalone acceptance while on, whether or not acceptance learning is on: each readable active pay-per-stop, pay-per-mile and pay-per-hour working minimum moves independently up or down to that offer's value. From 0.6.31 it also keeps that offer's total pay, and in area mode a quarter of each Autopilot score weighs an offer's total pay against it. This happens between offers, at the screen reader's safe point. The latest acceptance replaces earlier accepted levels and starts the bar's next-24-offers hold again; earlier accepted scores do not override a newer lower acceptance. From 0.6.37 it also reads the decision history for offers you declined yourself since that acceptance: each holds the bar at least one point above its score under your current rules for the 24 counted offers after it. Nothing new is kept for this; the decline is the history's record of what was seen of the offer afterward. Later bar changes move these working minimums together. Turning Autopilot off uses exactly your saved and enabled learned minimums again; turning it on with the same goal restores its retained working adjustments. Autopilot never changes saved minimums or the learner's independent bests. Its earlier growth of saved minimums ended in 0.6.21.

The acceptance learner and independent Autopilot minimums add no new recipient or automatic-sharing choice. Existing diagnostics can include scoring mode, learning on/off and the recorded score kind, alongside observed offer figures and per-decision required pay, and fixed-word lines saying whether each of your accepts taught the learner and, if not, why (no amounts). Raw learned-best snapshots and adoption receipts are not sent. The offer timing study continues to exclude minimum amounts and learner evidence.

What leaves the phone, and when

Feedback in Settings is the single reporting screen. Under About, choose General feedback or a recent offer. Send feedback on an offer's ticket opens the same screen with that offer selected; setup and stop notices also open it. The preview, Send action, submission status and last ten references are shared. Each selection keeps the scope below. Export diagnostics is an optional diagnostic export inside this screen and does not submit the feedback draft.

Render, Cloudflare, Supabase, Google, Anthropic and OpenAI, and the email services that carry a message you send to the privacy contact below, handle what reaches them under their own terms and privacy policies. Copies you deliberately share through another app are controlled by that app and recipient.

What it never collects

The app does not request your DoorDash password, contacts, photos, messages, precise location or payment details. Accessibility can expose unrelated text when Dasher displays it; recognized payment, account and earnings screens are discarded, and the masking described above is applied before diagnostic text is saved.

Your choices

Help and privacy contact

Use Feedback in Settings, or the feedback form on offerfilter.org, for non-sensitive feedback without creating an account. Do not type customer, payment, account or other sensitive details. If you need to refer to an earlier submission, keep the short reference shown after it is accepted; Settings' feedback dialog lists the last ten.

For privacy, data-deletion and security requests only, email privacy@offerfilter.org. Unlike feedback, email is not anonymous: the developer sees your address and uses it only to answer you. Your message passes through your own email provider and the email services that deliver mail for offerfilter.org to the developer. Feedback carries no name or account, so to ask about a submission you sent, include its reference; without it the developer may be unable to tell which anonymous submission is yours. Send everything else as anonymous feedback.

The project's public issue tracker is suitable only for public, non-sensitive development discussion; posts there are public. Do not attach diagnostic reports, customer details, payment or account information, addresses, screenshots containing personal information, or tokens.

Children

Offer Filter is not for anyone under 18.

Changes

When this text changes in substance, the app shows its notice again before it reads anything more or sends feedback or its daily count.


This website

The sections above describe the app. This one covers offerfilter.org itself.