Legal

Privacy policy

Last updated 30 September 2026

FrontBug is a Chrome extension for reviewing web pages, a hub where teams review together, and a command-line tool that talks to that hub. The extension records notes about the page you are reviewing, together with screenshots and the browser activity around each note, and lets you export them as a file or send them to a hub project. This policy covers the extension, the hub at app.frontbug.com, the questionnaires sent from it, and this website. Who is responsible for FrontBug is stated in the legal notice.

Summary

The extension has no account and no analytics. It keeps what it records on your computer, in the browser's local storage, and makes no network requests of its own until you connect it to a hub project. Its data leaves your computer only when you export it yourself or sync it to a hub you have connected.

The hub is a server with accounts. What it stores, where, for how long and who can see it is described under "The FrontBug hub" below. If someone sent you a questionnaire from the hub, the section "Questionnaires" explains what happens to your answers.

What FrontBug records

FrontBug records nothing until you start a review session on a site, and it records nothing on any site where you have not started one. While a session is running on a site you have granted, it records:

• The notes you write, with their type, severity, tags and status.
• Screenshots of the elements, regions or pages you choose to capture.
• The identity of the element a note is attached to: the markup around it, a selector that can find it again, its accessible name, its position and size, its computed styles, and, when the site is running a development build that exposes it, the component name and source file.
• The URL and title of the pages you visit within that session, so notes can be grouped by page.
• Console messages and errors produced by that page.
• Network requests made by that page: method, URL, status, timing, size and headers. Request and response bodies are not recorded.
• Your actions on that page, clicks, typing, form submissions, scrolling and navigation, as reproduction steps. Text you type into a field is recorded as its length, not its content.
• The display name you choose, or, if you leave "use the account signed into Chrome" on, the email address of the Google account signed into this Chrome profile. This is used to sign your notes so that a team reviewing the same site knows who wrote what.
• A random identifier generated once for this Chrome profile, so that two people using the same display name can still be told apart.
• Your settings.

Masking

Because console and network activity can contain credentials, FrontBug masks them before storing them, and this is on by default:

• Authorization, Cookie, Set-Cookie, X-API-Key, X-Auth-Token and Proxy-Authorization headers are replaced with "<redacted>".
• URL parameters and values whose name suggests a credential, token, secret, key, password, auth, session, bearer, api-key, access, refresh, are replaced with "<redacted>".
• Values that look like credentials regardless of their name, JSON Web Tokens, long hexadecimal or base64 strings, are masked. Email addresses are partially masked. Card-shaped and IBAN-shaped numbers are masked.
• Values typed into form fields are recorded as a length. Values in password, email and telephone fields, and in fields marked as sensitive by the site, are not recorded at all.

Screenshots are not masked. Whatever is on the screen is in the image. Before you export, FrontBug shows you every screenshot in the session and lets you delete any of them.

You can turn individual masking rules off in Settings. Doing so means credentials may be stored in full, on your computer, and may end up in anything you export.

Where it is stored

On your computer, in this Chrome profile, using the browser's local storage for notes, screenshots and logs, and Chrome's extension storage for settings. FrontBug does not use Chrome's synchronised storage, so none of this is copied to Google's servers or to your other devices.

What is transmitted

By default, nothing. FrontBug does not send your notes anywhere unless you ask it to, and it never sends them to us for any purpose of our own. There are three ways data can leave your computer, and all three are off until you turn them on.

Exporting. You get a file, a zip download or a folder written into a project you pick, and what happens to that file is entirely up to you. An export includes your notes, screenshots, the recorded activity, your display name and, unless you turn off "include email in exports" in Settings, your email address.

Connecting to a hub project. If you pair the extension with a FrontBug hub, the notes of the sessions you sync are uploaded to that hub: their text, the screenshots, the recorded activity and your display name. They are stored there so the people in that hub project can see them, which is the point of connecting. Pairing is explicit: you ask for a code, and someone with access to the project has to approve it. You can undo it from Settings, and the project owner can revoke the key from the hub at any moment; from then on nothing more is sent. If you use the hub we run at app.frontbug.com, we are the ones storing that data; what it keeps and for how long is described under "The FrontBug hub" below. Once paired, the traffic also goes the other way: while the side panel is open, the extension asks that hub every 45 seconds for the current status, severity and tags of the notes in the session you are looking at, so the board shows what your team changed instead of a stale copy. That request carries the project key and the session id and nothing else, and it stops the moment you close the panel or unpair.

