Privacy Policy

1) No uploads or server-side processing

Audio conversion is processed locally with WebAssembly. Your files are not uploaded to our servers for conversion, and we do not store copies of your audio.

2) Cookies & consent

In regions where prior consent is required, we show a consent banner so you can decide whether to allow analytics and advertising cookies. In regions where prior consent is not required, these services may load by default. Essential cookies are used for basic site functions, such as remembering your consent preferences.

• Necessary: required for core functionality.
• Analytics: used to understand site usage and improve features (Google Analytics, Ahrefs).
• Advertising: used for ad delivery and performance measurement (Google AdSense).

You can change your choices at any time from Cookie settings.

3) Vendors we use

• Google Analytics (GA4): enabled after consent where required by local rules, or loaded by default where prior consent is not required. Google policies: partner sites.
• Ahrefs Analytics: additional usage metrics, enabled after consent where required by local rules, or loaded by default where prior consent is not required.
• Google AdSense: ad services enabled after consent where required by local rules, or loaded by default where prior consent is not required. Learn more: Google Ads & cookies.

We use Google Consent Mode v2 so your cookie settings control how Google services behave.

4) Third-party libraries (client-side only)

The app uses browser-side libraries such as FFmpeg (WebAssembly) and JSZip. These tools run locally in your session. Audio content is not sent to third parties for conversion.

5) Data retention

We do not retain converted audio files on our side. If you allow analytics or advertising cookies, those providers may process pseudonymous data under their own privacy policies. You can withdraw consent at any time from Cookie settings.

6) Anonymous technical error logs

To diagnose conversion problems, we may store anonymous technical error events when a conversion fails. These logs can include the input format, selected conversion settings, target output format, a sanitized error message, and coarse device capability data such as device class (mobile/tablet/desktop), OS family, browser family, approximate memory tier, and screen size class.

We do not store audio content, file names, local file paths, full user-agent strings, IP addresses, or other direct personal identifiers in these technical logs.

Logs are kept for troubleshooting and can be manually removed when related fixes are deployed.

7) Children's privacy

This service is not intended for children below the age required by local law. If you think a child has shared personal data, use available privacy settings and local parental controls.

8) Changes to this policy

We may update this page as the product evolves or legal requirements change. When that happens, we update the date shown at the top.

9) Useful links

For more context, you can visit About, check practical settings in the Blog, or go back to the main converter.