diff --git a/About-the-required-permissions.md b/About-the-required-permissions.md
index e75556f..3e06a2a 100644
--- a/About-the-required-permissions.md
+++ b/About-the-required-permissions.md
@@ -75,6 +75,8 @@ This is necessary to be able to:
     - This will ensure no TCP connection is opened **at all** for blocked requests: **It's for your own protection privacy-wise.**<sup>[1]</sup>
     - For pages with lots for blocked requests, this will actually remove overhead from page load (if you did not have the setting already disabled).
     - When uBlock blocks a network request, the expectation is that it blocks **completely** the connection, hence the new permission is necessary for uBlock to do **truthfully** what it says it does.
+- Disable _"Disable hyperlink auditing/beacon"_
+    - [Background information](http://www.wilderssecurity.com/threads/hyperlink-auditing-aka-a-ping-and-beacon-aka-navigator-sendbeacon.364904/).
 
 uBlock's primary purpose is to block **network connections**, not just data transfer. Not blocking the connection while just blocking the data transfer would mean uBlock is lying to users. So this permission will stay, and sorry for those who do not understand that it actually allows uBlock to do its intended job more thoroughly<sup>[2]</sup>. A blocker which does not thoroughly prevent connections is not a real blocker.