The basic idea: people often sit in rooms waiting for specific moments (private mode, ticket shows, certain goals, certain phrases). ReadyLive watches the rooms and alerts you when your triggers happen, so you don’t have to wait around.

What I’m most focused on right now isn’t growth or features, it’s privacy and security.

Privacy-first by design

I intentionally built this so it’s usable without giving up personal data: • no ads, no tracking, no analytics tied to users • you don’t need a real email (fake emails work fine) • no viewing history, no behavioral profiles • as little stored data as possible (the goal is: even if someone got the DB, there’s not much to learn)

I’m not looking for a full audit or free work, more like: what obvious security problems am I missing?

If you were threat-modeling something like this: • where do privacy leaks usually happen in systems like this, even when you try to avoid storing data? • any common gotchas with letting users define triggers (even with strict limits)? • does using Telegram for notifications change the threat model in ways people often underestimate? • what would you try to break first?

I’m trying to sanity-check the boundaries early, before complexity creeps in.

Link: https://readylive.io

Happy to answer any questions or share details if that helps.