Skip to main content

Privacy Policy

Last updated: 27 May 2026

This page describes what data Grabber (the Android app) and jobblocks21.blogspot.com (this blog) collect, what we do with it, and your rights.

The Grabber Android app

What Grabber stores on your device

  • Your filter settings (minimum £/hr, depot codes, vehicle type, time windows, presets) — stored locally in the app, never transmitted off your device.
  • Job-pack credit balance — stored locally, synchronised with the payment processor only when you purchase a new pack.
  • Per-session run statistics (how many offers screened, how many accepted) — visible only in the app, never transmitted.

What Grabber sends off your device

  • Crash reports via Firebase Crashlytics (Google) when the app crashes. Crashlytics captures the stack trace, device model, Android version, and a crash-time fingerprint. It does NOT capture your filter settings, your Amazon Flex credentials, your delivery history, or the contents of your screen. We use this only to diagnose and fix crashes.
  • Payment transactions via Stripe when you purchase a credit pack. Stripe receives your card details and processes the payment. Grabber receives only a confirmation that the purchase succeeded, plus the credit count to add to your local balance. We never see or store your card number — that lives entirely with Stripe under their security and compliance regime.

What Grabber does NOT do

  • Does not collect, read, or transmit your Amazon Flex login credentials.
  • Does not log your delivery history, route details, customer addresses, or any other content of the Flex app beyond the offer-screen filtering decision in the moment.
  • Does not include any third-party advertising SDK.
  • Does not include any analytics SDK that tracks user behaviour (we have Crashlytics for crashes only, not Firebase Analytics or similar).
  • Does not require an account on our servers — there are no Grabber accounts; your local install is the only state.

Accessibility Service permission

Grabber requires Android's Accessibility Service permission. This is what lets it read the Flex offer screen and tap "Accept" on qualifying blocks. The permission scope is restricted to the Amazon Flex package (com.amazon.flex.rabbit) — Grabber does not read any other app on your device. We made this restriction explicit in the Accessibility Service declaration in the app manifest.

This blog (jobblocks21.blogspot.com)

This blog is hosted on Blogger, a service operated by Google. Google's standard cookies apply to your visits — those are governed by Google's Privacy Policy. We do not run any additional analytics, retargeting, email-signup forms, or third-party trackers on the blog itself.

We have not enabled comments on blog posts. Public discussion happens on Reddit threads we engage with from u/Chemical-Hawk-5378; for direct queries, see "How to contact us" below.

Your rights under UK GDPR

For the limited personal data we hold (your Stripe transaction record + any GitHub issue you've filed), you have the right to:

  • Request a copy of what we hold about you.
  • Request correction of inaccurate data.
  • Request deletion of your data (subject to legal obligations — e.g. financial records may need to be retained for tax purposes).
  • Withdraw consent at any time (uninstalling Grabber removes all local data; deleting your Stripe transaction history is subject to Stripe's data retention policies).

To exercise any of these rights, see "How to contact us" below.

Children's privacy

Amazon Flex requires drivers to be 18 or older. Grabber is intended for adult Amazon Flex couriers. We do not knowingly collect any data from anyone under 18.

Changes to this policy

If we change how Grabber or the blog handles data, we'll update this page and bump the "Last updated" date at the top. Material changes (anything that adds new data collection or third-party sharing) will also be announced via the GitHub release notes for the next app version.

How to contact us

All privacy questions and GDPR requests go through GitHub. Open a new issue at github.com/aynerseda-droid/gtrabber/issues with a clear privacy label and describe what you need. Don't include sensitive personal data in the issue body itself — once it's filed, we'll arrange a private channel for the data exchange.

If you'd prefer the request to be private from the start, file a security-style report via GitHub's "Report a vulnerability" tool on the same repo — that creates a private advisory only the maintainer can see, which is appropriate for sensitive privacy requests too.

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