Update README.md


Description
===========
Imagine a financial adviser who has multiple clients.
This adviser wants to register an account for his practice with a web service 
that allows him to store and retrieve financial information for multiple clients and support advise he offers them.
In order to fulfill his ethical obligations to his clients, 
this adviser is required to keep the names and identifying and contact info
of each and every one of his clients private.

As the founder and author of this service,
I do not want to trouble this adviser with the burden 
of having to device his own scheme for encoding clients' names 
and having keep them in a separate record that he stores on his 
computer or in his desk drawer.
Doing so would drastically reduce the appeal of this web service to busy professionals,
and increase the risk that persons' identities and contact info 
might be exposed in the case of clients of advisers who do choose to use the service.

Instead, I want this adviser to be able to easily identify each of his clients 
whose financial information he entered into the site 
knowing that he and he alone can view that information.
Even someone with access to the database and a decryption key 
will never be able to see his clients' real names, identifying info, and contact info.

That means that even while I, the founder of the site, 
make a representation in my Terms of Usage document 
that I will never reveal persons' identities or contact info,
If one day I sell the rights to this web service to another party,
I want to sleep at night knowing that 
the new site owner will never be able to access persons' identifications and contact info 
from the data he acquired.