Privacy Policy

Last updated: September 30, 2026

1. Who we are and what Brow is

Brow : AI meeting recording (“Brow”) is a macOS application developed by Anthony Fernandez, an independent developer based in France (“we”, “the developer”). Brow lives in the menu bar and the MacBook notch: it reminds you of upcoming meetings, records them on your Mac, transcribes them on-device and produces meeting notes.

The developer operates no servers for Brow, and you do not create an account with the developer. Brow talks directly from your Mac to the services you choose to connect (Google, Notion) and to the software you install yourself (Claude Code). We do not collect, receive or have access to any of your data.

2. Google user data Brow accesses

Connecting a Google account is optional. If you sign in with Google, Brow requests the following scopes. All of them are read-only: Brow never creates, edits or deletes calendar events or contacts.

https://www.googleapis.com/auth/calendar.events.readonly

Brow reads the events of the current day on your primary calendar: title, start and end time, description, attendees (email address, display name, whether you declined), the video-meeting link (e.g. Google Meet, Zoom), and the event and recurrence identifiers. This is used to show upcoming meetings in the notch, offer to record them, open the video link when you click “Join”, and attach the meeting’s title and attendees to the note of a meeting you record. Cancelled events and events you declined are ignored.

https://www.googleapis.com/auth/contacts.readonly

When you record a meeting, Brow looks up each attendee by their email address in your Google contacts and reads, if found, their name, organisation, job title and photo. This is used to display who took part in the meeting and to spell their names correctly in the note and its summary. Brow does not read or import your contact list as a whole.

https://www.googleapis.com/auth/contacts.other.readonly

If an attendee is not in your contacts, Brow looks up their email address in Google’s “Other contacts” (people you have interacted with) and reads their name only, so the note shows a real name when the invitation carries none.

