Confirmed users, Bureaucrats and Sysops emeriti
1,217
edits
Data Collection: Difference between revisions
clarify ability to keep limiting to prerelease
(Fix markup for data categories) |
(clarify ability to keep limiting to prerelease) |
||
| Line 28: | Line 28: | ||
== Eligibility for Default on Data Collection == | == Eligibility for Default on Data Collection == | ||
* Categories 1 & 2 (Technical & Interaction data) | * Categories 1 & 2 (Technical & Interaction data) | ||
** Pre-Release & Release: | ** Pre-Release & Release: Data may default on, provided the data is exclusively in these categories (it cannot be in any other category). In Release, an opt-out must be available for most types of Technical and Interaction data. Teams can limit data collection to prerelease populations only if appopriate for testing/validation, cost reduction, or risk mitigation. | ||
* Category 3 (Web activity data) | * Category 3 (Web activity data) | ||
| Line 36: | Line 36: | ||
* Category 4 (Highly Sensitive data) | * Category 4 (Highly Sensitive data) | ||
** Pre-Release: Default off. May be eligible for opt-in data collection by specific users, provided there is (i) advance user notice (ii) consent and (iii) an opt-out. | ** Pre-Release: Default off. May be eligible for opt-in data collection by specific users, provided there is (i) advance user notice (ii) consent and (iii) an opt-out. | ||
** Release: Default off. May be eligible for opt-in data collection by specific users, provided there is (i) advance user notice (ii) consent and (iii) an opt-out. | ** Release: Default off. May be eligible for opt-in data collection by specific users, provided there is (i) advance user notice (ii) consent and (iii) an opt-out. | ||
== Requirements == | == Requirements == | ||