For example having the app be purely a data collection tool which then streams it to the server to do all computation?
I would bet this is more a case of business goals being met by dev teams in the quickest and easiest way possible, without anyone providing legal or regulatory oversight to ensure the implementation is complying with required laws.
That's not any kind of justification or excuse though!
It's an offence under GDPR to fail to cooperate with a supervisory authority. There are extensive record-keeping and transparency requirements. Trying to play cat-and-mouse is itself illegal and likely to be legible to the regulator.
I'd not be surprised if the next version of the app included an "integrity proctection" added officially in order to "protect couriers' security".. these can be bypassed, but it shows that exposing your tools is not always a wise move.
THEREFORE A COMPUTER MUST NEVER MAKE A MANAGEMENT DECISION
- however the entity that owns it can be held accountable.
[1] - https://reversing.works/posts/2023/12/mobile-reverse-enginee...
[2] - https://media.ccc.de/v/37c3-12133-mobile_reverse_engineering...