The goal is to make screen-sharing feel safe again without adding steps to a demo.
Everything runs locally—regex + entropy heuristics compiled to WASM—and the extra CPU cost averages ~1 ms per mutation on my M1.
Custom rules can be added with a JSON file for teams that have proprietary token formats.
visit https://entropysec.io
Feedback please <3
pinkmuffinere•1d ago
- I can't tell what this is until I scroll "below the fold" (ie, below the first visible screen). I think your tagline just needs to be clearer. Even your first sentence in the post here could be a decent description ("Entropy, a small Chrome extension that spots API keys, tokens, emails, and throws a blur overlay on them in real time")
- I'm not very comp-sec minded. I've never in my life worried about leaking API keys, tokens, email addresses, etc via screen share. I have worried about leaking bookmarks, sensitive email drafts, slack messages, etc. But I also don't think I care enough to pay for something that blocks those. Hopefully there are people that do care enough to pay
- An idea for a possible pivot: Ad agencies sometimes want to show how much money or traffic they bring in for clients. Made up data isn't convincing to close a sale, but real pages can have sensitive data like company names, logos, ad spend, etc. With a slight pivot, you might be able to provide them something to obscure that info. I only have second-hand knowledge of this problem, so you'd need to verify that they care enough about this -- don't take my word for it.