Thanks! Yes, everything is stored locally in the browser — no backend at all.
And that’s a great idea. I’ve been thinking about adding an export/import option, and encoding the data into the URL hash actually fits the “offline + privacy-first” vibe really well.
I’ll explore it — would be super useful for sharing or backup without requiring any server.
Thanks for the suggestion!
A small suggestion that immediately came to my mind, why not try making it a JSON serialized data and base64 encode it just like JWT. So that it can be shared and loaded effectively.
Just thinking out loud here ;)
This is what I would do too but one problem I think there is a max HTTP URL length
If you look at the traffic, it doesn't send anything (I could test) to its server, and there are entries in browser's local storage.
Have you considered adding an export/import data option? I was actually expecting "Copy link" to have my months worth of event data encoded in the url after the # (so it would never be sent to the server, but means I could share the month with a friend). Just an idea.