Last active
July 29, 2026 14:14
-
-
Save fabriciocarraro/a9b9fb6957d12ac11e084acf4cc7f262 to your computer and use it in GitHub Desktop.
Privacy Policy - Fred: meeting notes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Privacy Policy — Fred: meeting notes without the bot (Chrome extension) | |
| Last updated: 2026-07-29 | |
| ## What this extension is | |
| Fred is a meeting-recording extension used by a single team with its own | |
| self-hosted Fred server. It records meetings you are in (with the recording | |
| indicator visible) and uploads the audio to **your team's own server** so it | |
| can produce transcripts and meeting notes. It does not work without such a | |
| server, and the extension's developer operates no server and receives no | |
| data. | |
| ## What data it handles | |
| - **Audio**: the meeting tab's audio and, if you grant the microphone | |
| permission, your own voice. Recording happens only after you explicitly | |
| start it and is always indicated on the extension icon (REC). | |
| - **Meeting page content**: the names shown on the meeting page's participant | |
| tiles and who is currently speaking, captured while you record so the notes | |
| can attribute sentences to speakers. No other page content is read. | |
| - **Configuration**: the server URL and your personal access token, stored | |
| locally in your browser (`chrome.storage.local`), never synced to Google. | |
| ## Where data goes | |
| All recorded audio and speaker events are sent **exclusively to the server | |
| URL you configured** — a server operated by your own team, typically | |
| reachable only inside your organization's network or VPN. Nothing is sent to | |
| the extension developer, Google, or any third party. There is no analytics, | |
| no telemetry, no advertising, and no sale of data of any kind. | |
| What happens to the audio after upload is governed by your team's server: | |
| in the standard Fred deployment, audio is processed locally on that machine | |
| (transcription, speaker naming, summaries) and old recordings are deleted | |
| automatically after a retention period; consult your team's administrator. | |
| ## Data retention in the browser | |
| Audio is streamed to your server in small chunks during the recording and is | |
| not kept in the browser afterwards. The stored configuration (server URL, | |
| token) persists until you remove it in the extension's Options or uninstall | |
| the extension. | |
| ## Your choices | |
| - The microphone permission is optional and granted only on the Options page; | |
| without it, only the meeting tab's audio (the other participants) is | |
| recorded. | |
| - You choose when a recording starts and stops; there is no automatic or | |
| hidden recording. | |
| - Removing the extension removes all locally stored configuration. | |
| - Your access can be revoked centrally by your team's administrator, which | |
| immediately disables uploads from your token. | |
| ## Contact | |
| This extension is operated privately by the team that runs the corresponding | |
| Fred server. For any privacy question or request, contact your team's Fred | |
| administrator. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment