================================================================================
PRIVACY POLICY FOR CHANGE CASE
Last Updated: October 2026
================================================================================
1. INTRODUCTION & CORE PRIVACY COMMITMENT
Change Case ("the Extension", "we", "us", or "our") is designed from the ground up to respect user privacy and adhere to the highest security standards.
Our privacy promise is straightforward:
• We DO NOT collect, store, transmit, or sell any personal data.
• We DO NOT track your browsing history, keystrokes, visited websites, or search queries.
• We DO NOT use external analytics, advertisements, tracking cookies, or third-party tracking scripts.
• 100% OF TEXT CONVERSION OCCURS LOCALLY ON YOUR COMPUTER.
2. HOW THE EXTENSION WORKS & DATA HANDLING
When you select text on a webpage or type into the extension popup:
1. The text is processed strictly within your computer's local memory (RAM) using client-side JavaScript algorithms.
2. The converted text is immediately placed back into your active input field, editor, or system clipboard.
3. Once the conversion is completed, no log, copy, or record of your text is retained anywhere.
4. The extension does not connect to any remote server or external API.
3. PERMISSIONS BREAKDOWN & WHY THEY ARE USED
To perform text case transformations seamlessly across the web, Change Case requests the following specific permissions:
• contextMenus:
- Why it is used: Allows the extension to add the "Aa Change Case" options into the standard right-click context menu in Google Chrome.
- What it does NOT do: It does not give access to your browsing history or page content; it only displays menu items when you right-click.
• activeTab:
- Why it is used: Grants temporary, scoped access ONLY to the single tab that is currently active, and ONLY when you explicitly invoke an extension action (such as clicking a context menu item or pressing a shortcut key).
- What it does NOT do: It does not monitor background tabs, does not run automatically on web pages you browse, and expires as soon as you navigate away.
• scripting:
- Why it is used: Chrome Manifest V3 requires the "scripting" API (specifically chrome.scripting.executeScript) to perform in-place text replacement in editable textareas, input fields, and rich text editors on the active tab upon your command.
- What it does NOT do: It does not inject code automatically or persistently into websites. It only runs transiently when you trigger a transformation.
• storage:
- Why it is used: Enables saving your custom preferences—such as words you want to protect in the "Ignore List" or custom word replacements in the "Correct List"—via chrome.storage.sync so they remain saved between browser sessions.
- What it does NOT do: It does not store personal data or documents; it only holds your configuration text strings.
4. ARE ALL THESE PERMISSIONS TRULY NECESSARY?
YES. Every declared permission is strictly necessary for the extension to fulfill its single core purpose, following Google's "Principle of Least Privilege":
• Why activeTab + scripting instead of broader permissions?
Many legacy extensions requested broad host permissions such as "<all_urls>" or "*://*/*", which allowed extensions to read and inject scripts into every webpage automatically.
Change Case deliberately avoids all host permissions. Instead, it pairs "activeTab" with "scripting", meaning the extension receives temporary permission only at the exact moment you invoke an action. This is Google's officially recommended best practice for secure text manipulation tools.
• Could we remove "contextMenus"?
Only if users were forced to copy text, open the extension popup, paste the text, convert it, copy it back, and paste it into their editor. The context menu enables the seamless 1-click right-click workflow that users expect.
• Could we remove "storage"?
Only if users were willing to lose their Ignore List and Correct List preferences every time they restart their browser.
• What permissions were explicitly OMITTED because they are NOT needed?
- NO "<all_urls>" or broad website permissions
- NO "tabs" permission (which would expose browsing history and open tab URLs)
- NO "webRequest" or network inspection permissions
- NO "cookies" permission
- NO "identity" or Google account login permissions
5. THIRD-PARTY SERVICES & ANALYTICS
Change Case does not use any third-party SDKs, telemetry frameworks, tracking beacons, or cloud servers. All assets, scripts, and stylesheets are packaged locally inside the extension.
6. COMPLIANCE WITH CHROME WEB STORE POLICIES
Change Case complies with all Google Chrome Web Store Developer Program Policies, including the Single Purpose Policy, Limited Use Requirements, and the Privacy and Security Guidelines.
7. CONTACT & INQUIRIES
If you have questions, feedback, or suggestions regarding this Privacy Policy or the extension, please contact us through the extension's Chrome Web Store support page.