Password Keeper

Almost all services which require some personal data require methods to keep it safe and only provide access to you alone. With all the abundance of such requirements, you might quickly forget details. However, you can use applications like Password Keeper to make sure these are all safe and sound inside a database.

Two types of databases to manage

The application can take care of two things for you, meaning it can save accounts, as well as passwords. Both components are rather similar, both in terms of database design, as well as data input options. However, the accounts category is fitted with less filter options which you find as tabs when exploring databases.
There’s absolutely no entry by default, so you might want to get started and add a few details first. The creation process, including requirement fields are pretty similar, regardless of the category you wish to populate.

Various detail fields to fill in

As such, you need to fill in specific fields for name, developer, workstation license type, category, related to, website, email, phone, contact, and up to six custom fields you can populate with data values like password, user, owner, registration number, unlock code, license number, zip password, and more.
As mentioned before, categories are similar when it comes to database navigation. All entries are shown in a table with column header based on input fields, with additional filter options found as tabs. Additionally, entries can be individually viewed through drop-down menu selection.
It’s also a good idea to pay a visit to the support menu to add an extra layer of security to your database. Here you have the possibility to set up a master password so only you can access the database, and create a backup, just in case something goes wrong.

To sum it up

In conclusion, Password Keeper comes with good intentions, and certainly enough requirement fields to add all details you need to. However, the general layout is rather chaotic and lacks integrity, while there’s no real difference between the two database types.