unflicker collects nothing, sends nothing, and has no way to reach the network even if it wanted to.
There are no accounts, no analytics, no telemetry, no advertising identifiers and no crash reporting of our own. Nothing about you or your machine is gathered, stored remotely, or shared with anyone.
The Mac App Store app runs in Apple's sandbox, and it does not request
com.apple.security.network.client, the entitlement macOS requires before an
app may open an outgoing connection. Without it the operating system refuses the
connection, so this is enforced by macOS rather than by our good intentions. You can
check for yourself with codesign -d --entitlements - against the installed
app.
Your settings stay on your Mac, in the ordinary places macOS keeps an app's preferences. Nothing is uploaded, synced or backed up to us, because there is nowhere for it to go.
To list your cameras and set the control, unflicker reads the USB descriptors each camera publishes about itself: its vendor and product id, its product name, and the control values and ranges it supports. That happens entirely on your Mac and none of it is transmitted or retained.
unflicker never opens a video stream. It does not request the camera entitlement, and it cannot see, capture or record what your camera is pointed at.
If you have opted in to share analytics and crash data with developers in your privacy settings, Apple may give us anonymised crash reports for the App Store build. That channel is Apple's, is controlled entirely by your own setting, and is governed by Apple's privacy policy rather than this one. We collect nothing through it beyond what Apple chooses to aggregate.
If this policy ever changes, the updated version appears on this page. Questions are welcome on the issue tracker.