Local files & privacy

Shrynk’s product promise is that your source files are not uploaded to us to convert or compress. That is why the desktop app exists, and why the website preview runs in the tab (canvas for stills, ffmpeg.wasm for video) instead of a server encode farm.

Browser preview

• Still images decode and re-encode in the tab with the canvas API. Nothing is posted to a Shrynk upload API. One file, about 25MB.
• Video compress loads JS plus a ~30MB ffmpeg core from dl.getshrynk.com (cached after the first run). Opening the Convert tab does not download ffmpeg.
• The video you drop is read in the tab, encoded there, and saved with a download.
• This site uses Google Analytics (G-E8S3WNCEBV) for page traffic, not for reading your media.

Desktop app

• Convert and compress read/write paths you choose on disk. History (task id, formats, counts, output folder, sizes, errors) lives in a local SQLite database under the app’s AppData folder.
• FFmpeg/FFprobe run as bundled binaries. Calibre, if you installed it, also runs locally.
• License activate / check / deactivate and the update checker talk to the network. They send license and client identifiers, not your videos or spreadsheets.

What we cannot promise

Once you send the output to WhatsApp, Drive, or email, those services apply their own policies. Shrynk only covers the step on your PC. If you need a file to stay offline, do not upload the result either.

Questions: support@soft-sell.com.