About

Hi — I'm Seda Ayner, the person behind Grabber and this blog.

I started delivering for Amazon Flex in the UK in late 2025. The work itself was fine. The bit that wore me down was the offer screen: spending most of my downtime refreshing for blocks that disappeared the moment I tried to tap them, often because someone with a faster phone or a quicker thumb beat me to it. After enough of that I sat down to build a tool that would screen and accept blocks I actually wanted, on my own phone, without the cloud-bot baggage that triggers Amazon's enforcement.

That tool is Grabber. It's an Android app for Amazon Flex couriers in the UK. It runs as an Accessibility Service on your own device, reads the Flex app's offer screen, and one-tap accepts blocks matching filters you set (minimum £/hr, depot station, vehicle type, time window). No cloud server, no shared account, no subscription. First five blocks are free; after that it's a pay-as-you-go credit pack — £1 for ten jobs, £8 for a hundred, £35 for five hundred. Full product overview: what an Amazon Flex block grabber actually costs in 2026.

What this blog is

This blog is the long-form companion to Grabber. Each post is the answer to a question I either hit myself or kept seeing other drivers ask:

• How to tell if an Amazon Flex block is actually worth accepting — the real £/hr maths once you fold in drive in, depot wait, and unpaid drive home.
• What actually gets you deactivated from Amazon Flex — what shows up in real deactivation reports vs what drivers worry about.
• How to appeal an Amazon Flex deactivation — the documented escalation channels and what tends to move cases.
• Amazon Flex UK weekly hours cap — how the 40-hour rolling window works — explainer on the cap mechanic most drivers misread as "every Monday".
• Amazon Flex bot detection in 2026 — why on-device tools differ from cloud bots — the technical side of why architecture matters more than whether automation is used at all.

How I write these posts

Every factual claim about Amazon Flex (cap rules, escalation paths, forfeit timing, app behaviour) is cited from public sources at the bottom of each post. If I can't source a specific claim, I either flag it as uncertain or leave it out. I've also rewritten earlier posts where I overstated detail — when a UK driver pointed out that a specific in-app UI element I'd referenced didn't actually exist, I removed the claim and apologised in the comment thread on Reddit. I'd rather get fewer things right than more things wrong.

Disclaimer

Grabber is not affiliated with, endorsed by, or built by Amazon. Amazon Flex is a trademark of Amazon.com, Inc. Using any third-party tool to interact with the Flex app may breach Amazon's terms of service; the choice to use one is yours.

Getting in touch

All contact runs through GitHub. Open an issue and tag it appropriately:

• Bug reports + feature requests: github.com/aynerseda-droid/gtrabber/issues
• Blog post corrections, journalist queries, partnership ideas: open an issue at the same repo with a clear label (blog, press, partnership) — I'll route it.
• Privacy / data requests: see the Privacy Policy for how to file one through GitHub.

If you're new and want to try the app, latest release is here: github.com/aynerseda-droid/gtrabber/releases/latest — APK SHA-256 and VirusTotal URL scan are published in the release notes.