The only way to prevent data from being abused is to prevent it from being collected in the first place.
Privacy Browser has two primary goals.
- Minimize the data that is sent to the internet.
- Minimize the data that is stored on the device.
In contrast, privacy sensitive features are disabled by default in Privacy Browser. If one of these technologies is required for a website to function correctly, the user may choose to turn it on for just that visit. Or, they can use domain settings to automatically turn on certain features when entering a specific website and turn them off again when leaving.
Privacy Browser PC is currently in an alpha state. Users are encouraged to read the Handbook (press
F1 inside the program). It has many missing features, but it has become usable enough for those who like to live on the edge. Bug reports and feedback are appreciated. Users should expect that all of the features currently implemented and planned for Privacy Browser Android will also be implemented in Privacy Browser PC. There is no need to submit a bug report for these missing features as I will add them as they get closer and I have a better idea of how I will implement them. However, please submit a bug report for any of the existing features are not functioning well.
The Git repository can be cloned by running the following command:
git clone https://git.stoutner.com/
Privacy Browser PC is developed using KDevelop with CMake. Assuming you have both installed, as well as the standard Qt and KDE Frameworks libraries, you should be able to open and build the project using the included
PrivacyBrowserPC.kdev4 file. The list of the needed development libraries can be seen in the main CMakeLists.txt. There is a list of Debian packages needed to build Privacy Browser in the Debian control file.
Technical support is available on the forums.
Privacy Browser development can be followed at https://fosstodon.org/