How Video Processing Works
When you choose a supported MP4 or MOV, Brum makes the file available to browser APIs so it can inspect the video track, decode frames, and create forward-and-reverse motion.
Processing and verification run locally on your device. The source file is unchanged, and the finished result is a new silent H.264 MP4.
Exact-duration targets may trim the final emitted frame so the finished file still matches the duration you requested.
Information Handled by Brum
Video files
Source videos and generated results are held by your browser for preview, processing, saving, or sharing. Brum does not intentionally upload them to a server.
Accounts
Brum has no account system and does not require personal profile information.
Media storage
Brum has no cloud media library. Temporary browser object URLs are released when they are replaced or when you leave the workflow.
Inputs are limited to 50 MiB and generated outputs to 200 MiB. Processing retains one decoded range at a time, limited to 8 frames and 32 MiB of pixel storage.
Your Files and Third Parties
Saving writes the result through your browser. Sharing opens the device share sheet only when the browser supports local file sharing and you choose that action.
Security and Local Processing
Local processing reduces the need to transfer media, but browser and device security still matter. Keep your browser updated and review the destination before sharing.
Changes to This Privacy Policy
This page will be updated if Brum changes how it processes media or handles information. The date above identifies the current version.
Contact
Questions and reports can be opened in the Brum GitHub repository.