Privacy

Privacy policy

Last updated: 2026

Protecting your data is the cornerstone of BunnyConverter. This policy explains the small amount of information we touch and the safeguards we put in place.

No uploads, ever

Files stay on your device. Conversions run entirely in your browser using WebAssembly pipelines so there is never a reason to move your content to a remote server.

Temporary processing only

Converted assets exist only in memory or as temporary object URLs. Refreshing or closing the tab clears everything automatically.

Transparent permissions

When BunnyConverter requests access to your files, it happens through native browser pickers. Permissions are scoped per interaction and cannot read your filesystem outside the files you select.

We update this document whenever we expand the toolkit or integrate new technologies.

Details

How BunnyConverter handles files

BunnyConverter is designed so selected files remain on your device. When you choose a file, the browser gives the page temporary access to that file for the current interaction. Conversion code then reads the file locally, creates the requested output, and prepares a download in the same browser session.

Temporary object URLs and in-memory results are used to preview and download converted files. Refreshing the page, closing the tab, or starting over clears the active session state. BunnyConverter does not provide cloud storage, remote processing queues, or account libraries because those features would require a different data model.

Some conversions depend on browser capabilities and available memory. If a file is too large or a format is not supported by the current browser, the tool may show an error instead of sending the file elsewhere. That behavior is intentional: unsupported work should fail locally rather than silently upload private content.

All BunnyConverter tools follow the same local workflow: choose a source file, let the browser complete the supported conversion or edit, then download the result. There is no project library to manage and no remote job to wait for. If a browser cannot read a format or does not have enough memory for a large file, the tool reports the problem locally so you can try a smaller file, a different format, or a desktop browser.

Good to know

  • Selected files are processed in the browser session.
  • Converted downloads are created from local results.
  • Unsupported files are not sent to a fallback server.