Add 4 products from PeaFactory

[GrimPixel]

This site has 4 products: File Lock PEA, Calendar Lock PEA, Notebook PEA, Image Lock PEA.
https://eck.cologne/peafactory/en/index.html

[dngray]

I don't see any reason to add these when we have better alternatives.

Additionally they don't appear the be developed publicly, ie with public source repo.

Some of these products also aren't actively maintained.

[Beloumi]

I think Calendar Lock PEA has no good alternative as an offline desktop application.

If you want to manage calendars online, EteSync, ProtonMail and Tutanota are fine, but if you just want to keep the data on the device, there is no other option as far as I know. That doesn't mean the program should necessarily be included.

The repo is at Codeberg: Calendar ;Lock PEA Repo
Note, I have a bias, I am the developer of the Calendar Lock PEA.

[dngray]

but if you just want to keep the data on the device

You can create offline calendars in most apps, as you can with Etar, or Lightning, of the other many calendar programs out there. E2EE is really there to prevent the threat model of your service provider reading your calendar events, if you're not synchronizing it though that's really quite unnecessary.

With Android, there are separate user accounts, so that's one way of keeping local calendars encrypted I suppose.

The repo is at Codeberg: Calendar ;Lock PEA Repo

That repo only appears to have a README and a LICENSE in it.

[Beloumi]

You are right, there are various good offline calendars for all systems, but they leave the data on the device unencrypted.
Of course, this is less problematic than giving this data to a service. In my opinion, it still makes sense to protect calendar data on the device. But perhaps it does not correspond to the intention of privacyguides "Protect your data against global mass surveillance programs."

The code is located in branches (master): branch

[dngray]

they leave the data on the device unencrypted.

Thing is, though you've got robust full disk encryption options, so I don't see what threat model this solves.

With Android, and iOS they those devices require encryption now.

The code is located in branches (master): branch

You should move the LICENSE and README to the master branch then and delete both branches locally and remotely

git branch -d main
git push origin --delete main