HNHacker News
TopNewBestAskShowJobs

hashbrown490

1 karma · joined May 20, 2025

submissionscomments
hashbrown490··on The Fall of Roam (2022)
Baibhav posted this screenshot down the thread, but I wanted to add some more context.

We followed up with our ex-employee to get the final (cutoff) message in this email thread https://firebasestorage.googleapis.com/v0/b/firescript-577a2...

In it he tries to explain that these are help graph transactions they are seeing. I do apologize if you didn't understand it at the time, but we did try to explain it to you. I Hope this clears up everything for anyone following along.

hashbrown490··on The Fall of Roam (2022)
Thanks for sharing, see Baibhav's response for what happened here, these logs you are seeing are for the public help graph, not your personal graph.
hashbrown490··on The Fall of Roam (2022)
Hi, co-founder of Roam, Josh here. I don't recall your case ever being brought up to me, but as Baibhav said in his comment, we have strict no-access rule for engineers. They (and me) are only allowed to open your graph if given explicit permission by you through support. We have always had this rule and it's in our terms and conditions.

I think I found your account and I don't see any access logs to your graph from anyone other than your account. If you can provide any more info or screenshots of we would be able to dig deeper into exactly what you saw. It could have been a console log or a hard coded employee email in the code.

We've always cared deeply about user's privacy and ownership over their notes. This is why we've had this policy from the start and focused heavily on local first features and data portability. We offer fully offline graphs, where the data never touches our server and is never able to be accessed by anyone on our team. We also offer fully encrypted graphs, which are stored on our servers but are not able to be read by anyone without the password (our team cannot read your data).