The local channel. If you turn on "allow local agents" and paste the token, the extension opens a connection to 127.0.0.1 on your own computer, so a coding agent running there can read your notes and ask for a fresh screenshot. That connection never leaves your machine: it is refused for any web page, and the daemon only accepts a token generated on that computer.

Third-party services

In the extension: none. FrontBug does not use analytics, crash reporting or advertising inside the extension, and the extension sends your data to no third party. It talks only to the hub you connect it to, and to your own computer if you turn on the local channel. The FrontBug hub is not a third party: it is part of this same product, and you decide whether to connect to it.

In the hub, a few providers do part of the work, and each one receives only what that part needs:

• OVHcloud rents us the server the hub runs on, in its data centre in Frankfurt, Germany.
• Postmark sends the hub's emails: confirming your address, resetting your password and team invitations. It receives the recipient's address and the message.
• Google, only if you choose to sign in with Google, confirms who you are and gives the hub your name, email address and profile picture.
• Apple, only if you choose to sign in with Apple, confirms who you are and gives the hub your name the first time and an email address, which is a private relay address if you choose to hide yours.
• Expo, which delivers notifications to the FrontBug mobile app through Apple's push service (the app is iPhone-only for now), receives each notification's text and the push token of your phone, only if you use the app and allow notifications.
• Deepgram, only when voice transcription is turned on in the hub, receives the audio of voice notes to turn it into text.
• Cloudflare, only when the hub's check that you are a person is turned on, runs that check on the page where you start answering a shared questionnaire link. It receives what the check reads from your browser and your IP address, not your name or your answers.

Postmark, Google, Apple, Expo, Deepgram and Cloudflare may process that data outside the European Union, including in the United States.

Sharing

Your data is not sold. It is not used for advertising, for building a profile, or for anything unrelated to producing your review. What stays in the extension is shared with no one, because the extension does not transmit it, and no person at FrontBug can access it. What you upload to a hub project is shared with the members of that project, which is the point of uploading it, and with the providers listed above for the part each one does. Nobody at FrontBug looks at it except to operate, secure or repair the hub, or when the law requires it.

How long it is kept, and how to delete it

In the extension, data stays until you delete it. You can delete an individual screenshot, a note, or a whole session from the side panel; deleting a session deletes its screenshots and logs with it. Settings has a "delete all data" action that removes everything. Removing the extension from Chrome deletes its storage as well. Deleting data in the extension does not delete what was already synced to a hub; the hub has its own rules, described below.

Site access

FrontBug requests access to a site at the moment you start a review on it, one site at a time. It is not granted access to any site at install time. Settings lists every site you have granted and lets you revoke each one, which also stops FrontBug running there.

The Chrome debugger

To photograph a page taller than your screen, FrontBug briefly uses Chrome's developer protocol, which is why Chrome shows a "FrontBug started debugging this browser" banner during the capture. The connection is opened for that one screenshot and closed immediately afterwards. If you dismiss the banner, FrontBug takes the screenshot a slower way instead, and does not reconnect.

The FrontBug hub

The hub at app.frontbug.com is where a team reviews together. Unlike the extension, it is a server and it needs an account. If you use the extension without connecting it, this section does not apply to you.

What it stores.

• Your account: your name, your email address and whether you have confirmed it, and either a hash of your password or, if you sign in with Google, your Google account identifier, the address of your profile picture and the sign-in tokens Google returns, or, if you sign in with Apple, your Apple account identifier and the email address Apple gives the hub.
• Your sign-ins: for each signed-in session, the IP address and the user agent of the browser or app it was opened from. A session ends 90 days after you last used it, or earlier if you sign out.
• The mobile app, if you use it: for each phone, its platform, the app version, its language and time zone (so notifications are written in your language and quiet hours follow your clock), when it was last seen, whether you allowed notifications and, if you did, its push token; your notification preferences; and the notifications sent to you, which the hub deletes after 30 days. The app contains no advertising identifiers and no analytics.
• Your teams: the organisations and projects you belong to, your role in each, and the invitations sent, with the invited email address and who sent them.
• What the extension and the command-line tool upload to a project: the notes, with their author as recorded (display name, the email address if you sign notes with your Chrome account, and your time zone), screenshots, voice notes and, when transcription is on, their transcripts, the addresses of the pages reviewed, and the recorded console, network and action activity. Comments and changes made in the hub are stored with who made them.
• Connections: when a browser or a terminal asks to connect to a project, its device name, its version and the IP address the request came from. That address is shown to the person approving, so they can tell whether the request comes from their own network. Project keys are stored only as a hash.
• A record of the activity in each project, who changed what and when, which the members of the project can see.
• Like any web server, the hub sees the IP address of each request, and its server logs can keep it for a while to diagnose failures and abuse.

