=== PRIVACY POLICY FOR TAB AUTO REFRESH ===
Last updated: October 19, 2026
Tab Auto Refresh ("we", "our", or "the extension") is committed to protecting your privacy. This Privacy Policy explains our practices regarding data collection, user privacy, and browser permissions.
------------------------------------------------------------
1. ZERO DATA COLLECTION PHILOSOPHY
------------------------------------------------------------
Tab Auto Refresh adheres to a strict "Zero Data Collection" policy:
• We do NOT collect, store, transmit, or monitor any personal information.
• We do NOT collect browsing history, visited URLs, web traffic, or search queries.
• We do NOT track user behavior, page interactions, or keystrokes.
• We do NOT use third-party analytics (no Google Analytics, Mixpanel, or telemetry scripts).
• We do NOT operate remote tracking servers or databases.
The extension functions 100% locally and offline on your computer.
------------------------------------------------------------
2. EXPLANATION OF REQUESTED PERMISSIONS
------------------------------------------------------------
Tab Auto Refresh requests only the bare minimum permissions required to perform automated page reloads in Google Chrome (Manifest V3):
1. "tabs"
• What it does: Allows the extension to identify the active tab's title and URL when you open the popup, execute reload commands (via chrome.tabs.reload) according to your chosen schedule, update the countdown badge on the toolbar icon, and clean up background memory when you close a tab.
• What it does NOT do: It does NOT inspect webpage content, read passwords, intercept network requests, or track tabs that you have not scheduled for auto-refresh.
2. "alarms"
• What it does: Chrome Manifest V3 uses background service workers that automatically go to sleep after 30 seconds of inactivity to conserve memory and battery. The "alarms" API allows the browser to wake up the service worker exactly when a scheduled reload interval is due.
• What it does NOT do: Alarms are purely internal scheduling mechanisms. They do not access any user data or network activity.
3. "storage"
• What it does: Uses Chrome's local storage (chrome.storage.local) to save your preferences directly on your device. This includes your custom refresh intervals, cache bypass option, active reload rules, and light/dark theme preference.
• What it does NOT do: Stored preferences remain strictly inside your browser profile and are NEVER uploaded, synced, or transmitted over the internet.
------------------------------------------------------------
3. ARE ALL OF THESE PERMISSIONS STRICTLY NECESSARY?
------------------------------------------------------------
Yes. We have audited every line of code to ensure that no superfluous or unnecessary permissions are declared:
• Can "tabs" be removed?
No. Without the "tabs" permission, Chrome API strictly prohibits extensions from issuing reload commands to background tabs and managing tab-specific countdown badges.
• Can "alarms" be removed?
No. In Chrome Manifest V3, standard JavaScript timers (setInterval/setTimeout) in background service workers are terminated when Chrome suspends the worker. Without "alarms", auto-refresh would stop functioning after 30 seconds whenever the tab or browser is in the background.
• Can "storage" be removed?
No. Without "storage", every time you close the popup or restart your browser, all of your configured intervals and active reloading jobs would be instantly lost.
WHAT WE INTENTIONALLY OMITTED (AVOIDING INVASIVE PERMISSIONS):
To maintain maximum privacy and fast Chrome Web Store approval, we deliberately avoided requesting broad, sensitive permissions:
• NO "<all_urls>" or host permissions: We cannot read or modify the content of websites you visit.
• NO "cookies" permission: We cannot view, alter, or access your session cookies or credentials.
• NO "webRequest" or network interception permissions.
• NO "history" permission.
This makes Tab Auto Refresh one of the safest, most privacy-friendly reload extensions available.
------------------------------------------------------------
4. THIRD-PARTY DISCLOSURE
------------------------------------------------------------
We do not sell, trade, rent, or transfer any user data to third parties under any circumstances. There are no advertising networks, data brokers, or monetization SDKs integrated into this extension.
------------------------------------------------------------
5. CONTACT & INQUIRIES
------------------------------------------------------------
If you have any questions or feedback regarding this Privacy Policy or the security of the extension, please open an issue on our official support repository or contact the developer directly.