e-passes do not have anything to do with proximity tracing.
So suggesting to move it as a separate optional app linked instead of integrating with proximity tracing
e-passes linked with identity, address, and destination, and often includes family/co-traveler details.
A contact tracing app, which already collecting social graph and location, linking it with state verified identity-based e-passes is a dangerous data-hungry development without purpose limitation for contact tracing.
So this should be split out as a separate app, linked from aarogya setu, for those who need, without any interlinkage between both
I know the Android app is just a web view on top of a non-released proprietary server as listed in #1.
But since this app is pitching itself as a user-facing contact tracing app, it should address this concern
e-passes do not have anything to do with proximity tracing. So suggesting to move it as a separate optional app linked instead of integrating with proximity tracing e-passes linked with identity, address, and destination, and often includes family/co-traveler details. A contact tracing app, which already collecting social graph and location, linking it with state verified identity-based e-passes is a dangerous data-hungry development without purpose limitation for contact tracing.
So this should be split out as a separate app, linked from aarogya setu, for those who need, without any interlinkage between both