Created
August 15, 2024 02:35
-
-
Save wahengchang/f6eea3da160192e3a47a6faf40977f26 to your computer and use it in GitHub Desktop.
All Url - Privacy Policy
This file contains 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 URL Extractor Chrome Extension | |
Last updated: 2024/08/15 | |
## Introduction | |
This Privacy Policy describes how the URL Extractor Chrome Extension ("we", "our", or "the extension") collects, uses, and discloses information from its users. | |
## Information Collection and Use | |
The URL Extractor Chrome Extension is designed to respect user privacy. We do not collect, store, or transmit any personal information or browsing data. | |
### Data Accessed | |
- The extension only accesses the content of the current tab when the user explicitly clicks on the extension icon. | |
- This access is used solely to extract URLs from the active webpage. | |
- The extracted URLs are displayed to the user within the extension popup and are not stored or transmitted elsewhere. | |
### Permissions | |
- The extension uses the `activeTab` permission, which allows temporary access to the current tab when the user invokes the extension. | |
- No other permissions are used that would allow access to user data or browsing history. | |
## Data Storage | |
- All functionality of the extension is processed locally on the user's device. | |
- No data is stored beyond the current browsing session. | |
- No data is transmitted to external servers or third parties. | |
## Changes to This Privacy Policy | |
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date. | |
## Contact Us | |
If you have any questions about this Privacy Policy, please contact us at: | |
[email protected] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment