[leppr]

> I went looking for solutions and found some interesting options - but most of them required me to give up my bank and brokerage login data. For me this was a non-starter. I was just not comfortable entrusting a company with that sensitive information no matter how well intentioned they were.

Your app is on a kind of privacy/security middle ground because the portfolio data seems to not be client-side encrypted, which is something privacy conscious users look for.

At the same time I understand data entry is manual?

If I'm going to go through this trouble I would rather have the whole privacy package keep my consolidated portfolio information to myself (which I know is valuable, actionable information. There's a reason most portfolio apps are free without ads).

Overall, I think your landing page doesn't sell your product really well. There are already many portfolio apps. If the big advantage of your app is the breadth of the investment types it support, this should be emphasized more.

[ngburke]

You are correct, the data is not client side encrypted. Data entry is either manual, or for many major brokerages we offer a drag/drop import of CSVs. There is also a generic CSV upload capability.

Good valid points here though on being in the privacy 'middle ground'. There is some trust involved with having your transaction data live on our server, and that we execute correctly on our promise of only extracting transaction data from the (optional) CSV upload process.

Your comments have sparked some ideas on how we could go deeper in the privacy direction, so thanks for taking the time!

EDIT: Noted on the landing page having more emphasis on the full asset type support, thanks for the feedback.