In order to use this, I would have to give a lot of personally identifiable information. The privacy policy basically gives Leaky the right to do whatever they want with my personally identifiable information, such as providing an unlimited set of third parties for "internal business purposes," an unlimited number of present or future affiliates which they will "seek to require" to adhere to the privacy policy, to anyone who may purchase the company or its assets, or for a fairly extensive list of fraud and law enforcement reasons, to disclose it to an unspecified set of entities.
On top of that, there is no limitation on how long Leaky will hold such personally identifiable information, nor any information about how to get Leaky to remove it. So basically, once I enter information into Leaky, they may hold onto it forever and sell it to whoever they like for quite a wide variety of reasons, with no recourse for the user to protect their information.
I don't think that I would ever want to put such personal information in a service with such a weak privacy policy. And given the new model, in which this is just an implementation of the complex pricing structures used by auto insurance agencies, I wonder why this couldn't be made into an application that runs locally and never exposes my personal information to anyone else. Yes, you would probably have to go with a paid application, rather than an ad-supported web site, with all of the problems that entails, but for a product like this with such important privacy concerns and such little value (to the customer) to putting the data online or sharing it with people, it really seems like it would make more sense as an offline application, not a web app.