================================================================================
PRIVACY POLICY & PERMISSION AUDIT
================================================================================
PRIVACY POLICY
Last Updated: October 2026
1. INTRODUCTION
This Privacy Policy outlines how the "Spotify Music & Podcasts Online Downloader" (AudioHub) Chrome Extension ("we", "our", or "the extension") handles user information. We are committed to protecting your privacy and ensuring transparency regarding how our software operates.
2. ZERO DATA COLLECTION PRINCIPLE
We respect your privacy above all else:
• No Personal Information Collected: The extension does not collect, record, transmit, or sell names, email addresses, IP addresses, browsing history, or physical locations.
• No Tracking or Telemetry: We do not use third-party analytics (such as Google Analytics or Mixpanel), advertising trackers, or tracking pixels.
• No External Server Communication: The extension operates entirely client-side inside your browser sandbox. Your audio files and playlists are never sent to external servers or remote databases.
3. LOCAL STORAGE & DATA HANDLING
• All uploaded audio files (MP3, WAV, OGG, etc.) and playlist entries are retained exclusively on your device using the browser's built-in local IndexedDB and chrome.storage.local mechanisms.
• You have full control over this data: clicking "Clear" or uninstalling the extension immediately deletes all locally saved playlists and settings.
4. PERMISSIONS EXPLAINED
The extension requests only two minimal browser permissions:
1. "storage"
• Purpose: Allows the extension to remember your customized settings (volume, audio playback speed, shuffle/repeat preferences) and local playlist track entries.
• Scope: Restricted strictly to the extension's local sandbox. It cannot read data from other extensions or websites.
2. "downloads"
• Purpose: Allows the extension to trigger the saving of audio and podcast files to your computer's default "Downloads" directory when you click the "Download" button.
• Scope: Used only on user-initiated actions. The extension never initiates downloads automatically or in the background.
5. THIRD-PARTY SERVICES
The extension does not embed third-party advertising SDKs or tracking scripts. When you choose to stream an audio file from a public URL you provided, the audio stream is retrieved directly from that URL using standard HTML5 media playback.
6. CHANGES TO THIS PRIVACY POLICY
We may update this Privacy Policy from time to time. Any changes will be posted within the extension documentation and store listing.
7. CONTACT
If you have any questions or feedback regarding this Privacy Policy, please contact the developer via the official Chrome Web Store support page.
================================================================================
CRITICAL PERMISSION AUDIT: "Are all these permissions really needed?"
================================================================================
A detailed analysis regarding Google Chrome Web Store review guidelines and the Principle of Least Privilege:
1. IS THE "storage" PERMISSION MANDATORY?
-> YES, HIGHLY RECOMMENDED.
• Why it is needed: In Manifest V3, Chrome popup windows are transient—they completely close and reset their DOM/JavaScript state the moment the user clicks outside.
• Without "storage": Every time a user opens the popup, their playlist would disappear, the volume would reset to 100%, and the playback speed would reset to 1.0x.
• Review Impact: Google considers "storage" a very low-risk permission that is routinely approved without manual scrutiny.
2. IS THE "downloads" PERMISSION MANDATORY?
-> YES (for native download management), but technically can have an HTML5 fallback.
• Why it is used: The `chrome.downloads` API allows the extension to cleanly trigger downloads with proper sanitized filenames (e.g. `My_Podcast_Episode.mp3`), monitor download status, and place files cleanly into the user's Downloads folder without leaving open blank tabs.
• Could it be avoided? If an extension wants 0 extra permissions for downloading, it can simulate clicks on `<a href="blob:..." download="file.mp3">`. However, in Chrome extensions, anchor downloads from popups can be blocked by popup lifecycles or trigger browser security prompts. Having `downloads` permission provides a rock-solid, reliable user experience.
• Review Impact: Google reviews "downloads" easily as long as the justification states: "Used to save audio and podcast files to disk upon user request."
3. ARE SENSITIVE PERMISSIONS LIKE "tabs", "activeTab", OR "<all_urls>" NEEDED?
-> ABSOLUTELY NOT! (And it is crucial that we DID NOT include them!)
• Many developers mistakenly include:
- `tabs`
- `<all_urls>` or `http://*/*`
- `webRequest`
• Why you should NEVER include them in this extension:
1. Google Chrome Web Store will display a scary security warning during installation: "This extension can read and change all your data on the websites you visit." This frightens users and drastically lowers install rates!
2. Google's review team flags host permissions for intense manual review, which can take weeks and often leads to rejection under the "Excessive Permissions" policy.
3. Because this extension is an audio player and downloader for user-provided files and URLs, host permissions are completely unnecessary.
CONCLUSION:
The current permission configuration (`storage` + `downloads`) is the PERFECT SWEET SPOT:
- Maximum functionality (offline playlists + 1-click downloads)
- Zero scary permission warnings for the user
- "Very Low Risk Impact" badge on Chrome-Stats
- Fastest possible Chrome Web Store review approval