Privacy: the Jantar Meetings extension
extension v0.5.2 ยท last updated 31 October 2026
The extension sends nothing to us: there is no Jantar server. It talks only to Jantar on your own Mac, at http://127.0.0.1. One thing leaves your Mac, and only so the summary can be written: a meeting's transcript text goes to Anthropic through Claude Code on your own account. Screenshots never leave the Mac.
What it reads, and when
- Before you press Start notes: only whether you are in a call, and the page title (to fill in the meeting's name).
- After Start notes: the captions already on screen, then each new one, with the speaker's name and the time. These are the site's own live captions; captions must be on, and the extension never turns them on for you.
- Screenshots: of the meeting tab only, and only when you click the camera button, press the shortcut (Option+Shift+S) or choose Screenshot in the popup. On the first real calls, screenshots did not reach Jantar yet (the Meetings checks).
- It runs only on Google Meet (
meet.google.com) and Microsoft Teams on the web (teams.microsoft.com,teams.live.com,teams.cloud.microsoft).
What it keeps, and where
For each meeting, Jantar on your Mac keeps: its name, the site, the project and people you gave it, when it started and ended, every caption line with its speaker and time, your screenshots (JPEG), and the summary with its decisions and action items. The text is in meetings.db and the images in meetings/ inside your Jantar state folder (~/.jantar). The extension itself keeps only its pairing key and its settings, in Chrome's storage for the extension.
What leaves your Mac
After a meeting ends, its transcript text (the name, day, project, people and caption lines) goes to Anthropic through Claude Code on your account, the same way any Claude Code use does, so one Claude run can write the summary. Screenshots never leave the Mac. Your phone reads meetings from your Mac through the front door you set up (Tailscale, or your Cloudflare Tunnel). Nothing goes to the people who make Jantar.
Permissions, and why each is there
activeTab- To take a screenshot of the meeting tab when you click the Jantar icon or press the shortcut.
storage- To keep the pairing key and settings.
- Access to
http://127.0.0.1 - To send captions and screenshots to Jantar on your Mac.
- Page script on Meet and Teams
- To read the captions after Start notes, and to show the camera button.
- Optional: all sites
- Asked once, only if you allow it, so the camera button can take a screenshot without a click on the toolbar icon first. Chrome words the prompt for the widest case ("Read and change all your data on all websites"); the page script still runs only on Meet and Teams, and the extension photographs only the meeting tab, only when you ask. You can narrow it again in Chrome's Site access settings.
What it never does
- Record audio or video, or read the call's media.
- Join the call as a bot.
- Read a page before you press Start notes, beyond the two things above.
- Take a screenshot without your click, your shortcut or the popup.
- Talk to anything but Jantar on your Mac, or load code or images from anywhere.
- Sell, share or transfer what it reads, or use it for advertising.
How long it is kept, and how to delete it
Meetings are kept until you delete them. Delete one on the phone (with five seconds to Undo), or everything at the Mac with the steps in the extension guide (Deleting everything). jantar meetings unpair revokes every paired extension, and you can remove the extension in chrome://extensions. Time Machine may still hold older copies of these files.
Telling people you keep notes
Captions show only on your screen, and Meet and Teams tell no one that you keep them. Say so at the start of the call. Before you keep anyone's words, check what your workplace expects, and what the law says where the people are.
This website
This site sets no cookies, runs no analytics and loads nothing from another server. Your theme choice is kept in this browser's local storage. GitHub, which hosts the site, may log visits under its own privacy statement.
Changes and questions
Changes to this page are in the repository's history, and the date above moves with them. Questions: open an issue on the repository. Security problems: use GitHub's private vulnerability reporting (how). No e-mail address is published for this project.