Merge pull request #259 from webmachinelearning/privacy-considerations

Add privacy considerations for cached/persisted data

index.bs

@@ -428,7 +428,9 @@ No information from the underlying platform is exposed directly. An execution ti
 
 Note: The group is <a href="https://github.com/webmachinelearning/webnn/issues/85">soliciting further input</a> on the proposed execution time analysis fingerprinting vector and will augment this section with more information and mitigations to inform the implementers of this API.
 
-Implementers of this API are expected to be familiar with the <a href="https://gpuweb.github.io/gpuweb/#security-privacy">WebGPU Privacy Considerations</a>.
+Unlike APIs like WebGL, and WebGPU; this API does not intrinsically support custom shader authoring; and as a result is not prone to timing attacks that rely on shader caches, or other persistent data. The API builds upon pre-existing shaders and lower level primitives of the browser or the underlying OS. Web developers who interface with {{GPUDevice}} are expected to be aware of <a href="https://gpuweb.github.io/gpuweb/#privacy-user-agent-state">WebGPU compilation cache considerations</a>.
+
+In general, implementers of this API are expected to be familiar with the <a href="https://gpuweb.github.io/gpuweb/#privacy-considerations">WebGPU Privacy Considerations</a>.
 
 Ethical Considerations {#ethics}
 ===================================
@@ -2490,6 +2492,7 @@ Thanks to Alex Gough and the Chrome Security team for security review and questi
 
 Thanks to Michal Karzynski for sharing practical guidelines and learnings from ONNX.
 
+Thanks to Kaustubha Govind and Chrome privacy reviewers for feedback and privacy considerations.
 <pre class="biblio">
 {
   "Models": {