-
Notifications
You must be signed in to change notification settings - Fork 2
Privacy Policy
Privacy Policy for Rename File Extension on Upload Chrome Extension
Effective Date: March 28, 2025
Thank you for using Rename File Extension on Upload (the "Extension"), developed by Jamison Moore. This Privacy Policy explains how the Extension handles information. We are committed to protecting your privacy.
1. Purpose of the Extension
The Extension is designed to help users upload files that have specific non-standard extensions (like .log
, .ts
, .js
, etc.) to websites that expect a .txt
extension. It achieves this by modifying the file's name/extension locally within your browser just before the upload process begins on websites where you explicitly grant permission.
2. Information We Collect and How We Use It
Rename File Extension on Upload is designed with user privacy as a priority.
-
User Configuration Settings: We collect and store the following settings, which you configure via the Extension's options page:
- The list of file extensions you want to be renamed to
.txt
. - The state of the toggle option ("Rename ALL selected files").
-
How it's stored: These settings are stored locally on your computer using the
chrome.storage.sync
API provided by Google Chrome. If you are signed into Chrome, these settings may be synchronized across your devices by Chrome, but they are not transmitted to the developer (Jamison Moore) or any third-party servers. - Purpose: This information is used solely to control the functionality of the Extension according to your preferences – determining which files get renamed when the extension is active on an approved site.
- The list of file extensions you want to be renamed to
-
Information We DO NOT Collect:
- File Content: The Extension DOES NOT read, store, or transmit the content of any files you select for upload.
- Filenames (Persistently): While the Extension reads filenames temporarily to check extensions and perform renaming, these filenames are NOT stored persistently by the Extension or transmitted anywhere. The renaming happens locally within the browser's file input mechanism.
- Browsing History: The Extension does not track your browsing history or the list of sites you visit or enable it on.
- Personal Information: The Extension does not collect any personally identifiable information (like your name, email address, IP address, location, etc.).
-
Website Data: The Extension only interacts with specific
<input type="file">
elements on web pages where you have granted permission and does not read or collect other data from those websites.
3. Information Sharing
We DO NOT share, sell, rent, or trade any information, including your configuration settings, with any third parties. All processing happens locally within your browser.
4. Data Storage and Security
Your configuration settings are stored securely using Chrome's standard storage mechanisms (chrome.storage.sync
). Access is limited to the Extension itself running within your browser. Granted site permissions are managed securely by the Chrome browser itself via the chrome.permissions
API.
5. Permissions Justification
The Extension requires the following permissions to function:
-
storage
: Necessary to save and retrieve your configured settings (extensions list, rename-all toggle state) usingchrome.storage.sync
. This allows user customization of how files are renamed. -
scripting
: Necessary to inject the core logic (content.js
) into web pages after you explicitly grant permission for that specific site via the extension's popup action. This script is responsible for detecting file selections and performing the renaming based on your saved settings. -
tabs
: Required by the extension's popup action (toolbar icon) to identify the URL and hostname of the currently active tab. This information is needed solely to request or revoke the necessary host permission for that specific site using thechrome.permissions
API. This permission is not used to track browsing history. -
optional_host_permissions
(https://*/*
,http://*/*
): This declares the potential for the extension to request access to HTTP and HTTPS websites at runtime. It does not grant access automatically. Access to any specific website is only granted when you explicitly click "Enable on This Site" in the extension's popup for that site and approve the browser's permission prompt. This allows you to enable the extension only where needed, without granting broad access upfront.
6. User Choices and Rights
You have full control over the Extension's configuration and permissions.
- You can modify the list of extensions to rename and the "Rename ALL" toggle at any time via the Extension's options page.
- You control which websites the extension can access by using the "Enable on This Site" / "Disable on This Site" buttons in the extension's popup when visiting a website.
- You can view and revoke permissions for specific sites via the Extension's options page ("Sites Enabled via Popup" section) or through Chrome's standard extension permission management settings.
- You can disable or uninstall the Extension at any time.
7. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. If we make significant changes, we will update the "Effective Date" at the top of this policy. We encourage you to review this policy periodically.
8. Contact Us
If you have any questions or concerns about this Privacy Policy or the Extension's practices, please contact me at: Jamison.moore@gmail.com