Skip to content

Privacy policy

Last updated November 16, 2026.

midge.dev, its free tools, the Midge Chrome extension and Midge for Mac are provided to the community free of charge. We do not sell anything. You can reach us at [email protected].

Website

We count visits on our own server, without cookies and without a tracking script. Each visitor gets an anonymous ID that changes every day; your IP address is never stored. We see the first page you opened, how many pages you loaded, the website or link tag that sent you, your approximate country and the kind of device. If you join the waitlist or create an account that day, we note it on that day's visit so we know which channels people find Midge through.

The docs at midge.dev/docs are hosted by Mintlify and reach you through our server. Mintlify receives your IP address and browser details when you open them, and counts visits to the docs. Your midge.dev sign-in is never sent to Mintlify.

Your account

Your account keeps your email address, or the one Google, GitHub or Apple gives us when you sign in with them, and the name you give. When you create an account, we ask once for your name and what type of work you do (for example Engineering or QA), so teammates know who sent a report and we know who Midge is for. You can ask us to change or delete them at any time.

Product news by email is off unless you tick the box when you sign up or turn it on under Settings › Notifications, and you can turn it off there at any time. We keep a record of when you turned it on or off.

Get notified list

If you joined the list before the extension launched, we keep your email address, the page you joined from and your approximate country. We use it only to send one email about the launch. Ask us at any time and we will delete it.

If you ask in the app to hear about Midge for Mac, we note it on your account and send one email when it's out.

Free tools

The HAR viewer, HAR sanitizer and JWT decoder run entirely in your browser. Files and tokens are never uploaded.

Chrome extension

What the extension collects

On web pages, except the sites in your Never capture on list, the extension keeps the last five minutes of:

This stays in memory and in the extension's own storage on your device, and anything older than five minutes is dropped. When you take a screenshot or record, the extension also keeps the image or video you made. Instant replay keeps a recording of the page for the last 30 to 120 seconds; it is off until you turn it on for a site or for every site. Your microphone is used only while you record, and only if you turned it on.

When data leaves your device

Nothing leaves your device until you create a report. When you click Create, the extension uploads what you captured and the logs from the same moments to midge.dev, under your account. Before that, sensitive values are removed in your browser: passwords and secret fields, cookies, authorization headers, tokens in addresses, API keys and private keys are replaced, and email addresses and phone numbers are half masked. The review page shows how many values were removed. Password and card fields are blurred in screenshots and tab recordings. A capture you don't upload stays on your device until you discard it.

What is never collected

We don't sell data and we don't show ads.

Permissions the extension asks for

Your reports

Reports are stored so you can share them. You choose who can open each one: anyone with the link, the members of your workspace, or only you. You can delete a report at any time, and its files are deleted with it. To stop a browser from uploading, disconnect it in the extension's settings or remove it under Devices on midge.dev.

Midge for Mac

What the app records

Midge for Mac records only when you start a recording: the screen, window or area you choose and, if you turn them on, your camera, your microphone and the sound from your Mac. macOS asks you once to allow each of these and shows when your screen is being recorded.

While you record, the app uploads the video to midge.dev under your account, a few seconds at a time, so the link is ready moments after you stop. Nobody can open it until you click Create, which sends the title, description and trim you chose. If you delete the draft, start over or cancel, the app deletes the upload too, and an upload you never create is deleted from midge.dev within a day. The draft stays on your Mac until you create it or delete it.

Last 30 seconds

If you turn on “Keep the last seconds” in the app's settings, it keeps the picture of one screen, without sound or camera, for the last 30, 60 or 120 seconds, in memory only. Nothing is written to disk or uploaded until you save it with its shortcut; then it becomes a draft like any recording. macOS shows that the screen is being recorded, the menu bar icon shows a grey light, and the app says it's on each time it opens. It waits while your Mac is on battery or in Low Power Mode.

Logs from Chrome

If you turn on “Send this browser's logs to Midge for Mac” in the Chrome extension's settings, Chrome asks your permission once, and the extension then talks to the app on your Mac only. When the app records your screen, the extension adds the console and network logs of the Chrome tabs in the picture, with passwords, tokens, cookies and card numbers removed in the browser before anything reaches the app. For a screenshot, it adds the five minutes before. Turn the setting off and the extension stops talking to the app.

Logs from Safari

Midge for Mac comes with a Safari extension. It does nothing until you turn it on in Safari's settings and allow it on websites. Then, when the app records your screen, it adds the console and network logs of the Safari tabs in the picture, with passwords, tokens, cookies and card numbers removed before they leave Safari. The extension talks only to the app on your Mac, through a folder they share; it sends nothing anywhere else.

Logs from Electron apps

