The challenge, for me, with a service like this is security. To effectively search all of my personal information, this service will need creds to see all of my personal data.

That makes this service a tempting target for attackers.

From an initial read through the ToS and Privacy Policy I don't get the impression that they're going for a zero-knowledge model where data is processed on a client, so that means that their server-side apps will need to access/process my personal data as part of provision of the service.

Now I have no reason to doubt their committment to security, however I also don't have a great deal of information that would allow me to say "yep this looks like somewhere I want to trust with all my personal details"

One recommendation I would make to the team, is provide a bit more information about the steps you're taking to secure data processed on this service and also talk about the third party assurance that you're getting over those controls.

Also (personal peeve perhaps) but that bit on the front page about "industry standard encryption" isn't really useful. TLS won't save me if the web app. has SQL Injection :)