PRIVACY POLICY: Flash Player for the Web
Last Updated: October 2026
1. INTRODUCTION & CORE COMMITMENT
"Flash Player for the Web" is dedicated to protecting your privacy and security. We believe that your browsing activity, files, and personal data belong solely to you. This extension is engineered to run 100% locally inside your web browser.
We do NOT collect, transmit, store, sell, or share any personal information, browsing history, web traffic, or device identifiers.
2. ZERO DATA COLLECTION DISCLOSURE
When using "Flash Player for the Web":
• No Personal Information Collected: We do not collect names, emails, IP addresses, or location data.
• No Browsing History Tracked: We do not log, monitor, or track URLs you visit.
• No Analytics or Telemetry: We do not use third-party analytics (e.g., Google Analytics, Mixpanel) or advertising trackers.
• No Remote Data Exfiltration: All Flash (.swf) parsing, rendering, audio synthesis, and emulation execute entirely on your local machine using bundled WebAssembly (Ruffle).
3. EXPLANATION OF REQUESTED PERMISSIONS
The extension requests only three specific Chrome extension permissions in its manifest. Here is exactly what each permission does and why it is used:
• "storage"
- Why it is used: Allows the extension to save your preferences locally via `chrome.storage.local`.
- What is stored: Basic settings such as whether the emulator is turned ON or OFF, whether to auto-convert Flash elements, and your preferred player scaling mode (Aspect, Stretch, or 1:1).
- Scope: Stored strictly on your local browser profile. It never leaves your machine.
• "activeTab"
- Why it is used: Grants temporary, user-invoked access to the single webpage tab that is currently active when you interact with the extension popup or context menu.
- What it does: Allows the extension to inspect the document object model (DOM) of the active tab for legacy Flash tags (`<object>`, `<embed>`, or `.swf` links) and show you how many Flash items were discovered.
- Security advantage: `activeTab` does NOT give ambient or permanent access to websites. It operates only on-demand when you interact with the extension.
• "scripting"
- Why it is used: Enables the extension to dynamically execute the Flash emulator script (`content/content.js`) and inject the player styling (`content/content.css`) into the active tab when you click "Play Flash on this Page" or have Auto-Convert enabled.
- What it does: It replaces obsolete Flash placeholders with an HTML5 canvas player container so you can interact with the Flash content.
--------------------------------------------------------------------------------
ARE ALL THESE PERMISSIONS REALLY NECESSARY?
--------------------------------------------------------------------------------
YES, and this permission set represents the absolute minimum necessary (Principle of Least Privilege) for a functional Flash emulator extension.
Here is why:
1. Why not fewer permissions?
- Without "storage", the extension would forget your preferences (such as turning the player ON or changing the volume) every time you close Chrome or restart your browser.
- Without "activeTab", the extension could not see if the current tab contains Flash games or animations, and could not replace them for you to play.
- Without "scripting", the extension would be technically incapable of injecting the WebAssembly emulator code into the webpage to revive the Flash elements.
2. What permissions were deliberately AVOIDED for your safety?
- NO Host Permissions (`<all_urls>`, `http://*/*`, `https://*/*`): Many other extensions request broad host permissions, giving them permanent background access to read and modify all your web traffic. "Flash Player for the Web" strictly avoids this; it only acts on the tab you are actively viewing when you trigger it.
- NO "webRequest" or "declarativeNetRequest": We do not intercept or redirect your network requests.
- NO "cookies": We have zero access to your website cookies or session data.
- NO "tabs" (broad tabs permission): We do not monitor your background tabs or open windows.
- NO Remote Hosted Scripts: All emulation code and WebAssembly libraries are bundled locally inside the extension package in full compliance with Chrome Web Store security guidelines.
4. LOCAL SWF FILES & DRAG-AND-DROP
When you use the Standalone Player (`player.html`) to open a local `.swf` file from your hard drive, the file is read using the standard HTML5 `FileReader` API in your browser's local memory sandbox. The file is never uploaded to any cloud server or third party.
5. THIRD-PARTY WEBSITES
When you visit third-party websites containing Flash content, those websites remain governed by their own individual privacy policies. "Flash Player for the Web" does not inject ads, tracking scripts, or affiliated links into any page you visit.
6. COMPLIANCE WITH CHROME WEB STORE POLICIES
This extension strictly complies with the Google Chrome Web Store Developer Program Policies, including the Limited Use policy, Data Minimization guidelines, and User Data FAQ.
7. CONTACT
If you have any questions or feedback regarding this Privacy Policy, please open an issue or reach out through our official developer support page.