AI beside the page
AI Chrome Extensions That Summarize, Draft and Extract From the Side Panel, With Your API Keys Kept on Your Server
The quickest way to build an AI extension is to tuck your API key inside the package, where anyone who unzips it can read it. Then every user is running up your bill. A careful build keeps the key on a server, sends only what the user chose to share, and keeps the answer one click away.
November 16, 2026 · 8 min read
The short answer
A custom AI Chrome extension puts an assistant in the browser's side panel or right-click menu that summarizes the page, drafts a reply or pulls structured fields out of what you are reading. It calls your own AI provider through your server, so keys never ship in the extension. DataCram builds them from $1,500, depending on complexity, with a fixed written estimate before work starts.
On this page
- The key in the package is a key for everyone
- Chrome's side panel, as Google documents it
- Three jobs an AI extension does well, one at a time
- Your provider, your server, your bill
- What users must be told before the first summary
- Building the assistant, from the prompt on paper to the listing
- When the assistant you need is already in a browser tab
The key in the package is a key for everyone
An extension is a bundle of files installed on every user's machine. Anything in that bundle can be read by anyone who installs it, including an AI provider key. Put one there and every curious user holds your billing account. That is not a theory about bad actors. It is how files work.
Chrome's rules push in the right direction anyway. Google's Manifest V3 overview, read in November 2026, says an extension "can only execute JavaScript that is included within its package." The store's Manifest V3 requirements then allow remote calls for "Performing server-side operations with data," naming encryption with a private key as an example. Translation: the model call belongs on your server, and the extension talks to that server.
A model's answer is not code, which keeps the design inside the rules. Google's remote hosted code page says remotely hosted code "does not include data or things like JSON or CSS." The extension asks a question, receives text or structured data, and shows it. Nothing new runs.
Chrome's side panel, as Google documents it
The side panel is the natural home for an assistant. Google's sidePanel reference, read in November 2026, describes it as a way "to host content in the browser's side panel alongside the main content of a webpage." It needs the sidePanel permission, is available from Chrome 114, and "remains open when navigating between tabs (if set to do so)." Because it is an extension page, "side panels have access to all Chrome APIs."

