Privacy Policy & Zero-Upload Guarantee | Drop & Clean
100% In-browser cryptographic data isolation, zero cloud storage, GDPR & CCPA compliant.
Zero Server Data Upload
Unlike traditional cloud-based tools, Drop & Clean processes one hundred percent (100%) of your media files directly within your own browser window using locally executed WebAssembly. Zero bytes of audio or video content are ever uploaded to, transmitted to, or stored on external servers. Neither the source files, intermediate processing buffers, nor generated outputs leave your device at any stage of the processing pipeline.
Diagnostics & Privacy-First Analytics
The Service relies on the legitimate-interest basis set out in Article 6(1)(f) of the General Data Protection Regulation (GDPR) to collect only minimal, anonymized telemetry and aggregated diagnostic data, limited to processing-speed metrics, scrubbed error reports, aggregate feature-usage statistics, and browser-engine identifiers. Such data is used exclusively to optimize engine performance, maintain service stability, and prevent abuse. No file names, personal identifiers, or media contents are collected, retained, or shared with any third party.
Local Cache & Memory Governance
Temporary audio frames, waveforms, and processing buffers reside exclusively within your browser's private secure sandbox and an IndexedDB-backed cache. You may clear the local cache at any time from the Studio settings; clearing the cache irrevocably erases all locally stored temporary data associated with the Service. The Service maintains no server-side copy of any such data.
Local Private Sandbox Storage & Immediate Erasure
All temporary audio buffers, waveforms, and video frames reside strictly within the browser local private secure sandbox and are never written to any location accessible by third parties. When you close the tab or click Clear Cache, all such buffers are erased instantly and without residual copies. No data is retained on the Company's servers, and no data is shared with any analytics provider other than the aggregate telemetry described in Section 2.