Skip to main content

Contact

All contact for Grabber and this blog runs through one place: GitHub Issues.

GitHub Issues — the only channel

github.com/aynerseda-droid/gtrabber/issues

Open an issue and add a clear label so it routes correctly. Don't worry about following a strict template — a couple of sentences with the right tag is enough to get me to look at it.

If your message is about… Tag it
A crash, bug or unexpected app behaviour bug
A feature you want or a filter that should behave differently feature
A blog post that's wrong or missing a source blog
A press / journalist enquiry press
A privacy or GDPR data request privacy
An impersonation or scam report (someone pretending to be us) security

For sensitive items (privacy data requests, security issues, impersonation reports), use GitHub's Report a vulnerability link on the same repo instead of a public issue — that creates a private advisory only the maintainer can see.

Typical first-response time: within 48 hours on weekdays.

Where to find the app

Direct APK download (latest release): github.com/aynerseda-droid/gtrabber/releases/latest

Each release page includes the APK file's SHA-256 fingerprint and a VirusTotal URL scan so you can verify integrity before installing.

Reddit and X

Two read-only-ish channels where you can see what we post but the GitHub Issues route is still the canonical place to actually reach us:

  • Reddit: u/Chemical-Hawk-5378 — mostly on r/AmazonFlexUK and r/AmazonFlexDrivers. If you've seen a comment that helped, that's where to find more. If you've seen one that's wrong, please reply on the thread and I'll correct it.
  • X / Twitter: @AynerSeda — short-form tips and pointers to the blog. DMs are open but slower to respond than GitHub Issues.

What we don't do

  • We don't take payment outside the in-app credit-pack system (any "buy Grabber direct from me" message is not from us).
  • We don't sell driver lists or referral packages.
  • We don't write paid endorsements of other Flex tools.
  • If someone is impersonating us asking for payment, please file a GitHub issue tagged security — we'd like to know.

Disclaimer

Grabber is not affiliated with, endorsed by, or built by Amazon. Amazon Flex is a trademark of Amazon.com, Inc.

Comments

Post a Comment

Popular posts from this blog

How to tell if an Amazon Flex block is actually worth accepting — the real maths every UK driver should run

Amazon Flex shows you a headline rate on every block offer. £45 for 3 hours. £18.50/hr. £22.00/hr. Those numbers look fine until you put them through the actual maths a driver does after the fact, and most of them turn out to be a different number than the one on the offer screen. This post is the maths you should be running before you accept, not after. It's the same conversation that happens in every UK driver thread on Reddit — most drivers eventually find their way to a version of this calculation, but it usually takes a few burnt Saturdays first. The headline number is misleading on purpose The £/hr Amazon shows you is the block window divided by the pay. That's the time the route itself takes, from your first drop scan to the last. Everything outside that window — and there's a lot of it — is unpaid. The real time you spend on a block looks more like this: Drive to the depot. Unpaid. Depends on which station you got the offer from. Depot wait time. ...
Post a Comment
Read more

Amazon Flex bot detection in 2026 — why on-device block grabbers differ from cloud commission bots

Amazon's 2025 enforcement push made one thing clear: not all third-party block grabbers carry the same risk. The same Reddit threads that report "my account got flagged after I started using bot X" almost never describe the same architecture as the apps that don't show up in deactivation stories. The difference isn't whether automation is allowed — it isn't, per Amazon's terms. The difference is which detection signals each kind of tool leaves behind. This post is a technical breakdown of those signals: what cloud commission bots look like to Amazon's backend, what on-device accessibility-based grabbers look like, and what Grabber specifically does to keep its cadence pattern closer to a human driver's. None of this is a claim of undetectability — that doesn't exist. It's an explanation of why two block grabbers from the same Reddit thread can have very different deactivation profiles. What Amazon's 2025 enforcement actually targe...
Post a Comment
Read more

What actually gets you deactivated from Amazon Flex in 2026 — and what doesn't

Every Amazon Flex driver thread eventually circles back to the same anxiety: am I about to lose this. Deactivation is the only thing about Flex that's genuinely punitive — every other problem (rate variance, station drama, route quality) is annoying but solvable. Deactivation is final. This post is what's actually known about Flex deactivation in 2026 — from Amazon's own enforcement posts, from driver reports across r/AmazonFlexUK and r/AmazonFlexDrivers, and from the patterns that appear consistently in deactivation stories. It isn't insider knowledge. It's the public picture, organised so you can stop worrying about myths and focus on the things that actually matter. What Amazon's terms actually say The Independent Contractor Agreement — the contract you ticked when you signed up — lists clear grounds for termination. Paraphrased, the main ones are: Failure to deliver in accordance with Amazon's operational standards. Theft, contraband, or v...
Post a Comment
Read more