Privacy Policy

1. Overview

FTP Playlist Grabber ("the Extension", "we", "our") is a Chrome browser extension that scans FTP directory listing pages and exports file lists as playlists. This Privacy Policy explains what information the Extension accesses, how it is used, and how it is stored.

By installing or using the Extension you agree to the practices described in this policy.

2. Data We Do NOT Collect

The Extension does not:

• Collect, transmit, or sell any personal information
• Send any data to our servers (we operate no backend servers)
• Track your browsing history
• Use cookies or any cross-site tracking mechanisms
• Access any page other than the currently active tab when you explicitly invoke the Extension
• Communicate with any third-party analytics, advertising, or data-collection service

3. Data the Extension Accesses Locally

The Extension reads the following information solely to provide its functionality. None of this information leaves your device.

3.1 Active Tab Content

When you click the Extension icon, it reads the HTML content of the currently active browser tab to detect FTP directory listings and extract file URLs. This happens entirely within your browser. The Extension only accesses the tab you are actively viewing at the moment you invoke it.

3.2 Local Storage (chrome.storage.local)

The Extension stores the following data locally on your device using the Chrome storage.local API:

• User preferences — your settings such as default export format, scan depth, dark/light mode preference, and other UI options
• Scan history — a log of recent scans (URLs visited, file counts) used to populate the History tab
• Session state — temporary data to restore the popup state between opens

This data is stored locally on your device only. It is never transmitted externally. You can clear it at any time by uninstalling the Extension or clearing Chrome's extension storage via chrome://settings.

4. Chrome Permissions Explained

The Extension requests the following Chrome permissions. Each is necessary for a specific feature:

Permission	Why it is required
activeTab	Allows the Extension to read the HTML of the tab you are currently viewing — only when you click the Extension icon. Required to detect FTP directory listings and extract file URLs.
scripting	Allows the Extension to inject a content script into the active tab to parse the FTP directory listing DOM. No scripts are injected without user action.
storage	Allows the Extension to save your preferences and scan history locally using chrome.storage.local. Data never leaves your device.
downloads	Allows the Extension to trigger a file download when you export a playlist — so the generated .m3u / .pls / etc. file is saved to your Downloads folder.

5. Third-Party Services

The Extension does not integrate with, load code from, or send data to any third-party service, API, or analytics platform. There are no embedded trackers, no ad networks, and no crash-reporting services.

6. Children's Privacy

The Extension does not knowingly collect any data from anyone, including children under the age of 13. Because no personal data is collected at all, the Extension inherently complies with COPPA and similar regulations regarding children's privacy.

7. Data Retention and Deletion

All data stored by the Extension (preferences and scan history) lives exclusively in your browser's local extension storage. You can delete it at any time by:

• Uninstalling the Extension from Chrome — this removes all associated storage
• Navigating to chrome://settings/siteData and clearing extension data
• Using the "Clear History" button in the Extension's History tab

We have no copy of your data and cannot delete it on your behalf because we never receive it.

8. Security

The Extension runs entirely within the Chrome extension sandbox. It only accesses the active tab when explicitly invoked by you and does not run background processes that read page content without your action. The Extension is open source — you can audit the full source code at any time.

9. Changes to This Policy

If we update this Privacy Policy, the revised version will be published at this URL with an updated "Last updated" date. Continued use of the Extension after any changes constitutes acceptance of the revised policy. We do not anticipate significant changes because the Extension fundamentally does not collect user data.

10. Contact

If you have questions or concerns about this Privacy Policy or the Extension's behavior, please contact us:

• Email: YOUR_EMAIL@example.com
• GitHub Issues: github.com/YOUR_GITHUB_URL/issues

We will respond to privacy-related inquiries within 30 days.