Built by someone
who was told to
just do more trips.

Don Quixote did not fight the windmill because he thought he could win.
He fought it because he could not look away.

The system is large. The terms of service are long. The support scripts are rehearsed. The chats time out. The agents disconnect.

We know.

But there is a difference between a person who is wrong and a system that is designed to make you feel wrong. Cervantes understood this four hundred years ago. The knight who charges the windmill is not deluded — he is the only one honest enough to name what he sees.

This site is not a crusade. It is a record.
The windmill does not fall. But it gets documented.

My name is not important. What I did is.

I delivered an order. The restaurant forgot a drink. I am not allowed to open sealed bags — that is the platform's own policy, written in their own words. The customer didn't know that. So they gave me a thumbs down and selected "Professionalism with customers" as the reason.

I didn't argue. I didn't wait. I drove back to the restaurant — on my own time, with my own gas — picked up the missing drink, and delivered it to the customer's door. He shook my hand. He said he would contact support to remove the rating.

He did. And nothing changed.

"A removed rating does not always result in a change to the visible thumbs up/down counts shown in the app."

That sentence was written by a Priority Support agent. It was meant to close the conversation. Instead, it opened this one.

What that sentence reveals

If a removed rating doesn't change the count, and doesn't change the satisfaction rate, then what changes? What does "removed" mean in a system where nothing is visibly different before and after?

It means the display exists to pacify, not to inform. It means the system was designed to make you feel heard while ensuring nothing actually moves. It means platform support is not a resolution mechanism — it is a pressure valve.

I am a software professional. I understand systems. I understand data consistency. I understand when a number that should change does not change. That is not a UX quirk. That is a design decision. Someone chose to build it this way.

Why this site exists

Because I have always believed that if something is wrong, you say so. Clearly. With evidence. Without apology.

I have worked in education technology, training people who had no voice in the systems that governed them. I have worked in enterprise infrastructure, where accountability was measured in uptime and audit trails. I have lived in countries where fairness was a promise rarely kept, and in a country that wrote it into its founding documents.

I know the difference between a system that fails by accident and one that fails by design.

  • No anonymized facts. Every case on this site is documented with real order numbers, real dates, real transcripts. If we can't source it, we don't publish it.
  • No platform affiliation. We are not funded by anyone with a stake in the outcome. This site costs what it costs and runs on principle.
  • No editorializing. The contradictions speak for themselves. We arrange them. We don't need to add adjectives.
  • No surrender. Every time a support agent ends a chat without answering the question, the transcript gets longer. We are patient. We document everything.

Who this is for

For the driver who got a warning for something a restaurant did.

For the one who was told their rating would be reviewed — and was never contacted again.

For the one who asked a direct question and got four different answers from four different agents, none of which matched the numbers on the screen.

For anyone who did the job correctly and was still punished for it — and was told that doing more of the same job was the only remedy.

This site is the answer they should have given you.

— The person who built this.
Orange County, California. June 2026.

Have a case, a question, or a document you want reviewed?
report@driverfairness.com