Both your and Apple's concerns are valid. This change makes the fact (arguably) that these local storages are caches apparent. Some web apps already saw the da

Both your and Apple's concerns are valid. This change makes the fact (arguably) that these local storages are caches apparent. Some web apps already saw the danger of having an easily purge-able storage on the client side and simply implemented an export function for their tools. I admire those tools more than the ones who overuse local storage for everything. One such tool is draw.io, a flowchart maker. You use the app, persist everything in local storage and when you are done, you export your project into a file, all happening on the client side. When you need to edit, you import the file on launch. It's portable, it's protected from browser bugs/decisions and imho pretty user (privacy) friendly.