Last updated August 28, 2026

M4A to MP4 converter privacy policy for local files

How selected media, temporary browser data, hosting requests, support messages, and external links are handled.

Privacy for M4A to MP4 media files and downloads

Media selected in the converter is processed locally by WebAssembly in the browser. The application does not post the source media or finished result to a conversion server, create an account library, or retain a server-side conversion history.

During a session, the browser creates temporary in-memory files and object URLs so the converter can process and download results. Removing an item revokes its result URL. Closing or refreshing the tab clears the current application state, although a file already downloaded remains wherever the user saved it.

Technical data used to deliver the free online converter

Like most websites, the hosting layer may receive standard request data such as IP address, browser user agent, requested path, referrer, time, and response status. This information can be used for availability, security, abuse prevention, and aggregate performance diagnosis.

The current converter does not require advertising cookies, an account cookie, or a media-upload identifier. If analytics or hosting configuration changes in the future, this policy should be updated before the new collection begins.

Browser storage and M4A converter settings

Current queue items and conversion settings are held in page memory rather than saved as a persistent conversion history. The site manifest and static files may be cached by the browser or network layer to improve repeat loading, but those assets do not contain a user's selected media.

Users can clear browser cache and site data through their browser controls. Private or incognito browsing may reduce persistent local traces, but downloaded files still follow the device's normal download behavior.

Support email privacy for converter questions

Messages sent to support can include the sender address, message content, and mail-system metadata. Do not attach private media merely to report a conversion issue. A reproducible description, public sample, source format, browser version, file size, and error text are usually sufficient.

Support messages may be retained as needed to answer the request, maintain an abuse record, or document a technical correction. They are not a substitute for an encrypted file-transfer service.