- First add a security page, I need to know you're doing basic things like encrypting the data on your end etc. Hopefully you're using at least something like KMS for your at-rest encryption (all DBs and disks) if using AWS.
- Then also publicly state on the security page something to the effect of "No Pry employee has the ability to access customer data without your explicit approval, and all access is audited". Meaning, if you need to work a support case for some customer, you have to ask them before you look at their data, and you have to track when this access occurs
- Ultimately you'll get something like a SOC2 cert to show that you actually have these controls in place that you say you do
I think with this, you'll be able to overcome some of the fears. Native apps is a shrinking market and a distraction for you IMO. Your customers are already fine with cloud solutions, since they're using Quickbooks Online, Xero etc. by definition, you just need to convince them you're trustworthy as well.
- Pry knowns my transactions, so they know who my customers are, and how much I'm charging them. Maybe one of my competitors could bribe a Pry employee to divulge this information. Same for suppliers, etc. Maybe not important for B2C SaaS, but for many companies this is a real threat.
Is it possible for Pry staff to do any actions in the accounts such as withdraws?
Does third part access void TOS with banks that have protections in place?
If Pry is sold to another company, how is data transferred to the new company? Does the end user have the option of preventing the transfer?
I don't mean this as a giant joke, but where do you find these accountants?
I'm not saying that they don't try to, but things that would be major security no-no's to people on HN are often a regular part of business for others (emailing photocopies of 'secure' documents, copy/pasting passwords, etc).
I saw a tweet recently to the effect of "I'm not sure who I'd rather have my data, a giant megacorp or a startup with 5 employees who can query the DB from their laptop." I think this is a good example of that.
I would use this if it included encrypted data storage with client-side computation, and/or was self-hostable (you can still charge a license fee!)