Created
July 27, 2025 17:49
-
-
Save Vaishnavimore10/b7f6a581b4d52c77364a31daff85c430 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Privacy Policy for ChatGPT Privacy Guard | |
| Last Updated: July 27, 2025 | |
| Thank you for using ChatGPT Privacy Guard. Your privacy is our top priority. This policy outlines what data the extension handles and how it is treated. | |
| 1. Data We Handle | |
| ChatGPT Privacy Guard handles two types of data to provide its core functionality: | |
| a) Password Hash: When you set a password, the extension creates a one-way cryptographic hash of it. We do not store your actual password in plain text. This hash is used solely to verify your identity when you switch to Private Mode. | |
| b) List of Private Chats: The extension stores a list of the unique identifiers (IDs) for the conversations that you have explicitly marked as private. | |
| 2. How Data is Stored | |
| All data handled by this extension, including the password hash and the list of private chat IDs, is stored exclusively on your local computer using the secure `chrome.storage.local` API provided by your browser. | |
| 3. Data We DO NOT Collect or Transmit | |
| This extension DOES NOT collect, transmit, or share any of your data with any external servers, third parties, or the developer. All functionality is self-contained within the extension and your browser. | |
| We do not track your browsing history, your chat content, or any other personal information. | |
| 4. Changes to This Policy | |
| We may update this privacy policy from time to time. We will notify you of any changes by posting the new privacy policy on this page. | |
| 5. Contact Us | |
| If you have any questions about this privacy policy, you can contact us at [Your Email Address Here]. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment