Desired functionalities in CWA vs data/privacy protection

[dsarkar]

Question to the community!

• The CWA is limited in certain functionalities, due to limitations related to data/privacy concerns and protection. These limits are established amongst others in the law, in the technical implementation of the ENF, and the policy of Google/Apple.

• However, in this community, in the AppStores and other media, regularly proposed enhancements would affect the area of data/privacy protection.

Question: Which are the most desired or mentioned functionalities/enhancements (but seem currently impossible to be implemented due to privacy concerns and/or technical limitations of the ENF and/or Apple/Google policy.)?

Thank you very much for your help to shed some light on this and let's improve/modify the following list

• More information on risk encounter
  • exact time of risk encounter
  • exact location of risk encounter
• UX/UI contact diary
  • Access GPS to enter a location
  • Access to the phone's contacts to enter a person

[dsarkar]

@Ein-Tim @ndegendogo @MikeMcC399 and community ?

[Ein-Tim]

IMHO most desired:

• Informative logging results to be available in app #5 (or something similar which confirms the user that the app works) - informative logging results
• Location and exact date of a low risks (green) contact #206 (related: Show more details about "risk encounters" #100, Restaurant mode #208, Make it possible to optionally share the exact time of encounters #266, Feature Request and Implementation Concept: report/map risky contacts - show, where and when risky contats happened #288, Collecting place & time of infections for RKI & respecting data privacy #349) - time/location of risk encounters

[ndegendogo]

Yes, I think @Ein-Tim already mentioned the most pressing and desired.

• Informative logging results to be available in app #5 / Display currently received beacons with distance #19 / Möglichkeit zum Testen der Funktionsfähigkeit der App #243 - some way to confirm that everything is setup and working correctly, especially with regard to the BLE beacons. We have seen that some settings (esp. on some Android configurations) can be tricky. But also imagine, my phone fell to the ground and the screen broke - how can I verify that the BLE unit is not also broken?
• Location and exact date of a low risks (green) contact #206 and similar (more information / details on risk encounters).
• then there were some ideas to address "superspreader events" and "clusters", like Potential super-spreader identification and notification #355 / [Paper] Lighthouses: A Warning System for Super-SpreaderEvents #279 / Display the number of current contacts in range #262 / Source cluster detection helper #240 / Semi-Automated Source-Cluster Detection #213
• and if you are in discussion with Apple & Google, you could also mention Corona-Warn-App for Apple-Watch #12 (support for Apple Watch)

And, maybe off-topic here, but maybe you can also bring up #109 - "One phone can be used to manage all tests of a family". This feature was very much missed last summer (and I am sure, latest next holiday season this discussion will come up again). It will need some kind of concept for a "local user account management".