X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhelp%2Fhtml%2Fprivacy.html;fp=help%2Fhelp%2Fhtml%2Fprivacy.html;h=8704ce88c21724c7a8751b5eafadfe9559330372;hb=4b031bc957ad1c5512798c6206adac7ed0364331;hp=9ad61b5512b8a55bdeb5ec7de768f7e720d84ee9;hpb=6723fff70de0a8576fab9196e99ece7ae67f3dbf;p=jalview.git

diff --git a/help/help/html/privacy.html b/help/help/html/privacy.html
index 9ad61b5..8704ce8 100644
--- a/help/help/html/privacy.html
+++ b/help/help/html/privacy.html
@@ -34,35 +34,36 @@
   <p>Usage data is collected from the logs of various web services
     that the Jalview Desktop contacts through its normal operation.
     These are described below:</p>
-  <ul>
-    <li><em>HTTP logs on the Jalview website</em><br> We
-      record IP addresses of machines which access the web site, either
-      via the browser when downloading the application, or when the
-      Jalview Desktop user interface is launched.<br> <br>
-      <ul>
-        <li><i>The Jalview Getdown Launcher</i> (Since 2.11.0) examines release
-          channels every time Jalview launches to determine if a new
-          release is available.</li>
-        <li><i>The questionnaire web service at
-            www.jalview.org/cgi-bin/questionnaire.pl is checked and a
-            unique cookie for the current questionnaire is stored in the
-            Jalview properties file.</i></li>
-        <li><i>The Jalview web services stack is contacted to
-            retrieve the currently available web services. All
-            interactions with the public Jalview web services are
-            logged, but we delete all job data (input data and results)
-            after about two weeks.</i></li>
-      </ul> <br></li>
-    <li><em>Google Analytics</em><br> Since Jalview 2.4.0b2,
-      the Jalview Desktop records usage data with Google Analytics via
-      the <a href="http://code.google.com/p/jgoogleanalytics/">JGoogleAnalytics</a>
-      class.<br> The Google Analytics logs for Jalview version 2.4
-      only record the fact that the application was started, but in the
-      future, we will use this mechanism to improve the Desktop user
-      interface, by tracking which parts of the user interface are being
-      used most often.</li>
-  </ul>
-  </p>
+	<ul>
+		<li><em>HTTP logs on the Jalview website</em><br> We record
+			IP addresses of machines which access the web site, either via the
+			browser when downloading the application, or when the Jalview Desktop
+			user interface is launched.<br> <br>
+			<ul>
+				<li><i>The Jalview Getdown Launcher</i> (Since 2.11.0) examines
+					release channels every time Jalview launches to determine if a new
+					release is available.</li>
+				<li><i>The questionnaire web service at
+						www.jalview.org/cgi-bin/questionnaire.pl is checked and a unique
+						cookie for the current questionnaire is stored in the Jalview
+						properties file.</i></li>
+				<li><i>The Jalview web services stack is contacted to
+						retrieve the currently available web services. All interactions
+						with the public Jalview web services are logged, but we delete all
+						job data (input data and results) after about two weeks.</i></li>
+			</ul> <br></li>
+		<li><em>Usage Analytics</em><br> Since Jalview 2.11.2.7, the
+			Jalview Desktop records usage data with a self-hosted instance of the
+			analytics stack <a href="https://plausible.io">Plausible.io</a> via a
+			custom GPLv3 client developed by Ben Soares. Prior to this, Jalview
+			versions as far back as 2.4 recorded application launches via <a
+			href="http://code.google.com/p/jgoogleanalytics/">JGoogleAnalytics</a>
+			.<br> Usage logs for Jalview record the fact that the
+			application was started, and details about the OS, installed Jalview
+			launcher (if any) and java version used. In the future, we will use
+			this mechanism to improve the Desktop user interface, by tracking
+			which parts of the user interface are being used most often.</li>
+	</ul>
   <p>
     <strong>Stopping Jalview from calling home</strong><br> If you
     run Jalview in 'headless mode' via the command line, then the