diff --git a/tf_oss_dashboard/help.md b/tf_oss_dashboard/help.md
index 3e1d25fd8207491723a0ac116ba53adde87a46b5..ee5fab835abddd0d421a72cad46faa93fe256dcd 100644
--- a/tf_oss_dashboard/help.md
+++ b/tf_oss_dashboard/help.md
@@ -2,9 +2,6 @@ This is TensorFlow's open-source build status dashboard. It tracks all
 GitHub statuses for the TensorFlow repository that are published to GitHub.
 The source for the dashboard is on [TensorFlow SIG Build](https://github.com/tensorflow/build/tree/master/tf_oss_dashboard).
 
-We use Google Analytics to help figure out how many people are using the
-dashboard, but we don't track anything else.
-
 Many of these jobs use Google's internal continuous integration systems, and may
 not report their results publicly. We're trying to make more of our important
 jobs visible to external developers, but security concerns make this a slow
@@ -71,7 +68,14 @@ Here are some tips and notes about the dashboard:
 - Kokoro, Google's CI system that powers most of these jobs, does not report
   "in progress" jobs, so there is no way to see how many Kokoro jobs are
   pending.
-- The "kokoro" job is actually multiple jobs that are all called "kokoro." These
-  statuses overlap and are effectively useless, because each dot points to a
-  different job. If your (Google) team owns one of these, you need to change the
-  `commit_status_context` github_scm config value to a real name.
+- The "kokoro" job (at the very bottom) is actually multiple jobs that are all
+  called "kokoro." These statuses overlap and are effectively useless, because
+  each dot points to a different job. If your (Google) team owns one of these,
+  you need to change the `commit_status_context` github_scm config value to a
+  real name.
+
+#### Cookies
+
+We use Google Analytics to help figure out how many people are using the
+dashboard, and that's it. [Learn more about Cookies
+here](https://policies.google.com/technologies/cookies).