Where. On a server we rent from OVHcloud in its Frankfurt data centre, in Germany, in the European Union. The database and the stored files, screenshots and voice notes, are on that same server.

What for. To run the hub for you and your team: to sign you in, to show each project to its members, to send the emails an account needs, and to keep the service working and secure. Not for advertising, profiling or selling.

How long. By default the hub deletes nothing on a schedule: review sessions stay until someone deletes them. The owner of a project can set a retention period between 7 and 365 days in the project settings. Once a session is older than that, the hub deletes the whole session: its notes, screenshots, voice notes and recorded activity. Members with permission can delete an individual note or screenshot at any time. Your account stays until you delete it.

Backups. Something deleted from the hub can remain for a while in the backup copies we keep so the hub can be recovered after a failure.

Who can see it. The members of the project it belongs to, according to their role. We can technically access the server, and only do so to operate, secure or repair the service, or when the law requires it.

Deleting it. Notes, screenshots and sessions can be deleted from the hub, and a project can set a retention period, as above. You can delete your account yourself, on the web at app.frontbug.com/account or in the mobile app under Settings › Delete account. Deleting it removes your name, your email address, your sign-ins, your phones, your notification preferences and the project keys of the browsers and terminals you connected. Organisations you share with other people stay: you leave them, and the notes and comments you wrote there stay with them, under the name you signed them with. If you are the only owner of an organisation that has other members, you first have to make someone else an owner. If you are its only member, deleting your account does not delete the organisation: it stays, with all its projects, notes, screenshots and voice notes, without members, and FrontBug support can give it an owner again so its team can get back in. You confirm by typing the email of your account. To ask for a copy of your data, write to privacy@frontbug.com from the address of the account.

Questionnaires

A team using the hub can send a questionnaire to people outside the team, for example to ask a client how a page should behave. It opens on a page of app.frontbug.com, without an account.

Who is responsible. The team that sent the questionnaire decides what to ask and what to do with the answers: it is responsible for that data, as its controller. FrontBug stores it on the team's behalf and on its instructions, as its processor, and does not use it for anything of its own.

What is stored. The name you give, or the one the team entered for you; your email address, only if you choose to leave it; your answers, including anything you write in a comment; and when you opened the link and when you sent your answers, which also appear, with your name, in the project's activity record. Your IP address is not stored with your answers: the hub keeps it only in the server's memory, never in its database, to limit how many requests can come from the same place.

What for. Only for that questionnaire. The team reads your answers and, if you left your email address, may reply to you. The hub does not send you emails: if the team writes to you, it does so from its own address.

How long. Your answers follow the retention period of the team's project. If the project has none, which is the default, they stay until the team deletes them. If it has one, they are deleted that many days after your link stops accepting answers, because it expired, was revoked or the questionnaire was closed. The page where you answer says which applies.

Deleting them. Ask the team that sent you the questionnaire: it can delete your answers, or the whole questionnaire, from the hub. You can also write to privacy@frontbug.com; since the data is the team's, we will pass your request on to it and act on its instructions.

This website

The pages on frontbug.com count visits, and that is all. What is sent to our own server is the path of the page, without its query string, the host of the site you came from, and the utm_source of the link if the link carried one. Nothing else.

There is no cookie, no identifier, no browser fingerprint and no third party analytics script. We cannot tell one visit from another or follow anyone between visits. The server keeps only a daily total per page, and not even the time of day.

A click on the install link is counted the same way, because the number of people who install is the only way to know whether this page is useful. It is still a count with nobody attached to it.

We measure this way on purpose. The whole point of the product is that nothing leaves your browser unless you ask, and putting someone else's tracking script on this page would say one thing in the text and another in the code.

Your rights

You can ask us for access to the personal data we hold about you, to correct it, to delete it, to receive a copy of it, or to object to or restrict how we use it, by writing to privacy@frontbug.com. If your data reached the hub through a questionnaire, the request goes to the team that sent it, as explained above. You can also complain to a data protection authority; in Spain, that is the Agencia Española de Protección de Datos (aepd.es).

Children

FrontBug is a tool for software development work and is not directed at children.

Changes to this policy

If FrontBug's data practices change, for example if the extension starts recording a new kind of data or the hub starts using a new provider, this policy will be updated before that change is published. Anything that sends data out of the extension will remain something you turn on, not something that happens by default.

Contact

privacy@frontbug.com

Back to frontbug.com