For Chrome extension developers

Onboard new users. Hear from the ones who leave.

Two hosted pages, one tiny SDK — both independently optional. Install: welcome screen, "where did you hear about us?" microsurvey, optional setup steps. Uninstall: reason chips, free-form text, optional email opt-in. No permission warnings. No trackers. Hashed IPs only.

Create free account ↓ Download SDK Read the quickstart →

On install On uninstall

/i/abc…

Welcome aboard.

Where did you hear about us?

Store Friend Search Blog

What the install page does

Opt-in — pass install: true to enable; otherwise skipped entirely.
Greets new users with your logo, color, and copy.
Captures referral source via an optional "Where did you hear about us?" microsurvey.
Renders optional onboarding steps (title + body + image) for first-five-minutes setup.
Skips automatically on updates — only opens when onInstalled.reason === "install".

/u/abc…

Sorry to see you go.

Mind telling us why?

Too buggy Found better Privacy Other

Common complaints & what to do

On by default — pass uninstall: false to disable.
"Too many bugs" — filter the dashboard by reason; ship a focused bug-bash before the next release.
"Found a better one" — read the free-form text; users almost always name the competitor.
"Privacy concern" — audit your manifest permissions; add a plainer privacy note to your store listing.
"Don't use it" — onboarding gap. Add an install-page setup step that demonstrates the core feature.

How it works

Three lines of code. Two hosted pages. Zero permission warnings.

From signup to first feedback row in under ten minutes.

Sign up

Email-based identifier; we generate a strong password and a one-time recovery code. We never send email.

Register your extension

Paste your Chrome Web Store ID. Configure copy, color, reason chips, and optional microsurvey from the dashboard.

Drop in the SDK

One ES module. Both pages are independently optional:

import { ExtensionFeedback }
  from "./ef-sdk.js";

ExtensionFeedback.init({
  apiKey:    "ef_live_…",
  install:   true,   // default false
  uninstall: true,   // default true
});

What's in the box

What we do, what we refuse to do.

We do

Open hosted install & uninstall pages on your domain.
Capture reason chips, free-form text, optional email opt-in.
Let you export everything as CSV. Your data is yours.
HMAC-hash the IP with a server-side secret. Cannot be reversed.
Auto-NULL free-form text and email at 90 days.
Show a one-click opt out link in every feedback page.
Open-source the SDK (MIT). Audit it once and you're done.

We don't

Ship third-party analytics (no GA, Plausible, Segment, Mixpanel).
Run remote code from the SDK.
Fingerprint or set cross-site tracking cookies.
Sell, share, or license submission data.
Send email — recovery is a code you save at signup.
Trigger permission warnings. storage is the only requirement — a silent permission, no install prompt.

The SDK

Open source. Single file. Zero dependencies.

Drop it in your extension folder, import it relatively, and you're done. No bundler, no npm install, nothing to evaluate at runtime.

Direct download /sdk/ef-sdk.js · right-click → save as

Source on GitHub github.com/ExtensionFeedback/ef-sdk · MIT, issues + PRs welcome

Or via curl curl -O https://extensionfeedback.com/sdk/ef-sdk.js

Read it inline first /docs/sdk · the entire source rendered on one page

SDK reference View on GitHub ↗ 3-line quickstart

FAQ

Quick answers to common questions.

Does my extension need new permissions?

Only "storage", which most extensions already have. It's one of Chrome's silent permissions: users see no warning at install, and adding it in an update won't disable your extension pending re-approval. Everything else the SDK touches — chrome.runtime.setUninstallURL() and chrome.runtime.onInstalled — is permission-free.

Will the Chrome Web Store flag this?

An uninstall URL is an explicitly supported Chrome feature. You're not collecting anything you weren't entitled to. A short note in your privacy policy is good practice.

What does it cost?

Free during alpha. When pricing lands there will be a free tier and a paid tier; existing accounts get at least 30 days' notice and grace.

Where do I get the SDK?

Three options. Direct download from /sdk/ef-sdk.js; the public source at GitHub; or read it inline at /docs/sdk before downloading.

Can users opt out forever?

Yes — one click on /opt-out. We then drop every submission from that browser, for every extension on the platform, forever.

All questions →