Fair points, thanks for pushing on it.
IPs: you're right. We'll drop the raw IP entirely. Creator stats will keep only the iso country code, and view dedupe will run only on the random session ID that lives in memory and dies on refresh already. Nothing persists, nothing linked back to a user before, and now it's even less personal data without the IP.
Cookies: as far as I can tell, we only store settings the user toggles themselves. I'm doing a proper deep dive through the codebase just to be sure. Anything I find that isn't strictly necessary either goes or gets a consent gate.
Data access and deletion: I am adding a button to request an export or a deletion. But the limits are clear: we can delete everything in our own database, but we don't control the Hive blockchain. Users sign and broadcast their own posts with their own keys. We're a front end reading a public ledger. Nothing on chain can be removed by us or by anyone else. We'll say that plainly at signup as soon as it is live so nobody finds out the hard way.
Appreciate your feedback!
RE: Fresh News on 3Speak: Feed Algorithm, Watch Time Tracking and 3Speak Analytics!