It would only be easier to find security problems if someone actually audits your code, which probably won't be free. A good solution is to use an existing ser

It would only be easier to find security problems if someone actually audits your code, which probably won't be free. A good solution is to use an existing service with strong data protections to hold your actual content and then build your service to use authentication tokens with that service. There are lots of options depending on what kind of data you need to store, like Digital Ocean for a SQL instance or Firebase for JSON.