Skip to main content
Back to Vidara MP3

Privacy Policy

Vidara MP3 Privacy Policy

Vidara MP3 processes selected media files locally in your browser with ffmpeg.wasm. Files are not uploaded to a conversion server by this app.

Last updated: 18 July 2026

Local processing

Selected media files are processed in the browser using ffmpeg.wasm and are not sent to our server for conversion.

No account required

The converter does not require sign-in or account data to use the local tools.

Browser storage

Converter preferences and conversion-history metadata may be stored locally on the device.

1. Overview

Vidara MP3 is a browser-based media converter for MP4 to MP3, MOV to MP4, video compression, trimming, audio extraction, and WAV/MP3/OGG conversion.

Conversion runs locally through ffmpeg.wasm. Performance depends on your device, browser, file size, and available memory.

2. Local Data

Media files selected in the converter are loaded into the browser and processed locally. This app does not upload those files to a conversion server.

Small preferences such as PWA install prompt dismissal, default audio bitrate, video preset, and download preference may be stored in browser localStorage until cleared. A local conversion history stores only result name, operation, format, input/output size, time, and completion status.

We do not persist selected media files, converted media files, or temporary object URLs in localStorage or conversion history. You can remove individual history entries, clear history, or use the converter's “Clear all local data” control to remove Vidara MP3 converter preferences and history.

3. Technical Data

The service worker stores the app shell and FFmpeg engine files in the browser Cache Storage so the app can work offline after those files have been cached. This cache remains on the device until the browser clears site data or a new app version replaces it.

Hosting providers may process standard server logs such as IP address, user agent, requested URL, and timestamps for security, troubleshooting, and operation.

4. Third Parties

FFmpeg core JavaScript and WebAssembly assets are served from this app's /ffmpeg path, not a third-party CDN. Selected media files are not sent to a conversion server.

If analytics, ads, authentication, or other third-party services are added, this policy will be updated before those services are enabled.

5. Security

Avoid processing sensitive media on shared devices. Browser downloads, localStorage, and the service worker cache may remain available to other users of the same browser profile until site data is cleared. Use reasonable security practices when deploying or extending the app.

6. Changes

Update this policy whenever your application changes how it stores, processes, or shares data.

7. Contact

For privacy questions or data-related requests, contact Nasution Corporation at rivaifnasution@gmail.com.