Chrome AI that shows every permission, every time.
Juniper is open-source browser AI with a public data manifest — no hidden reads, no broad permissions, just auditability you can verify before the first install.
— on the waitlist already
3B Chrome users
The problem
Every Chrome AI extension you have tried asks for broad permissions and buries the details in a privacy policy written for lawyers. You do not know what it is reading, when it contacts external servers, or who receives your browsing context. Sider and HARPA have the features — neither will show you a data manifest or let you audit what runs in your browser.
“3B Chrome users want AI assistance but fear shady extensions with broad permissions”
How it works
Juniper ships a versioned public data manifest with every release listing exactly which Chrome APIs it touches, why, and what leaves your machine.
Install the open-source extension
The full source is on GitHub — read it, fork it, verify it before a single keystroke runs.
Read the data manifest
A machine-readable file ships with every release: permissions claimed, APIs called, data sent, and data that never leaves your browser.
Use AI assistance without the dread
Page summaries, writing help, and tab context — all scoped to the minimum permissions required, nothing more.
Different becauseSider and HARPA compete on feature count. Juniper competes on auditability, because trust is not a feature you bolt on after shipping — it has to be the architecture.
What's inside
- 01
Public data manifest
A versioned, machine-readable manifest ships with every release listing every Chrome API claimed, every endpoint contacted, and every data type that leaves your browser.
- 02
Minimal permissions by design
Juniper requests the narrowest set of Chrome permissions that makes each feature work, not a broad catch-all that covers features you may never use.
- 03
Open-source, line by line
The full extension is MIT-licensed on GitHub with no obfuscated bundles and no minified-only releases — what you read is what you run.
- 04
AI assistance scoped to context
Page summaries, selection rewrites, and tab Q&A are each scoped to the active tab only and cleared when you navigate away.
- 05
Diff-able releases
Every update ships a changelog that maps permission changes to the specific feature that required them, so you decide whether to upgrade with full context.
- 06
No account required for core features
Basic AI assistance runs without an account — no email harvesting on install, no mandatory sign-in to summarize a page.
Built for
Priya, 31, security-conscious full-stack developer
Priya reads the permissions dialog instead of clicking through it. She has uninstalled three AI tools this year after reading about data practices in HackerNews threads. She wants AI in her browser but will not trade auditability for convenience.
You probably
- →You read the permissions dialog instead of clicking Accept
- →You have removed an extension after finding out what it was reading in the background
- →You check GitHub for a repo before installing anything from the Chrome Web Store
Questions
The data manifest shipped with every release documents exactly this. For AI features, the selected text or page content you explicitly invoke goes to the configured LLM endpoint. Nothing is sent passively or in the background.
Yes. The repository includes the extension source, the build pipeline, and the manifest generation script. There are no closed build steps or private forks that diverge from what you install from the Chrome Web Store.
The default uses a configurable endpoint — you can point it at OpenAI, Anthropic, a local model, or any provider with an OpenAI-compatible API. The data manifest updates to reflect whichever endpoint you configure.
Sider and HARPA compete on features. Juniper's core differentiator is auditability: a public data manifest, minimal permissions, and open-source code you can read before installing. If feature count matters more to you than trust, Juniper is not the right tool.
The current manifest requests activeTab for on-demand page access, storage for settings, and scripting for selection detection. It does not request history, bookmarks, all-tabs access, or webRequest.
Core functionality is free and open-source. The paid Founder tier covers sync, a managed LLM endpoint, and audit log export. No feature that ships free will move behind a paywall in a later release.
The manifest includes a build hash tied to the tagged release commit. The README documents the reproducible build steps so you can compile from source and compare.
A small team of developers who read extension source code before installing and found the audit tools were missing. The repository is open for contributions and the roadmap is public.
Why now
- 3B Chrome users00-dossier.md hypothesis
Trust
- MIT Licensed
- Open Source
- Minimal permissions
- Public data manifest
30-day money-back. No questions asked.
Why this exists
Juniper exists because trust in browser extensions has to be earned through auditability, not asserted through a privacy policy.
Chrome's AI extension category is growing fast and trust is losing — the market treats features and transparency as a trade-off, and we think that is a false choice.
Built by a small team of developers who read extension source code before installing it and found the audit tooling was missing.
Reach us: hello@waitlist.solutions