Building an app I don't want to ship

Is it incorporation for liability protection?

Terms of service docs that state nothing is hack proof?

Getting the right liability insurance?

In depth penetration tests prior to launching and continuously thereafter?

Continuously monitoring for suspicious activity on a server to detect hacks?

Instead I've been exploring a strange idea of using sqlite client side. People would save their data to a sqlite file that gets downloaded, then when they come back, drag the file back onto the browser to pick up where they left off. A little awkward, but 100% client side, side skirting most of the problems.

(I realize hardly anyone would bother to use this app. But making it public with sqlite is really just an experiment. I host the app on a raspberry pi inside our home network and we use it that way.)