Merge pull request #32 from WICG/update-privacy-security-section

Update privacy security section
w3c · Jun 27, 2019 · 40fde42 · 40fde42
2 parents 4c99dcf + 5f6795d
commit 40fde42
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 1 deletion.
diff --git a/explainer.md b/explainer.md
@@ -276,4 +276,3 @@ The API allows `set()`ing an `unsigned long long`. When presenting this value, i
 
 ### Security and Privacy Considerations
 The API is set only, so data badged can't be used to track a user. Whether the API is present could possibly be used as a bit of entropy to fingerprint users, but this is the case for all new APIs.
-
diff --git a/index.html b/index.html
@@ -114,6 +114,7 @@ <h2>
         If the application's badge is <b>nothing</b>, the badge is said to be
         "<dfn>cleared</dfn>". Otherwise, it is said to be "<dfn>set</dfn>".
       </p>
+      <p>Note: The API is set only, so the badge data cannot be used to identify users.</p>
     </section>
     <section>
       <h2>
Original file line number	Diff line number	Diff line change
Expand Up		@@ -276,4 +276,3 @@ The API allows `set()`ing an `unsigned long long`. When presenting this value, i

		### Security and Privacy Considerations
		The API is set only, so data badged can't be used to track a user. Whether the API is present could possibly be used as a bit of entropy to fingerprint users, but this is the case for all new APIs.