Effective Date: February 19, 2026
This Privacy Policy outlines how the Cloud Media Manager & Viewer app handles your data. The app is built with a strict offline-first, client-side only approach, adhering to the highest privacy standards set by the PrivMITLab guidelines.
We do NOT collect, store, transmit, or share any personal data or information. There are:
The application does not use any HTTP cookies. We utilize localStorage purely to save your local UI preferences (such as dark mode and temporary edits to the JSON catalog) within your own web browser.
This application operates as a static client-side wrapper. When you click on a cloud link (e.g., Google Drive, Dropbox, Mega), the application embeds their native iframe players or streams the files directly from their servers to your browser.
By using these cloud providers' links, you interact directly with their infrastructure. They may collect metadata such as your IP address or browser characteristics, governed by their own respective privacy policies. This application does not intercept or transmit any credentials or tokens to those providers.
The application integrates the YouTube IFrame Player API for direct playback of YouTube links. Since YouTube is an external Google service, they may track your viewing habits in accordance with their privacy guidelines. No analytical or watch history data is sent back to this application.
The application utilizes a Service Worker (sw.js) to cache the core files (HTML, CSS, JS, manifest, and the catalog file) directly on your device. This is done entirely locally to allow the application to function when disconnected from the internet. No cached data is uploaded to any server.
Your media catalog resides in data.json which is served from the GitHub repository. If you use the built-in "Apply Changes" feature to update the JSON layout, that modified version is saved to your browser's localStorage. It is never uploaded to any remote server. To permanently update your catalog, you must modify the data.json file in your own GitHub repository directly.
Because there is no backend server and no data is collected, there is no data to delete or request. The codebase is fully transparent, open-source, and static. You can verify this by inspecting the source code files in your browser or directly on GitHub.
← Back to App