SpikedAI Chrome extension

Privacy policy

Last updated: 19 August 2026

This policy covers the SpikedAI Chrome extension only. The Spiked AI web app at https://app.spiked.ai and the SpikedAI desktop app have their own terms.

The short version

The extension does not send anything anywhere. It has no server of its own, makes no network requests, and holds no account credentials. It reads two things — which Google Meet call you are on, and what the Spiked AI tab already knows — and moves them between surfaces that are already open in your browser.

What it reads

The address of your Google Meet tabs. The extension runs on https://meet.google.com/* to tell an active call (meet.google.com/abc-defg-hij) apart from the Meet home page, so it knows when to offer the Connect Live card. Nothing else on the page is read: not the video, not the audio, not the chat, not the participant list, not the captions.

The address and title of the active tab, while the side panel is open. The “Ask Spiked” panel shows which page it is grounded in. This is read on request, from the active tab of the window the panel belongs to, and is used to render that line in the panel. It is not stored and not transmitted.

What the Spiked AI tab publishes about itself. When you have https://app.spiked.ai open, the panel mirrors what that tab is already showing you — the Autopilot state, its answer cards, the selected client, the revenue figures. This travels from the page to the panel inside your browser, over Chrome’s own extension messaging. It never leaves the machine by way of the extension.

What it stores

In chrome.storage.local, on your machine, in your browser profile only. None of it syncs, and none of it is transmitted:

Key What it is
cardPosition where you dragged the in-call card to
handled:<meeting url> that you connected or dismissed a given call, so it is not offered again for four hours
panelTheme the panel’s colour and intensity
panelTextSize the panel’s text size
drawerHeight how tall you dragged the panel’s bottom drawer

You can clear all of it by removing the extension.

What it sends

Nothing, to anyone. The extension originates no network traffic: there is no fetch, no XHR, no WebSocket and no analytics anywhere in its code. This is a design rule, not an accident — it is what guarantees that a question asked in the panel is answered exactly once, by the web app, on the account you are already signed into.

Two things do leave the extension, and both go to a page you already have open:

Accounts and credentials

The extension holds no token, runs no sign-in flow, and does not read or write your session. Everything that needs an account is done by the Spiked AI tab, which is signed in the ordinary way, in your browser.

Third parties

None. No analytics, no crash reporting, no advertising, no trackers, and no data sold, rented or shared with anyone.

Permissions, and why each is needed

Four, and two sites. Each is here because a feature stops working without it.

Permission What it is for
storage Keeping your own preferences on your machine — the table above. Local only.
tabs Finding an already-open Spiked AI tab so Connect Live focuses it instead of opening duplicates; enabling the side panel on Meet tabs and disabling it everywhere else; showing you which page the panel is grounded in. No browsing history is collected, stored or sent.
sidePanel The “Ask Spiked” panel itself, and restricting it to Google Meet tabs rather than offering it on every site.
scripting Only to inject this extension’s own content scripts into tabs that were already open when it was installed or updated — otherwise installing mid-call does nothing until you reload the meeting. No remote or generated code is ever injected.
Site access What it is for
meet.google.com Recognising that you are on an active call, so the card and the pill appear on it. Only the address is read — never the audio, video, chat, captions or participants.
app.spiked.ai Relaying what that tab already shows you into the side panel, and relaying your button presses back so the app performs them under your existing session. This is the only origin the extension exchanges messages with, and every message is checked against it.

The extension executes no remotely hosted code. There is no build step, no eval, and no externally sourced script, stylesheet or font.

Contact

Questions about this policy: support@spiked.ai