diff --git a/public/static/docs/user-guide/privacy.md b/public/static/docs/user-guide/privacy.md
index 96df48f177..376841af50 100644
--- a/public/static/docs/user-guide/privacy.md
+++ b/public/static/docs/user-guide/privacy.md
@@ -5,8 +5,8 @@ make it easier to store files on Google Drive. For more details on how to set it
 up, refer to
 [Setup a Google Drive DVC Remote](/doc/user-guide/setup-google-drive-remote)
 
-DVC uses the _DVC_ Project on Google Cloud Platform. (That is the name you will
-see in a consent screen.) DVC integration is governed by common policies,
+DVC uses the _DVC_ Application on Google Cloud Platform. (That is the name you
+will see in a consent screen.) This integration is governed by common policies,
 recorded here.
 
 Your use of Google APIs with DVC is subject to each API’s respective terms of
@@ -18,7 +18,7 @@ service. See
 DVC accesses Google resources from the machine where you use DVC. Your machine
 communicates directly with the Google APIs.
 
-The _DVC_ GCP Project never receives your data or the permission to access your
+The _DVC_ Application never receives your data or the permission to access your
 data. The owners of the project can only see anonymous, aggregated information
 about usage of tokens obtained through its OAuth client, such as which APIs and
 endpoints are being used.
@@ -34,13 +34,13 @@ which requires that you authenticate yourself as a specific Google user and
 authorize these actions.
 
 DVC can help you get a token by guiding you through the OAuth flow in the
-browser. There you must consent to allow the _DVC_ GCP Project to operate on
+browser. There you must consent to allow the _DVC_ Application to operate on
 your behalf. The OAuth consent screen will describe the scope of what is being
 authorized e.g. it will name the target API(s) and whether you are authorizing
 “read only” or “read and write” access.
 
 There are two ways to use DVC with Google Drive without authorizing the _DVC_
-GCP Project: bring your own service account token or configure the package to
+Application: bring your own service account token or configure the package to
 use an OAuth client of your choice. See
 [Setup a Google Drive DVC Remote](/doc/user-guide/setup-google-drive-remote) for
 more information.
@@ -71,7 +71,7 @@ in `.dvc/tmp/gdrive-user-credentials.json`.
 
 ## Usage in other packages or applications
 
-Do not use an API key or client ID from the _DVC_ GCP Project in an external
+Do not use an API key or client ID from the _DVC_ Application in an external
 package or tool. Per the
 [Google User Data Policy](https://developers.google.com/terms/api-services-user-data-policy),
 your application must accurately represent itself when authenticating to Google
@@ -79,7 +79,7 @@ API services.
 
 If you use DVC inside another package or application that executes its own logic
 — as opposed to code in DVC or by the user — you must communicate this clearly
-to the user. Do not use credentials from the _DVC_ GCP Project; instead, use
+to the user. Do not use credentials from the _DVC_ Application; instead, use
 credentials associated with your project or your user.
 
 ## Acknowledgments