openid and email (https://www.googleapis.com/auth/userinfo.email)

Used to identify the Google account you signed in with and to show its email address in Brow’s Settings.

3. How Google user data is used

Google user data is used only to provide the user-facing features described above: meeting reminders in the notch, recording prompts, and meeting notes with the right title and participants (including their summaries). Brow does not use Google user data for advertising, retargeting or interest-based ads, does not sell it, does not use it for profiling, credit or lending purposes, and does not include any analytics or tracking. Brow does not use Google user data to develop, improve or train generalized artificial-intelligence or machine-learning models.

4. Where data is stored and for how long

Everything Brow stores is stored on your Mac:

• Google sign-in tokens are stored in the macOS Keychain. Signing out in Brow’s Settings deletes them.
• Calendar events are kept in memory while Brow runs and are fetched again from Google as the day goes on. They are not written to disk, except as part of the note of a meeting you record (below).
• Attendee details found in your contacts (email address, name, organisation, job title and a link to the photo) are cached in ~/Library/Caches/Brow/people.json, so a recurring meeting does not need new lookups. An entry is looked up again from Google once it is more than seven days old. Photos themselves are loaded from Google’s image servers when displayed.
• Meeting notes are Markdown files in a folder you choose (by default ~/Meetings). A note contains the meeting’s title, date, duration, video link and calendar event identifiers, the participants (email address, name, organisation, job title and photo link, from Google Calendar and Contacts), the transcript and the summary. A search index, your note groups and your spelling dictionary are kept in an SQLite database in the .index sub-folder of that folder. If you place this folder in a synced location (for example iCloud Drive or Dropbox), your sync provider will hold a copy under its own terms.

Retention: notes, the index and audio backups are kept until you delete them — Brow never deletes your notes by itself. The attendee cache stays until you delete it or it is replaced by fresher lookups. Tokens are kept until you sign out.

5. Sharing and transfers (Limited Use)

The developer never receives your data. Brow transfers Google user data from your Mac to another service only as needed for a user-facing feature you choose to use:

• Anthropic, through your own Claude Code installation and Claude account — meeting summaries. If Claude Code is installed on your Mac and set up in Brow, Brow runs it locally after each recording to produce the summary (decisions, action items, topics). Brow passes it: the meeting title and calendar description, the participants’ names, email addresses and job titles (from Google Calendar and Contacts), a spelling list made of the participants’ names and your own dictionary entries, excerpts around moments you marked, and the transcript. Claude Code sends this to Anthropic to generate the summary, under your agreement with Anthropic for your Claude account. Brow asks Claude Code not to save the session, and runs it with no tools and no MCP servers. If Claude Code is not installed, notes are saved without a summary and nothing is sent.
• Notion — only if you connect your Notion workspace. For each meeting, Brow writes to the Notion database you choose: the meeting title, date and time, duration, participant names (or email addresses when no name is known), groups, video link, and the content of the summary, decisions, action items, topics and marked moments. The transcript is never sent to Notion. This data is then held by Notion under your agreement with Notion.
• Your Claude client, through Brow’s MCP server — only if you register it. Brow includes a local MCP server (browmcp) that runs on your Mac over standard input/output and gives read-only access to your notes (list, search, read a meeting, list action items), including participant details. It is only active if you add it to your own Claude client (such as Claude Desktop or Claude Code); what that client then sends to Anthropic is governed by your agreement with Anthropic. It never reads your voice data.

We do not transfer Google user data to anyone else, and we do not sell it. The only other circumstances in which Google user data could be transferred are those permitted by Google’s policy: to comply with applicable law, or as part of a merger, acquisition or sale of assets with your explicit prior consent.

In particular:

• Brow does not use or transfer Google user data for serving advertisements, and does not transfer or sell it to advertising platforms, data brokers or other information resellers.
• Brow does not use Google user data to develop, improve or train generalized AI and/or ML models.
• No human reads your Google user data. Because Brow has no servers, the developer has no access to it. Should that ever change, humans would read it only with your affirmative agreement for specific messages or data, when necessary for security purposes (such as investigating abuse), to comply with applicable law, or when the data is aggregated and anonymised and used for internal operations.

6. Audio, transcripts and voice data

This is not Google data, but we want you to know how it is handled:

• Recording starts only when you ask. Brow records your microphone and your Mac’s system audio to two audio files (.m4a) next to the note. You can turn off “Keep audio tracks after transcription” in Settings; the files are then deleted once the meeting is transcribed.
• Transcription and speaker separation run on your Mac with on-device models. The speech models are downloaded once from Hugging Face on first use; no audio or personal data is sent in that download.
• Voice data: if you enrol your voice or ask Brow to recognise a speaker in the future, voice prints (numerical speaker embeddings) are stored locally in ~/Library/Application Support/Brow/Voices/, separately from your notes. You can erase your voice print, forget a known voice, or erase all voice data from Settings.
• Brow never uploads your audio or voice data. The transcript leaves your Mac only as described in section 5 (summary by your Claude Code, or your own Claude client via MCP), and never goes to Notion.

7. Security

• All network requests to Google, Notion and model downloads use HTTPS (TLS). The only plain-HTTP connection is the local sign-in redirect on 127.0.0.1, which never leaves your Mac.
• Google sign-in uses OAuth 2.0 with PKCE in your browser; Brow never sees your Google password. Tokens and secrets are stored in the macOS Keychain.
• Distributed builds are signed with an Apple Developer ID, use the hardened runtime and are notarised by Apple.
• Brow contains no third-party analytics, advertising or crash-reporting SDKs.

No system is perfectly secure. Your notes are ordinary files on your Mac, protected by your macOS account (and FileVault if enabled).

8. Your controls and deletion

• Disconnect Google: sign out of Google in Brow’s Settings. This deletes the tokens from the Keychain. To also revoke Brow’s access on Google’s side, visit myaccount.google.com/permissions.
• Delete the attendee cache: delete ~/Library/Caches/Brow/people.json.
• Delete notes: delete individual notes from Brow’s Notes window or the Finder, or delete the whole meetings folder (including its .index sub-folder).
• Erase voice data: Brow’s Settings › Voice › “Erase All My Voice Data…”.
• Disconnect Notion: disconnect Notion in Brow’s Settings › Integrations. Brow revokes its Notion token and deletes it from the Keychain. Pages already created stay in your Notion workspace until you delete them there.
• Stop MCP access: remove Brow’s server from your Claude client’s configuration.
• Data held by third parties (Anthropic for summaries, Notion, your sync provider) is managed under your account with them.

Because we hold none of your data, we cannot access or delete it for you, but we are happy to help: write to dev.genyus@gmail.com. If you are in the European Union, you also have the right to lodge a complaint with your data-protection authority (in France, the CNIL).

9. Children

Brow is a productivity tool for professionals. It is not directed to children under 16, and we do not knowingly process children’s data.

10. Changes to this policy

If Brow’s handling of data changes, we will update this page and its “Last updated” date. We encourage you to review this page periodically.

11. Contact

Anthony Fernandez — dev.genyus@gmail.com