Browser extensions are powerful because they live close to your data. That same power makes privacy a non-negotiable design constraint for us.
Minimal permissions
We start every project by listing the absolute minimum permissions needed. If a feature can be built without a permission, we drop the permission. This reduces attack surface and builds user trust.
Local processing
Bookmarks, browsing patterns, and user input should not leave the browser. Our extensions use Chrome APIs to read data locally and perform all computation on-device.
No analytics by default
We do not include analytics scripts in our extensions. Feedback comes from support emails and direct conversations with users.
Open source as accountability
We build transparency into our privacy policy and clear permission explanations, so users always know what the extension does.