Privacy notes
The short version: your files never leave your device. The longer version explains what that means in practice.
Files are processed on your device
Every operation — conversion, compression, resizing, PDF work, archive creation — runs in your browser using local CPU and memory.
Files are never uploaded for processing
SnapConv has no conversion API, no upload endpoint, and no server fallback. Selecting a file does not send it anywhere.
Files are not stored after you leave
The queue lives in memory only. Closing or refreshing the tab discards the files, their previews, and the results.
Generated files stay on your device
Downloads are produced locally from the verified artifact your browser just encoded.
What SnapConv does not collect
- File names or paths
- File contents or extracted text
- Images, documents, or generated output
- Sensitive metadata inside your files
Analytics boundaries
SnapConv is built with a typed analytics allowlist limited to coarse product signals such as page opened, tool selected, and processing outcome, with count and duration buckets. If analytics are ever connected, they are constrained to that allowlist: no session replay, no automatic DOM capture, no file contents, names, exact dimensions, hashes, or raw error payloads. This release ships with no third-party analytics provider connected.
Your workspace
There are no accounts, no cloud storage, and no synchronization. Anything you drop into SnapConv exists only for the current tab, and removing a file from the queue releases it from memory.