Privacy Policy

The extension does nothing in the background. It captures data only while you actively record a brief or take a screenshot. For a brief you record, that can include:

• Screen and voice recording. A recording of the browser tab you are on, mixed with your microphone narration, so we can see and hear the issue you are describing.
• Microphone audio. A short audio track of your narration, used only to transcribe what you said into ticket text.
• Screenshots and keyframes. A screenshot you choose to capture (with any annotations you draw on it), plus periodic still frames sampled from the recording so the ticket can show what was on screen.
• Diagnostic events from the recorded tab. Console errors, uncaught JavaScript errors, and failed network requests (method, the request URL, and the HTTP status) that occurred during the recording. We capture error messages and request URLs and status codes only. We do not capture the page DOM, request or response bodies, or cookies.
• Reproduction steps. A timeline of your clicks, scrolls, and key presses during the recording, so the ticket can describe how to reproduce the issue. Typed characters are masked (recorded as a placeholder, not the actual keystrokes).
• Page context. The URL and title of the tab you recorded, so the ticket records where the issue happened.
• What you type. The brief name, your written description, and any custom key and value fields you add.
• Environment. Your browser user agent string (browser and operating system), included as context on the ticket.

Sign in is handled by our authentication provider, Clerk. When you connect the extension to your account, the web app issues a pairing token that the extension stores locally in the browser and sends back to our backend to prove the brief is yours. The token is stored only on your device and is cleared when you sign out or disconnect. It is never shared with any third party.

We use the data above for one purpose: to generate a well written ticket from your recording and file it to the tracker you connected. The recording, screenshots, transcript, diagnostics, and the text you wrote become the ticket. If you enable the "attach the recording" option, the recording is attached to the filed ticket; otherwise it is used only to write the ticket and is not attached.

We do not use your briefs to build advertising profiles, and we do not use them to train third party models for unrelated purposes.

Your brief data is sent to the following services, and no others:

• Brief Cloud backend (cloud.get-brief.app), hosted on Fly.io, which receives the brief and orchestrates writing and filing the ticket.
• Supabase Storage, where the recording, audio, screenshots, and keyframes are uploaded (via short lived signed upload URLs) until the ticket is filed.
• OpenAI, used by our backend to transcribe your narration audio into text. Only the audio needed for transcription is sent.
• Clerk, our authentication provider, which handles sign in and your account profile.
• Your connected tracker (Linear or Jira), where the finished ticket is created on your behalf using the connection you authorized.

Brief media (recording, audio, screenshots, keyframes) is uploaded to storage only so the ticket can be written, and the source files are removed once the brief has been filed. A record of the ticket you filed (its title and status, and the link to it in your tracker) is kept in your account so your Brief Cloud feed can show it. You can delete or archive briefs from the web app.

• No advertising, ad networks, or affiliate injection.
• No analytics or telemetry SDKs in the extension (no Google Analytics, Segment, Mixpanel, Sentry, or similar).
• No selling or renting of your data to anyone.
• No reading of pages you have not chosen to record. The extension is inert until you start a recording or take a screenshot.
• No access to your cookies, passwords, or browsing history.

Each Chrome permission maps directly to a capture feature: tab capture to record the current tab, the active tab and host access to take a screenshot and inject the recorder onto the page you are on, scripting to capture console and network errors during the recording, an offscreen document to run the recorder, and local storage to keep your brief inbox and pairing token on your device. The extension talks only to the Brief Cloud web app for pairing.

Recording is always something you start. You choose whether to attach the recording to the ticket, what to type, and which tracker to connect. You can disconnect the extension or sign out at any time, which clears the pairing token from your device. To request deletion of account data, contact us at the address below.

Questions about this policy or your data? Email privacy@get-brief.app.