Questions

Yes — this is the whole point. Every control writes to the camera over CoreMediaIO, the same path macOS's own UVCAssistant uses. The change is on the sensor itself, visible to every app using that camera, not a layer CamTune adds on top.

No. CamTune never opens a capture session — it only reads and writes hardware control values. There's no video pipeline in the app at all, so there's nothing to see, record, or leak even in principle.

CamTune works with standard UVC (USB Video Class) webcams. Which specific controls show up depends entirely on what that camera's own driver publishes through CoreMediaIO — unsupported controls are hidden rather than shown broken. With only one camera to personally test against, Preferences has a one-click way to send diagnostics so support for more cameras can be added over time.

Not verified. Continuity Camera doesn't behave like a standard UVC device, and it hasn't been tested against CamTune yet.

No — confirmed empirically, not assumed. CoreMediaIO exposes exposure mode as a plain Manual/Auto switch, not the 4-position control some other platforms' drivers expose. CamTune's UI reflects what CoreMediaIO actually reports.

No. Brightness and Contrast are free forever. Everything else is a single one-time purchase — CamTune Unlimited — not a subscription.

No. Every control read and write happens locally between CamTune and your camera. A connection is only used for the App Store purchase itself and optional crash/analytics reporting.

Yes. Every connected camera shows up in the sidebar, each keeps its own profiles, and the menu bar lets you switch cameras or apply a profile without bringing the main window forward at all.