Comment by bradly | Hacker News Reader

Comment by bradly | Hacker News Reader

Parent Full thread

> Definitely open to feedback here!

Sure.

Know your audience. HN users are going to be focused on two things: how the your browers data is used and how you stop an agent from taking account numbers, inputted passwords, etc.

From the linked privacy policy:

   > Share data with third parties except our API service

It would be helpful for you to share the privacy policy of the API service as well.

   > When you use our script generation functionality:
   >    Generated Code: We retain rights to use, modify, distribute, and commercialize any scripts generated by our service
   >    Sharing Rights: Generated scripts may be used to improve our services, shared as examples, or incorporated into our script library

Anything you make is or can become public. I would revisit this decision and prioritize keeping users' data private.

Also, I would encourage you to understand your technology, even your marketing site, to be able to add a link to Privacy Policy and ToS in the footer without the burden of "an entangled mess of state machine" and the risk of breaking anything. If the marketing site technology is outside the scope of your expertise, consider how much worse would a static page would be?

> It would be helpful for you to share the privacy policy of the API service as well.

We have standard data processing agreements with any and all LLM providers that we use. These include do not train/retain provisions (whether you trust them is another question entirely).

> Anything you make is or can become public. I would revisit this decision and prioritize keeping users' data private.

Totally valid. We haven't acted on this clause (scripts are not shared unless your yourself enable sharing) so probably best to remove it. To be clear though, your page data is your own. That will never be shared (not even you yourself can opt to share that because the privacy concerns are too great). The generated scripts are much safer (generally boils down to a bunch of static CSS selectors, styles, etc.). Nonetheless, a valid point.

> Also, I would encourage you to understand your technology, even your marketing site, to be able to add a link to Privacy Policy and ToS in the footer without the burden of "an entangled mess of state machine" and the risk of breaking anything. If the marketing site technology is outside the scope of your expertise, consider how much worse would a static page would be?

Fair comment, fwiw we did ship it in the footer already :) For the standard site, when the extension is installed, there are 6 steps. Each step dynamically progresses based on your install state (installed, pinned, permissions granted, first generation, etc.) We put a lot into the onboarding experience and it is pretty complicated (happy to geek out over the details!), but we hide all this if the extension isn't actively installed. Unfortunately, my blunder was that one of those steps that was hidden includes the privacy policy.

Thanks for all the feedback!

Indeed.

> Instead of digging through selectors and hand‑writing custom JS/CSS

Some of us like that or at least the exact control it gives us Vs installing an extension that has access to my entire browser infrastructure and those terms.

I suspect many HN readers aren't the target market for this.

And that is totally fair!

I enjoy having control over my browser, as well. So much so that I built an extension that could help me with it :)

I didn't build this so I could make money, it was a side project that I tinkered with (after YC). I shared it with a few friends, they thought it was cool, their friends also thought it was cool, and it grew from there.

It's okay that many in the HN audience don't necessarily resonate with "Instead of digging through selectors and hand‑writing custom JS/CSS". At the very least, hopefully I inspired someone else to play with this idea. I personally think it is very cool and beneficial for the web!

Reply on news.ycombinator.com