Built for developers.Ready for their agents.
One repository, every browser that takes an extension.
Platform details
Jump to a section
Get started | |
Tools | |
Plans | |
Frequent questions |
What extension.dev collects, why, and the control you have over your data.
Last updated: November 6, 2026
extension.dev is built and run by one person, Cezar Augusto. This page explains, in plain English, what data the platform collects, why, and what you can do about it. It covers the hosted platform at extension.dev. The open-source Extension.js CLI has its own telemetry note in the docs.
A handful of vendors process data on my behalf so the platform can run. They only use it to provide their service to me:
This section covers the Chrome Web Store connection. It says what I take from Google, what I do with it, who can reach it, and how it is deleted.
https://www.googleapis.com/auth/chromewebstore) and the email of the Google account you picked. I show that email in your settings as “Connected as” so you know which account is linked. I do not access Gmail, Drive, Calendar, contacts, or any profile data beyond that email.I keep your account and project data while your account is active. Drafts, generated artifacts, and analytics are kept on a rolling basis. A Google refresh token is kept only while the Chrome Web Store connection exists; it is revoked at Google and deleted when you disconnect, and deleted with the project or workspace that held it. You can ask me to delete your data at any time. Just email hello@extension.dev.
Depending on where you live, you may have the right to access, correct, export, or delete your data, or object to some processing. To do any of that, email hello@extension.dev and I’ll take care of it.
The vendors above may process data in the United States and elsewhere. Where required, transfers rely on appropriate safeguards.
Anything about privacy: hello@extension.dev.
One repository, every browser that takes an extension.
Jump to a section
Get started | |
Tools | |
Plans | |
Frequent questions |