Mixed JPG, PNG, and WebP batch
- Build
- 1.0.7.0
- Tested
- August 2, 2026
- Result
- 12 of 12 completed; sources retained; one already-optimized PNG copied byte for byte.
LocalFlux Trust Center
What happens to your files and how to verify it
LocalFlux processes supported files on your Windows PC. Normal conversion, compression, and privacy-safe image processing do not upload your source or output files to Fuzzysense. No LocalFlux account is required, and the app does not send usage analytics or remote crash reports during normal use.
The short version
- Files stay on your PC
- Supported jobs use local conversion components and write results to a local folder you control.
- No account or app telemetry
- Normal use requires no sign-in and sends no usage analytics, advertising identifiers, or remote crash reports to Fuzzysense.
- Originals stay intact
- Documented workflows create new, collision-safe output names instead of overwriting or deleting the selected source.
- Offline after installation
- Normal supported conversions can run without an internet connection after Microsoft Store installation and licensing are complete.
The file-processing boundary
Adding a file, choosing an output, running a supported job, and writing the result happen on the Windows device. There is no upload stage in this processing path.
1 Source file on your PC
2 LocalFlux
3 Bundled conversion engine
4 New output file on your PC
Store traffic is separate from file processing
The statement “processed locally” describes the file route, not every network activity that Windows may perform.
- Microsoft Store
- Installation, purchase validation, licensing, updates, payments, and other platform operations may use Microsoft services under Microsoft’s policies.
- Links you open
- Opening the privacy policy, support address, or another web link can launch your browser and connect to that destination.
- Your files
- Those platform and browser activities are separate from LocalFlux’s conversion path. LocalFlux does not provide your selected source or output files to the Store for conversion.
Privacy, telemetry, and local diagnostics
During normal LocalFlux use, Fuzzysense does not receive a usage stream from the app.
- No account
- You do not create a LocalFlux profile, provide an email address, or sign in to run normal supported jobs.
- No file upload
- Fuzzysense does not receive the source files or converted files through the app’s normal processing workflow.
- No usage analytics
- The app does not send usage analytics or advertising identifiers to Fuzzysense.
- No remote crash reports
- Crash and conversion diagnostics are not automatically transmitted to Fuzzysense.
What may remain on the device
LocalFlux may store settings, output preferences, window placement, local conversion-failure records, and local crash logs so the app can work and be troubleshot. This information remains on the device unless you deliberately choose to share it. You can remove outputs, clear app data, delete local logs, or uninstall the app, subject to normal Windows behavior.
Bundled conversion engines
LocalFlux includes the components needed for its supported routes, so normal work does not depend on a cloud conversion service or a separately configured command-line installation.
- ImageMagick
- Handles supported image conversion and image-optimization work.
- FFmpeg
- Handles supported audio, video, animation, and audio-extraction work.
- LibreOffice
- Handles supported office-document conversion routes.
Third-party notices and licences are included with the app. Engine availability does not mean every possible format or conversion is supported; the Formats directory lists the routes LocalFlux exposes. Formats
Original-preserving outputs
LocalFlux is designed to leave the selected source in place and publish the result as a separate file.
- Converted, compressed, optimized, and privacy-safe results are written as new copies in documented workflows.
- Output names use an operation suffix and collision-safe naming when the intended name already exists.
- The source is not silently overwritten or deleted by the documented workflow.
- You can save beside the source, choose a fixed local folder, or be asked for a destination, depending on your settings.
Creating a separate output protects against an accidental overwrite during this operation. It is not a backup strategy. Keep independent backups of irreplaceable files.
What “verified lossless” means
Verified lossless is a result contract, not merely the name of an encoder setting. LocalFlux 1.0.7 uses a fail-closed workflow for supported image routes.
- Create an optimization candidate locally.
- Check the format-specific content invariants. Depending on the format, these can include decoded pixels, every rendered animation frame, TIFF pages, dimensions, timing, loop count, or geometry.
- Check the supported embedded metadata that the route commits to preserve.
- Publish the changed candidate only when the checks pass and the candidate is actually smaller.
- If the candidate is not smaller or cannot be verified, write an exact copy of the source under the expected new output name and report Already optimized.
“Verified” refers to the explicit content and metadata invariants checked by the named LocalFlux version for its supported routes. It is not a claim that every conceivable property of every file format has been mathematically proven equivalent.
Verify offline processing yourself
Use a synthetic or otherwise non-sensitive sample. Do not begin with an irreplaceable file.
- Install or update LocalFlux from Microsoft Store.
- Launch it once while connected so Store installation and licensing can complete.
- Create or download a non-sensitive sample in a supported format, such as a small PNG or WAV file.
- Disconnect Wi-Fi and Ethernet, or enable airplane mode.
- Open LocalFlux, run one supported conversion, and choose a local output folder.
- Confirm that a new output file was created and that the source still exists.
- Open the result locally, then reconnect when you are finished.
For a stricter review
An IT reviewer can watch the LocalFlux process in Windows Resource Monitor or temporarily block that app’s outbound traffic with Windows Firewall before repeating the sample conversion. Record the app version, input hash, output hash, and final file sizes with the test.
Windows, Microsoft Store, antivirus software, browsers, and other background processes may attempt their own network activity. Attribute traffic to the responsible process; do not treat unrelated Windows traffic as LocalFlux file processing.
Published evidence
These records use synthetic, rights-cleared inputs and the live Microsoft Store build. They document the tested version, exact bytes, hashes, screenshots, and important scope limits.
Verified-lossless GIF and exact-copy PNG
- Build
- 1.0.7.0
- Tested
- August 2, 2026
- Result
- GIF frame signatures and timing matched; the fallback PNG had the same SHA-256 as its source.
A precise promise, kept reviewable
This page describes the current LocalFlux trust model and names the builds behind the published evidence. If telemetry, network behavior, bundled engines, output handling, or verification logic changes, this page and its evidence record must be reviewed again.