For an app built with Electron (VS Code, Slack and others), the app offers to restart it so it can read its logs. It asks every time, and the app restarts only if you agree. The app then opens it with a debugging port that listens on your Mac only, adds the console and network logs of its windows to your recordings and screenshots, with passwords, tokens, cookies and card numbers removed on your Mac before anything is uploaded, and offers to restart it normally when you're done. While that app runs this way, other programs on your Mac could read its data, which is why the app tells you before and offers to end it after.

Connecting your account

You connect the app through midge.dev in your browser. It keeps its sign-in key in the macOS Keychain and sends the name of your Mac, so you can recognise it under Devices on midge.dev and disconnect it there or in the app's settings.

What the app doesn't do

Recording links

A workspace can send a recording link to people outside it. Someone who opens the link and records their screen sends that video, their voice if they allow the microphone, and the name, email and description they choose to give. It goes to that workspace only, and is handled like the workspace's other recordings, including the AI summary and transcript below. Nothing is recorded or sent before they click Start and Send. The workspace, not Midge, decides what to do with it; to have it removed, contact them or us.

The website SDK

A workspace can add Midge's SDK to its own website, on domains it has verified. While the page is open, the SDK keeps the page's console messages, network requests, clicks and page changes, plus the details the site chooses to add (for example a user ID or plan), in the browser's memory for up to five minutes. Nothing is sent unless the visitor clicks Report a bug, records and clicks Send. Then the video and the logs of the recording go to that workspace only, after the same redaction as the extension removes passwords, tokens, cookies and similar values in the browser. The workspace runs the site and decides what to do with these reports; for those, Midge processes data on its behalf.

AI summaries

When a report is ready, Midge writes a title (if it was sent without one), a short summary, the steps to reproduce and the likely cause. To do that it sends Anthropic's Claude API the report's description, page titles and addresses, its console errors, failed requests and steps (the redacted versions; nothing that was removed before upload), and what it shows: the screenshot, or a few still frames of the video, scaled down. Pictures aren't redacted beyond what you blurred before sending, so blur anything private first. Anthropic processes all this to produce the summary and doesn't use it to train its models. A workspace admin can turn AI summaries off for the whole workspace. Each person gets 30 summaries a month.

Slack, Linear, Jira, GitHub and webhooks

A workspace admin can connect a Slack channel or add webhook addresses. New reports in that workspace (not “Only me” ones) are then sent there: their title, link, who made them, counts of errors and failed requests, and their AI summary. Slack only gets a link to post into the channel the admin chose; Midge reads nothing from Slack. With Linear and Jira, Midge reads the list of teams or projects and creates the issues people ask for, with the same details; it keeps their sign-in tokens for that until an admin disconnects them. With GitHub, Midge acts as its own app on the repositories the admin installed it on, and only opens issues there.

AI coding assistants

You can make a token on midge.dev for a coding assistant such as Claude Code or Cursor. With it, the assistant reads the reports you can open (their redacted console, network requests and steps) through our MCP server at midge.dev/mcp. It can only read. What the assistant then does with that data is up to the assistant and its provider. The token is listed under Connected devices with when it was last used, and signing it out stops it at once.

Notifications and messages in the app

Midge for iPhone and Android can show notifications and messages about Midge: new features, tips and, later, offers. Notifications about your own recordings (a recording is ready to send) are separate and only need your phone's permission. News and offers are off until you turn them on in the app's Settings, and you can turn them off there at any time; when you're signed in, that one setting covers all your phones. Messages shown inside the app have their own switch in Settings.

To send them, the app registers with Midge: a random install number, the notification address Apple or Google gives it, the app version, language, region setting and time zone, and when the app was last opened. If you're signed in, this is linked to your account so Midge can choose messages from how you use it (for example how many reports you sent this month). If you never signed in, it isn't linked to a name or email. Midge keeps a record of each change to these switches, and what happened to each message (sent, opened, dismissed). Notifications go through Apple Push Notification service and Firebase Cloud Messaging (Google). Signing out unlinks the install from your account.

Activity notifications tell you when something happens to your work: someone answered your recording link, commented on or mentioned you in a report, a report came in through your website or app, a teammate joined, or someone watched your report for the first time. They show who and which report (its title), never the text of a comment. They are on by default, need only your phone's permission, and each kind has its own switch in the app's Settings. Notices about your own account, such as how many AI summaries you have left this month, also need only your phone's permission and never carry offers.

Report views

When someone other than its creator has a report open for 5 seconds, Midge counts a view. For someone signed in, it stores their account; for anyone else, a code made from their network address and browser that changes every day, never the address itself. Link previews (for example in Slack) don't count. The report's workspace sees how many people viewed it and the names of teammates among them; anyone else is shown as “someone”.

Cookies

We only use cookies that are needed to keep you signed in. We do not use advertising or tracking cookies.

Your rights

You can ask for a copy of your data, its correction or its deletion by writing to [email protected].