-
Notifications
You must be signed in to change notification settings - Fork 0
Privacy & Security
Since I'm trying to keep the app small and widely compatible there are already as few and as direct class and function dependencies in the code as possible.
That way I can make sure that there is as little likeliness to any data being grabbed by a third party as possible.
Besides that the only data any version of the app is meant to store persistently are the data sets that make up the binarised camera profiles.
It doesn't need any additional permissions or elevated rights to do its job and is perfectly happy with staying in its own directory.
NO VERSION CONTAINS ANY CODE INTENDED TO EVEN TRY TO ESTABLISH A NETWORK CONNECTION.
Your saved profiles are strictly stored locally in whatever is the "persistent directory" of the app on your device.
I am NOT LIABLE for ANY behaviour of ANY GIVEN FORKED VERSION. I have no control or care over what they do with their fork.
As already stated in Privacy there is no intended way to access anything outside the app's own directory.
Additionally all input fields in all GUI-based versions are suited with input masks and using explicit type declarations to mitigate potentially malicious inputs and thereby preventing this app to be utilized as a gateway into your system.
As of right now the CLI version does not have these protections in place but gladly it will bug out and mess up the entire application anyway if you give invalid inputs.
If you're worried about the safety and privacy your device and data, you can check out Privacy & Security for further information about what data the app gathers, which permissions it will ask for and how it uses both.