Reading the page should happen only when the user asks. The activeTab permission, per Google's activeTab documentation, gives "temporary access to the currently active tab when the user invokes the extension" and "displays no warning message during installation." Pair it with a right-click item for selected text, the way our GatorCrawl Keywords extension offers "Look up keyword volume" on any phrase, and the assistant sees only what the user pointed at.
Three jobs an AI extension does well, one at a time
Summarize what is on screen
A long contract, a support thread, a vendor's terms page. The user clicks, the panel returns the short version with the parts that need a human flagged.
Draft in your company's voice
A reply to the email on screen, a follow-up after a call, a product description from the supplier page, drafted with your own instructions and saved examples.
Extract fields into a system
Names, dates, amounts and addresses lifted from a page into a form, a CRM record or a spreadsheet row through that system's API, checked by the user before saving.
Pick one per extension. Google's quality guidelines, read in November 2026, say "An extension must have a single purpose that is narrow and easy to understand," and that separate functions "should be put into two different extensions." An assistant for one kind of page and one kind of task passes that test. A general chat box bolted onto every site is harder to explain to a reviewer and to a user. Extraction that ends in a CRM overlaps with our CRM extensions, and support drafting with customer support extensions.
Your provider, your server, your bill
| Where it lives | Why | |
|---|---|---|
| AI provider key | Your server only | A key in the package is readable by every user who installs it |
| Prompts and instructions | Your server | Changed without a store update, kept out of view |
| User's sign-in token | Extension storage | Proves who is asking, revocable from the user's account |
| Page text the user chose to share | Sent per request | Only what the user selected or the tab they acted on |
| Usage limits and logs | Your server | One place to cap spending and see what was asked |
That is the same shape as our GatorCrawl extension. Its service worker holds a user's extension token and calls the GatorCrawl Keywords web app, which does the expensive work and meters it against the user's plan. The GatorCrawl case study walks through it. For AI, the server also picks the model, trims what is sent, and stops a runaway user from spending your month in an afternoon.
One engineering note from Google's service worker lifecycle page: Chrome normally ends an extension's service worker "When a fetch() response takes more than 30 seconds to arrive." Long model answers need a design that respects that limit. Our AI integration and LLM integration services cover the provider side, and AI agent development covers assistants that take actions, not just write text.
What users must be told before the first summary
An AI extension sends page content to a server. That makes it a user data product in Google's eyes, with obligations that apply from the first install. Our permissions and privacy guide covers the warnings and disclosures in full, and browser extension security covers what happens when a developer account is not protected.
- Disclose before install. Google's disclosure requirements say an extension handling user data must "Prominently disclose what user data will be collected and how it will be used" and "Obtain the user's affirmative and informed consent."
- Send only what the purpose needs. The Limited Use policy allows only data "necessary for the extension's disclosed single purpose" and prohibits "Transferring, using, or selling data for personalized advertisements."
- Publish a privacy policy that names your AI provider's role, linked in the developer dashboard, as Google's privacy policy rule requires for any extension handling user data.
- Keep sensitive values out of long-term storage. Google's storage reference says "If you're working with sensitive user data, instead use storage.session."
- Check your provider's own terms on data retention and training, and match your disclosure to them.
Building the assistant, from the prompt on paper to the listing
- 1
Write the job and the prompt first
One page type, one task, the instructions and three real examples. If the prompt does not work in a plain test, an extension will not fix it.
- 2
Stand up the server route
A small endpoint that checks the user's token, calls your AI provider, enforces limits and logs usage. Connections to your AI provider and your own systems go live the same day.
- 3
Build the panel and the trigger
A side panel, a right-click item, or both, with activeTab so the page is read only when the user asks.
- 4
Draft the disclosures with the code
Permission reasons, the privacy policy and the store's data questions are written alongside the build, then submitted under your developer account.
The build starts at $1,500, depending on complexity, with a fixed written estimate before work starts. A summary panel for one page type is the simple end; extraction into several systems or support for more browsers raises it. Your AI provider bills you directly for usage. Updates after launch are quoted. See extension pricing and the full custom Chrome extension development offer.
When the assistant you need is already in a browser tab
Plenty of teams do not need a custom build. If people paste text into an AI chat tab a few times a week and nothing needs to land in a company system, that tab is fine. A custom extension pays when the same task repeats all day on the same kind of page, when the output has to go somewhere specific, or when company data cannot go to a consumer tool. For staff-only assistants, Google Workspace admins can install the extension for the whole company by policy, which our page on internal team extensions explains, so nobody has to find it in a store.
An AI extension should know less about your browsing than your coworkers do.
Browse the rest of the browser extensions section, or weigh the choice on extension versus web app. DataCram is a San Antonio, Texas web studio, building for the web since 1999 and working with teams across the US by phone, video and a shared project page. Read about the studio, look through our work, or call (210) 346-0848 with the page your team keeps pasting into a chat window.
Questions owners ask about custom browser extensions
No. Every file in an extension is installed on every user's machine, so a key inside it can be read by anyone who installs it. Keep the key on your server and have the extension call that server with the user's sign-in token. The store's Manifest V3 requirements allow server-side operations with data, and the server can cap usage per user.
Yes. Google's sidePanel API, available from Chrome 114, hosts content in the browser's side panel alongside the page, and it can stay open as the user moves between tabs if set to. It needs the sidePanel permission. Because the panel is an extension page, Google says it has access to all Chrome APIs.
No. With activeTab, the extension gets temporary access to the current tab only when the user invokes it, for example by clicking its icon or a right-click item, and Google says that permission shows no warning at install. Access ends when the user leaves the page. The assistant sees only what the user chose to share.
Yes. The extension never talks to the provider directly; your server does. That means you choose the provider and model, keep your existing account and pricing, and can switch later without a store update. Connections to your AI provider and your own systems go live the same day. Check your provider's terms on data retention and match your privacy disclosure to them.
A prominent disclosure of what data is collected and how it is used, the user's informed consent before install, a privacy policy linked in the developer dashboard, and use of data only for the extension's single purpose. Google's Limited Use policy also prohibits using or selling the data for personalized advertisements.
From $1,500 to build, depending on complexity, with a fixed written estimate before work starts. That includes the permission plan, privacy disclosures and store submission. Your AI provider bills you directly for model usage, and updates after launch are quoted. We do not promise a store review time; Google says review times can vary.
Keep reading
- Ask for lessChrome Extension Permissions Explained: The Warnings Users See, the Data Rules Behind Them, and a Privacy Policy That Matches the CodeWhich Chrome extension permissions trigger install warnings, how activeTab and optional permissions help, and the privacy disclosures Google requires.
- The offer, part by partCustom Chrome Extension Development Services: Discovery, a Permission Plan, the Build and a Listing in Your NameHire a Chrome extension developer for discovery, a written permission plan, a Manifest V3 build, store submission and a handover under your account.
- Your app, one tab closerSaaS Browser Extensions That Carry Your App's Login, Plan and Credits Into the Tab Your Users Already Have OpenA companion Chrome extension that signs in with your SaaS account, spends the same plan credits and bills on your own site. From $1,500, owned by you.
- Your data, on their pageCustom SEO Chrome Extensions That Paint Your Own Numbers Onto Google's Results PageBuild an SEO extension that shows your own keyword, rank or client data on Google results, on one site, with two permissions. From $1,500, yours to own.
- Capture, minus the clipboardCRM Chrome Extensions That Save a Contact in One Click, Straight Through Your CRM's APIA Chrome extension that saves the contact on your screen to your CRM in one click, through the CRM's API, with no copy and paste. From $1,500.
- Built for the back officePrivate Chrome Extensions for Your Staff, Installed by Policy and Never Listed for the PublicA private Chrome extension for your employees: unlisted or private on the store, force-installed by your admin, wired to your own systems. From $1,500.
- Everything in Custom Browser ExtensionsSee the section
From the Insights desk
- The Best Marketing, Web Development & SEO Company in San AntonioEvery San Antonio agency calls itself the best. Instead of claiming the title, here's exactly what to look for in a web, SEO, and marketing partner — and how DataCram measures up, point by point. Then you decide.
- Own the Building: Why a Custom Next.js Site Beats WordPress and WebflowWordPress and Webflow both rent you a website — you may decorate, you may not renovate. A custom Next.js build hands you the keys: complete customizability, a CMS shaped to your business instead of a builder's data model, and a site you actually own.
Give your team an assistant that knows its place
Tell us which page your team works on and the task they keep pasting into a chat window. We reply with an architecture, a permission plan and a fixed written estimate.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.