--- a/webaudio/specification.html	Mon Jul 18 17:53:50 2011 -0700
+++ b/webaudio/specification.html	Mon Aug 01 12:05:53 2011 -0700
@@ -252,8 +252,11 @@
           <li><a href="#SecurityConsiderations-section">
           17. Security Considerations</a></li>
       
+          <li><a href="#PrivacyConsiderations-section">
+          18. Privacy Considerations</a></li>
+      
           <li><a href="#requirements">
-          18. Requirements and Use Cases</a></li>
+          19. Requirements and Use Cases</a></li>
 
           </li>
       
@@ -2833,8 +2836,30 @@
 </p> 
 </div> 
 
+<div id="PrivacyConsiderations-section" class="section"> 
+<h2>18. Privacy Considerations</h2> 
+<p> 
+This section is <em>informative</em>.
+
+When giving various information on available AudioNodes, the Web Audio API potentially exposes information on characteristic features of the client
+ (such as audio hardware sample-rate) to any page that makes use of the AudioNode interface. Additionally, timing information can be collected through the
+  RealtimeAnalyzerNode or JavaScriptAudioNode interface. The information could subsequently be used to create a fingerprint of the client. 
+</p>
+
+<p>
+Currently audio input is not specified in this document, but it will involve gaining access to the client machine's audio input or microphone.  This
+will require asking the user for permission in an appropriate way, perhaps via the
+ <a href="http://developers.whatwg.org/video-conferencing-and-peer-to-peer-communication.html#video-conferencing-and-peer-to-peer-communication">getUserMedia() API</a>.
+</p>
+
+</div> 
+
+
 <div id="requirements" class="section"> 
-<h2>18. Requirements and Use Cases</h2> 
+<h2>19. Requirements and Use Cases</h2> 
+<p>
+Please see <a href="#ExampleApplications-section">Example Applications</a>
+</p>
 </div>