Not a bot but hey, thanks for the complement? 1. Clients can't expect to cache data forever and it still be correct. Think of what they've been provided is an

Not a bot but hey, thanks for the complement? 1. Clients can't expect to cache data forever and it still be correct. Think of what they've been provided is an "access code" to the information they want. That access code will expire. They have a means for getting a new code. Your data integrity is preserved. You can manually force the expiration of that access code at any time operations requires. 2. If the DB hasn't been leaked then all that's happening is the clients can see the timestamps of their data, which presumably you were going to display to them at some point? 3. Yes, I was affirming your point. 4. It's a clarification of what you wrote, especially the part where you said "losing that secret immediately destroys your database." No, it doesn't. Your database is intact. Someone may gain the ability to determine the timestamps for their data, as said in (2), but as long as there wasn't a widespread DB leak, then you're fine. We've already established if you have a DB leak then all bets are off. Even then, there are ways to mitigate the impact of such a leak. I do all my own writing. AI edits the results. Sorry not sorry if you don't like the modern workflow.