Trinity

How does a Password Manager work then, if there is no actual storage of a password?  The only details you need to know are in your head to generate that same password when you need it later.  The reason the program is called Trinity, is because a user only needs to remember 3 things to generate a repeatable password each time.  Here's how it works:

The first thing is the TIN, also called the Trinity Identification Number.  This is similar to a personal PIN code, it is used as a component to generate the same password over and over.

The second thing an end-user needs to remember is a passphrase of sorts called the PIP, or the Personal Identification Phrase.  This can be a long sentence that only that user knows, it could be a favourite quote, or anything.

At this point, you might be asking yourself, why this sounds extremely exhausting to remember all of these things for as many different passwords I need to keep track of, it's much easier to just use an encrypted wallet.

This is where things actually get more interesting from this point, you see both the TIN and PIP are meant to be shared between all of your password you need to generate.  So, the end-user only needs to remember one TIN and one PIP, and that's it.

The final and third thing an end-user needs to remember is the SPN, or otherwise called the Specific Password Number.  This is the unique number that identifies a very specific password.  It's best to think of a set of unique numbers that aligns with the account or service in someway to better remember this number.

One very interesting and unique aspect of this, is creating a very powerful and universal corporate password sharing system!  Here's a use-case example to whet your appetite for this software's potential in a large scale work environment, where at least a couple accounts need to be shared between a bunch of administrators.

Firstly, the TIN, the Trinity Identification Number would act like a full password rotator, so when the time comes to change all the passwords on all the associated accounts, update this number to a new one, and use some sort of automated tooling to perform the task.  The PIP, or the Personal Identification Phrase is then also shared with the people who need these passwords, and this special phrase would change when an employee leaves the company, and the same automated tool could go through all the systems to perform the password update.

Each Administrator can then easily jot down, or remember each of the account's SPN, or Specific Password Number.  The Pro version I was thinking of actually releasing one day actually includes an embedded SPN encrypted storage vault.  This allows the SPN to be safely stored in an encrypted form, but nothing else.  Upon opening Trinity, the end-user is still expected to provide the full TIN and PIP to use the locally encrypted SPN vault.  This can allow administrators within an organization to easily storage this critical number, and even share it among their co-workers who also need access safely.  If an employee has a local copy, once they leave the company, as the aforementioned PIP is changed, as I recommended above, then the local SPNs that this employee might still have are now completely void and useless.

If you are either an investor, or a corporation who does see value and potential in such a product, let's talk!  You can DM me on LinkedIn.  Let's make the password, where they might still be required more secure together!