Difference between revisions of "CoronaRiskScoring (Q4684)"
Jump to navigation
Jump to search
(Created claim: prospect (P368): Privacy International (Q2528)) |
(Removed claim: partner (P137): unknown value) |
||
| Property / partner | |||
| - | |||
| Property / partner: unknown value / rank | |||
| - | |||
| Property / partner: unknown value / qualifier | |||
| - | |||
| Property / partner: unknown value / qualifier | |||
| - | |||
| Property / partner: unknown value / qualifier | |||
| - | |||
| Property / partner: unknown value / qualifier | |||
| - | |||
| Property / partner: unknown value / qualifier | |||
| - | |||
Revision as of 07:43, 28 May 2020
project addressing risk scoring algorithms in contact tracing apps
| Language | Label | Description | Also known as |
|---|---|---|---|
| English |
CoronaRiskScoring
|
project addressing risk scoring algorithms in contact tracing apps
|
Statements
0 references
0 references
unknown value
0 references
unknown value
while AppCensus can't really help with risk scoring directly, they can help with auditing the functioning: input data as well as what gets exfiltrated, both through the app and through Bluetooth
0 references