Firstly, from a philosophical perspective I am at no point exposing emails of subscribers to the blog owners. The communications they send to those subscribers are limited to what's published in the RSS feed (once per new post).
As for in terms of infrastructure and app design, I contemplated the idea of implementing some kind of encryption or email alias system for a while, but ultimately decided against it. Some basic reasons are the ones also shared in the answers to this question on Stackoverflow:
https://stackoverflow.com/questions/767276/what-is-the-best-...
Since there is no direct access to emails via the logged in user's interface nor is there any kind of public or semi-public database access (through for example an API – the app is entirely server-side rendered), I already limit the damage that can be done through spoofed or stolen credentials (everything from a stolen password to a spoofed or stolen auth cookie).
The database does store emails of course, but the db is isolated from the application on a different server. At launch I used a Heroku hosted database but I'm planning to provision a database environment that is only open to private network IP access.
I'm also definitely interested in beefing it up further. Any advice?
