BugOwl Privacy Policy
BugOwl is a Chrome extension for reporting bugs, built in partnership with Pagerly. This page explains what it collects, where that data goes, who can see it and how to have it deleted.
The short version. Nothing leaves your browser until you take a screenshot or a recording. A report goes only to Pagerly, and to the Slack channel, Jira, Linear or Asana project you choose. We do not sell data, show ads or track your browsing.
What BugOwl collects, and when
So that a report can show what happened just before the bug, BugOwl keeps a short rolling log of the page's console messages, network requests and your actions while you browse. That log stays on your computer: it lives in the page's memory and in the extension's session storage, holds only the most recent entries, and is cleared when you close the browser. It is used only when you start a capture with the toolbar button, a keyboard shortcut or the right-click menu.
A capture can include:
- The screenshot or recording of the tab, region or screen you chose. The microphone is off unless you turn it on in settings.
- Console messages from the page: logs, warnings and errors.
- Network requests made by the page: the method, URL, status, timing and headers, and request and response bodies when that setting is on.
- Your actions on the page: clicks, navigation, and how many characters you typed into which field. The text you type is not recorded.
- Page and device details: the page URL and title, browser, operating system, screen size and language.
- What you write: the title, description and annotations you add.
Some data is removed before anything leaves your browser:
Authorization,Cookie,Set-Cookie, API key and CSRF headers are always replaced with «redacted».- Request and response bodies are never sent for URLs containing
/login,/auth,/token,/passwordor/oauth, or any other pattern you add in settings.
You can turn console, network, body and action capture off in BugOwl's settings.
Signing in
There are two ways to sign in:
- With your email. We email you a six-digit code through Mailmodo, our email provider, and keep your email address so your reports stay yours. We store only a scrambled form (a hash) of the code and of your sign-in token.
- With Pagerly. BugOwl uses OAuth, so your Pagerly password never reaches BugOwl. Your email address and Pagerly organisation come from Pagerly.
BugOwl keeps your sign-in in the extension's storage on your computer and sends it only to Pagerly, which runs BugOwl.
Where reports go
- On your computer. A capture is first saved in the extension's local storage.
- Pagerly. When you are signed in, the capture is uploaded to Pagerly so it gets a share link. You can turn this off in settings with Instant share link; then a capture is uploaded only when you save or file it. Pagerly stores reports on Amazon Web Services in the United States.
- Your team's tools. When you file a report, it goes to the Slack channel, Jira, Linear or Asana project, or Pagerly incident you picked. Signed in with Pagerly, that uses the connections your organisation set up in Pagerly. Signed in by email, it uses the Slack, Linear or Jira connection you approved in BugOwl: we keep the access token that service gives us, use it only to list where you can file and to create what you file, and delete it when you disconnect. A screenshot you file is fetched by Slack or Linear from a public address that only someone with the report's link could know.
- AI SRE, only if you ask. If you tick the option to have Pagerly's AI SRE investigate a report, the report is processed by your organisation's Pagerly AI SRE, as described in Pagerly's privacy policy.
Who can see a report
Each report has a share link with a random 12-character code. Anyone who has the link can view the report, the same as an unlisted video. The public page never shows your email address or your organisation. People in the Slack channel or project you file to can also see it there.
What we never do
- We do not sell or rent your data, or use it for advertising.
- BugOwl does not keep or send your browsing history. The rolling log described above never leaves your computer unless you capture.
- BugOwl contains no analytics or tracking code.
Keeping and deleting reports
Reports are kept until you or your organisation ask us to delete them. Email hello@pagerly.io with the share links, or ask us to delete every report from your organisation, and we will delete them within 30 days. Copies already filed in Slack, Jira, Linear or Asana are controlled by those tools.
Removing the extension deletes everything stored on your computer, including the sign-in tokens.
Chrome Web Store limited use
BugOwl's use of information received from Chrome APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only to create and file the bug reports you ask for.
More detail and contact
This page covers BugOwl. Your Pagerly account, and how Pagerly handles data in general, are covered by Pagerly's privacy policy. If we change this page we will update the date at the top. Questions: hello@pagerly.io.