Update PrivacyPolicy

Update to be a bit more generic

PrivacyPolicy.md

@@ -1,15 +1,15 @@
 # Privacy Policy
-Here are the ways that the **RIPS Validation Extension** changes / uses your webpage:
+Here are the ways that any Chrome Extensions by "**The RIPS Guy**" change / use your webpage:
 
 ## Login Name Tracking
-When users log in to RIPS, username is stored in Firebase Database. This is the data stored in the database:
+When users log in to RIPS, username is stored in a Firebase Database. This is the data stored in the database:
 1) username
 2) last login date
 3) Number of times user has logged in, on current version of extension
 
 This is meant for a few purposes:
-1) Tracking how many RIPS users have accessed RIPS on current version of extension
-2) When new staff is hired, make sure they are using RIPS with the extension is installed
+1) Tracking how many RIPS users have accessed RIPS on current version of the extension
+2) When new staff is hired, make sure they are using RIPS with the extension installed
 3) If some data is stored in RIPS with invalid format, confirm that they disabled or deleted the extension via Firebase.
 
 ## Chrome Dev Features
@@ -23,4 +23,8 @@ This is meant for a few purposes:
 3) chrome.storage
     - stores / edits / listens to local storage data changes
 
-
+## Web page manipulation
+Some extensions directly manipulate your webpage in the following ways:
+1) Hiding content the users don't need to see
+2) Adding improved formatting to the pages
+3) Adding new elements (like error messages)