> For the complete documentation index, see [llms.txt](https://docs.frontrun.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frontrun.pro/faq.md).
# FAQ
How does Frontrun make money?
Frontrun returns 90% of every trading fee to traders as cashback and earns the remainder. Additional revenue comes from Silver and Gold subscription tiers, which unlock higher usage limits and advanced features. See [Plans & Pricing](/plans-and-pricing.md) and the Fees page for the full breakdown.
Is the code open sourced? How can I audit it?
We’ve open-sourced **the exact Plasmo build** that we publish to the Chrome Web Store. This bundle contains every line of code that actually runs in your browser when you use the Frontrun extension.
We haven’t released the entire development repository because we work in a monorepo that also includes private packages and internal tooling unrelated to the extension. Those components contain proprietary logic and infrastructure code, so keeping them private protects both intellectual property and security.
By sharing the Plasmo build, we provide full transparency into what’s shipped to users while sensibly separating out non-essential, internal modules. If you’d like to audit the build, you can even paste it into ChatGPT for a line-by-line review:
Why does Frontrun ask for these Chrome permissions? Is it really necessary—and is my data safe?
Frontrun only requests the minimum set of permissions required to deliver its in-browser tooling. Every permission has a specific, narrowly scoped purpose:
| Permission | What we use it for | Why it matters to you |
| -------------- | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| **storage** | Save your labels, watch-lists, and UI preferences locally. | Keeps your custom settings without needing a back-end database. |
| **scripting** | Inject lightweight scripts that add wallet labels, fee-cut indicators, and other overlays on X, Solscan, GMGN, etc. | Enables all the on-page insights you installed Frontrun for. |
| **sidePanel** | Show the Frontrun control panel. | Gives you a convenient place to review positions or toggle features. |
| **webRequest** | Efficiently intercept and cache extension data. | Reduces page-load overhead so overlays appear instantly. |
| **windows** | Open and manage popup windows (e.g., settings, login). | Keeps UX tidy by using native Chrome pop-ups instead of new tabs. |
| **identity** | OAuth sign-in to sync your settings across devices | Lets you carry labels and preferences from laptop to desktop if you turn it on. |
* **Smaller footprint than most**: This list is *shorter* than what you’ll find in many web-3 wallets (e.g., Phantom requests additional permissions for account management and transaction signing).
* **No clipboard access, ever**: Frontrun has *zero* permissions to read or write your clipboard.
* **Privacy & security first**: All logic runs client-side; no keystrokes, private keys, or browsing history are sent to our servers. The open-sourced Plasmo build lets you verify this yourself.
In short, each permission directly powers a feature you can see, and nothing more.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.frontrun.pro/faq.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.