Privacy

Build Extension (https://build-extension.com) builds Chrome extensions from a prompt and, if you ask it to, publishes them to your own Chrome Web Store account. This page says exactly what it stores and what it does with it.

What Build Extension stores

How Build Extension publishes

When you press Publish, Google shows you its own consent screen. The access token Google returns is held only in memory for that single publish — Build Extension uploads the package and publishes the item by ID with it, then discards it. No refresh token, and nothing reusable, is ever stored. Every publish asks for consent again. The listing itself — description, screenshots, category, privacy and distribution — you complete in your own dashboard; Build Extension generates the text for you to paste.

What Build Extension never does

How long it is kept

Your account, your projects and the files generated for them are kept until you delete them. Your Publisher ID and item IDs are removed the moment you press Disconnect or delete a project, and when you delete your account.

Deleting your data

Press Disconnect on the connection page to forget your Publisher ID. Deleting your account removes the account, its sign-in sessions and its stored store identifiers. The generated project files are kept on disk unless you ask us to remove them — write to support@ext.svyat.site and we will.

Third parties

Build Extension talks to Google (sign-in, and the Chrome Web Store when you publish) and to Anthropic's Claude models, which write your extension's code and its store listing text. Your prompts and your extension's manifest are sent to Claude for that purpose. Nothing else leaves this server.

Contact

support@ext.svyat.site


Build Extension · Privacy · Terms · Support · support@ext.svyat.site