There's no way around working with data. Which is why you need to know the difference between the storage options you have. Some data is only used ...
For further actions, you may consider blocking this person and/or reporting abuse
IndexedDB ?
I always view cookies as existing for the benefit of the server, not the client, since it gets passed with every request.
IndexedDB is perhaps the most exciting storage option, and it has many advantages over LocalStorage in terms of storage space, object typing, asynchronous access...the point is, check it out!
Local storage is not recommended for saving authentication tokens. Cookies have the advantage of setting the 'httponly' flag, which means client side code cannot access the value. This can help mitigate the risk of some XSS attacks.
Some more information:
auth0.com/docs/security/store-tokens
owasp.org/index.php/HttpOnly
nice
JSON web token?
The Web Storage API is easy to access, but how do you start baking cookies? Any good tutorials you would recommend?