These are the questions that come up most when an agency or freelancer is thinking about fydbek for their clients. If yours is not here, write to hello@fydbek.com.
About fydbek
What is fydbek?
fydbek is a website feedback widget. A client, designer, copywriter or tester clicks a spot on the page, writes what to change and sends it. Each piece of feedback comes with a screenshot, the selected element and browser details. Your team handles it in the dashboard at app.fydbek.com, and AI agents work with it through the MCP server.
What does a piece of feedback include?
The comment, the page URL and title, the selected element with its selector, text and styles, the browser, OS, window size and a screenshot. Console errors and failed network requests are attached too. Instead of an element, the client can drag to select an area, suggest new copy right on the page, or record a voice comment. The voice is transcribed to text they can fix before sending.
Why is this better than email and screenshots?
An email rarely says where exactly the problem is on the page, in which browser or at what window size. fydbek adds all of that to the feedback, so you don't have to ask which heading the client meant. Each item has its own thread and status, so nothing gets lost in a long email chain. And agents can work with it directly, without anyone copying it out of an inbox.
Which websites does fydbek work on?
Any site where you can add code to the page head: plain HTML, Astro, Next.js, React and site builders with a custom code field. For WordPress there is a plugin that needs no theme changes. It also works on staging and in local development on localhost, *.test or *.ddev.site.
Clients and site visitors
Who sees the widget on my site?
Only people you invite by email, people you send a feedback link to, and members of your team. Regular visitors see nothing. Anyone can bring up the toolbar by adding ?fydbek to the URL, but without signing in they only get a sign-in button.
Do my clients need an account?
No. You can send a client a feedback link, for example in a chat. They enter their name and start leaving feedback, with no password and no email confirmation. Nobody verifies that name, and a guest from a link sees only their own feedback, so use an email invite for key people. An invite creates the account when they click the link in the email, and there is no password there either.
Does fydbek slow down my site?
Not for regular visitors. With the regular code they download only a small loader that loads async and does not block the page. The widget itself loads only for invited people. In strict mode, visitors download nothing from fydbek at all, not even the loader.
Does it work on mobile?
Yes. Clients can send feedback from their phone. On a touch screen, the first tap selects an element and the second opens the comment box.
Do I need the Chrome extension?
Your clients don't, the widget on the site is all they need. The extension is for your team: it opens the page at the same window size the client had and highlights the selected element. When a team member has the extension, the widget asks it for an exact screen capture instead of a copy of the page.
Data and privacy
Where is the data stored?
In the EU. fydbek runs on Cloudflare, and the database, files and screenshots are kept in Cloudflare's EU jurisdiction. The one exception is machine transcription of voice comments through Cloudflare Workers AI, which may run outside the EU. Cloudflare does not store the recording or the transcript and does not train on them.
What about GDPR?
For the content you and your clients put into fydbek, your agency is the controller and fydbek is the processor. The dashboard and the widget contain no analytics or advertising tools, and fydbek does not use your data to train AI models. The widget stores and sends nothing for regular site visitors. The details are in the privacy policy at fydbek.com/en/privacy.
What gets masked in screenshots?
The values of all form fields are replaced with dots in the screenshot and in the captured context. Elements with the data-fydbek-mask attribute are blurred in the screenshot and their text is replaced in the context. Parameters such as token, key, secret, password and code are removed from page and request URLs.
AI agents
How do AI agents work with the feedback?
They connect through the fydbek MCP server. An agent reads feedback with its screenshot and context, triages it, asks the client follow-up questions in the thread, turns it into tasks in another tool and stores the link. A coding agent such as Claude Code finds feedback for the page it is working on, fixes it in the repository and attaches an after screenshot. The client sees the agent's replies right in the widget, marked as coming from an agent.
Which AI agents can I connect?
fydbek is in the Claude connector directory, so you can add it in claude.ai and in the Claude desktop and mobile apps. Claude Code and other clients connect with an API token. Any other client that supports MCP over Streamable HTTP with OAuth or a token works too. In ChatGPT, you can add it from the app directory.
Can an agent delete things or act without my review?
It cannot delete anything, no tool on the MCP server deletes data. An agent has the same permissions as the account or token it acts for, within one organization. Every action it takes shows up in fydbek with the app it came through, for example via Claude. Following the work_on_page prompt, a coding agent sends its fixes to an internal review that only your team sees, and you decide when the client gets them.