About mewvi

Files chosen for local conversion are processed on your device. Their contents and filenames are not uploaded by that conversion flow. The processing engine is loaded from the site when needed.

Local file selections and generated outputs are held by the current page. Refreshing or closing it loses that workspace; keep downloaded results and select the source files again if needed.

Submitting a link sends it to Clyvora infrastructure. The media service contacts the source platform to inspect metadata, discover explicitly requested collection items, and retrieve selected media. That work can involve additional media, thumbnail, and subtitle requests.

Source metadata, job progress, and remotely processed files are stored by the media service so you can return to your queue and download completed results. This is server processing, even when you started it from the same interface as local conversion.

The service’s default retention is 24 hours for remote files and seven days for job and anonymous-session metadata. Temporary files are cleaned up after work finishes, fails, or expires. Deployment settings can affect those limits.

An anonymous session cookie associates remote jobs with this browser. Artifact access is protected by short-lived, file-specific grants. Clearing that cookie can remove your access to previous jobs; Clyvora does not provide an account recovery flow for anonymous sessions.

Theme and output choices are saved in this browser’s local storage. Local files are not saved there. The application cache holds site assets and conversion runtime files; API responses and downloaded media are excluded from the general application cache.

Hosting infrastructure and source platforms also handle network requests under their own policies. For implementation details, see mewvi’s network documentation (opens in a new tab).