Privacy Policy & Data Disclosures
Last updated: October 29, 2026 · Extension: Floatube (v1.0.0)
Zero Data Collection & 100% Local Storage
Floatube operates with a strict zero remote data collection architecture. The extension does not operate remote user databases, does not transmit telemetric data to external tracking servers, and does not collect personal identifiers.
chrome.storage.local.1. Exact Data Stored Locally on Your Machine
In compliance with Google Chrome Web Store User Data Policies, here is the exact breakdown of the data schema stored inside your browser's isolated chrome.storage.local:
settings)Stores your preferred playback rate (0.25x–2.0x), default volume, size presets (Small, Medium, Large), player opacity (30%–100%), auto-hide control timers, theme (Dark, Light, System), and behavior toggles (Minimize to Bubble, Focus Mode, Audio-Only Mode).
queue)Stores videos you manually add to your queue (Video ID, title, channel, duration, and thumbnail URL) to allow auto-playing the next video.
watchLater)Stores video links you mark to watch later. Completely private to your browser and not synchronized with any external server.
bookmarks)Stores your saved timestamps with custom notes and labels (Alt + B) so you can jump back to specific moments in tutorials or podcasts.
continueWatching)Stores your last watched timestamp and progress percentage for recent videos so you can resume where you left off.
playerPosition & playerSize)Saves the X and Y coordinates and width/height of the floating player on screen so it stays in your preferred position.
2. Manifest Permissions & Exact Technical Justification
Every permission declared in Floatube's manifest.json is strictly limited to enabling player functionality:
Why needed: Enables reading and saving local settings, queues, bookmarks, and player coordinates strictly on your local computer.
Why needed: Used only when interacting with the extension to check if the currently active tab is playing a YouTube video (youtube.com/watch or youtube.com/shorts), allowing the popup to display current video info and control playback.
Why needed: Injects the Picture-in-Picture trigger and floating UI overlay scripts into the YouTube page when requested by the user.
Why needed: Creates 3 right-click context menu shortcuts on YouTube links and video pages: "Open in Floating Player", "Add to Queue", and "Watch Later".
Why needed: Communicates with the optional local Electron companion app (com.floatube.companion) via standard local OS standard input/output pipes (stdin/stdout) for true system-wide always-on-top window display. No network communication is involved.
Why needed: Strictly restricted to youtube.com domains. Floatube has zero permission or capability to read, monitor, or interact with any non-YouTube website you visit.
3. YouTube API & Third-Party Interaction
Floatube operates on top of YouTube using standard web video elements and official YouTube IFrame embeds:
- When you watch a video, YouTube's standard content delivery rules and policies apply. View YouTube's official Google Privacy Policy and YouTube Terms of Service .
- Floatube does not bypass advertisements, does not download copyrighted videos to disk, and does not harvest private user tokens or cookies.
4. How to Delete All Stored Data
Because all data is stored exclusively on your device, you have immediate, permanent control:
Click the extension icon > Settings > scroll to DATA > click "Clear Queue", "Clear Watch Later", or "Reset All Settings".
Removing Floatube from chrome://extensions/ immediately and permanently purges all saved local data and preferences from your device.
5. Children's Privacy (COPPA Compliance)
Floatube does not collect any personal data from anyone, including children under the age of 13.
6. Contact & Support
For questions regarding this privacy policy or the Floatube Chrome Extension, please contact:
Developer Support: support@apnichoice.com