Thank you I find all your answers satisfactory.
As far as implementing e2ee look at cryptpad.fr they use a system where they encrypt the data locally and share the key with the link.
For example if you wanted to do this with location data you could encrypt with AES locally the location data. The key to decrypt that would be in the link. The site would automatically decrypt the content. The only data moving across the servers would be encrypted. The site would still have to be trusted to deliver trustworthy decryption code of course.
However, considering mobile distribution system is a much harder system to target an individual with. If the app could be used to see someone's beacon(probably given a random id) you could decrypt with the app.
At this point all you would have to do is trust the code of the app. You would assuming you didn't have any backdoors in the code would have zero access to data ever. Once the mobile app was shipped out you would have a zero trust system you could be forced by any bad actors to turn over data(say a state) and have no access to user data even if you completely had to turn over your server.
Fully zero trust as in not trusting the middleman(you) is very possible. It would be allowing users to build their own app from source to use the service which generates the id/link + keys. It could pair nicely with something already zero trust like Signal to share the id/keys.
E2EE is fully possible for something like this and could greatly lessen the importance of even need for TLS on the site.
I do think it is great what you are doing and thanks for taking the time to chat with me and explain your software
"The tracklog is NOT saved in this free version, just the last beacon!
You need to get the PRO version if you need the whole tracklog."
This feature I assume was removed and it is still mentioned on the Google Play link.
https://play.google.com/store/apps/details?id=com.emilburzo.graticule