This Privacy Policy explains, clearly and honestly, how the Gravador de Calls extension for Google Chrome (the "Extension") handles data when you use it. The short version: the Extension records only the audio coming from the other participants, keeps everything on your computer and sends nothing to Enkode or anyone else.
1. Who is responsible
Publisher of the Extension: Enkode
Contact e-mail: jefersonftlopes@gmail.com
Whenever this policy says "we" or "Enkode", it refers to the publisher of the Extension. Enkode does not receive your recordings or your call data: they stay only on your computer, under your control (section 5).
2. What the Extension is
Gravador de Calls records, tab by tab, the audio of the other participants in Google Meet and Microsoft Teams calls in Chrome, together with the call details, and saves each recording to a folder on your computer. It also has a tab mode (record what a tab plays, through the shortcut or the popup button), a per-tab volume control and an option, off by default, to leave the call and close the tab when it empties.
The Extension is an independent tool. It is not affiliated with, sponsored or endorsed by Google LLC or Microsoft Corporation. "Google Meet" and "Microsoft Teams" are trademarks of their respective owners and are mentioned here only to describe which services the Extension works with.
3. What is recorded
- Automatic recording (Meet and Teams): only the audio the call page receives from the other participants. Your microphone is never recorded. To mark in the transcript where you spoke, the Extension measures on your computer only whether there is sound on the microphone (the level, every fraction of a second), without keeping or sending the sound. Sounds from the call interface itself (join chime, notification) may appear, because they arrive through the same path.
- Tab mode: only when you trigger it (Alt+Shift+G shortcut or the popup button), it records what that tab plays, through Chrome's tab capture. It does not include your microphone either. It applies to the tab where you triggered it, including outside Meet and Teams.
- Volume for this tab: the tab's sound is processed live, in the browser, to change the volume. Nothing is recorded or stored because of it.
- Recordings contain no video, screen capture, chat, captions or typed text.
4. Which call data is kept
Along with the audio, each recording has an info.json file with:
- platform (Meet, Teams or another site in tab mode), call title (or the meeting code when there is no title), meeting code or ID, the tab's address (URL) and title;
- start and end date and time, duration and time zone;
- the participants' display names as shown in the call (best effort, read from the page) and your own display name, when the page shows it;
- who spoke and when: each participant's speaking intervals, read from the signals Meet and Teams send to the page, and the intervals when you spoke (only the moment, never the sound), in a
falantes.jsonfile in the same folder, with each person's total seconds ininfo.json; the transcript uses this to say who said each part; - the profile name you type yourself in the settings (optional);
- technical details of the recording: which audio path was used, source switches, gaps, the reason it ended (including the head count, when the auto-leave acted) and the Extension versions.
For the auto-leave (when you turn it on), the Extension reads on the page how many people are in the call. That count is used on the spot and is not kept, except in the end reason described above.
What is NOT processed: browsing history, cookies, passwords, content from other sites, advertising identifiers. The Extension uses no tracking cookies and no analytics tools.
5. Where the data is stored (only on your computer)
- Recordings: in the
Downloads/Call recordingsfolder (Downloads/Gravações de callswhen Chrome is in Portuguese), one folder per call (audio.webmandinfo.json). With the optional local helper installed (section 7), in the folder you choose. - Audio in progress: while the call is happening, the audio is kept in chunks in the Extension's local storage in the browser (IndexedDB), so it is not lost if the tab or Chrome crashes. The chunks are deleted as soon as the recording is saved to the folder.
- Settings and recent recordings: your preferences and the list of recent recordings (title, platform, date and where the file was saved) are kept in the Extension's local storage (
chrome.storage.localand IndexedDB), in your Chrome profile.
The Extension has no server, asks for no account or login and makes no network requests of its own. No recording, participant name or call data is sent to Enkode or to third parties.
6. What the data is used for
Only to provide the Extension's features to you: recording your calls, organizing each recording in a folder with the call details, showing in the popup what is recording and what was saved, and leaving the call on its own when you turn that option on.
7. Local helper and transcription (optional)
Two advanced features require a separate program, the local helper, which is not yet distributed through the Chrome Web Store: saving to a folder of your choice and transcribing each call. Without it, the Extension works normally and saves to Downloads.
When installed, the helper runs on your computer and talks only to the Extension (Chrome native messaging). Transcription also runs on your computer (whisper.cpp), and the text (transcricao.md and .srt) stays in the call folder. None of this leaves the machine.
8. What we do NOT do
- We do not sell anyone's data;
- We do not transfer or share data with third parties, for advertising or any other purpose;
- We do not use analytics, trackers or tracking cookies;
- We do not use the data to determine creditworthiness, or for any purpose unrelated to the Extension's function;
- We do not receive your recordings: they never leave your computer because of the Extension.
Limited Use (Chrome Web Store): the use of information received by the Extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
9. Participants' consent: the recorder's responsibility
The Extension records other people. You decide to record, and you are responsible for the recordings you make (in data protection terms, the controller of that data).
- In Brazil, the General Data Protection Law (LGPD, Law No. 13,709/2018) requires a legal basis to process personal data such as the participants' voices and names (for example, their consent or legitimate interest, as the case may be).
- In other countries and in several US states, the law requires the consent of all parties before a conversation is recorded.
- On installation, the Extension shows a notice about what is recorded and about consent; automatic recording stays off in that Chrome profile until you confirm it with "I understand".
- Tell the participants before recording and respect anyone who does not want to be recorded. The platforms themselves and your employer may also have rules about recording.
10. How long the data is kept
- Recordings and transcripts: they stay on your computer until you delete them. The Extension never deletes a saved recording.
- Audio in progress: only until the recording is saved. If it cannot be saved (for example, the disk is full), the popup tells you and the Extension retries every minute. A recording shorter than the minimum duration (30 seconds by default) is discarded without being saved, together with its title and participants.
- Settings and the recent recordings list: while the Extension is installed. Removing the Extension deletes everything it keeps in the browser, including the audio of a recording not yet saved; files already saved to the folder remain there.
11. Your rights
Because Enkode neither receives nor keeps your data, you already have full control: you can open, move or delete the recordings in the folder, clear the recent recordings list by removing the Extension, and turn off automatic recording per platform in the settings. A participant who wants access to, or deletion of, a recording should contact the person who recorded it. For questions about this policy, use the contact in section 15.
12. Security
- Everything stays on your computer: there is no server copy that could leak;
- The files are protected by your account on the computer. Anyone with access to it also has access to the recordings;
- The local helper, when installed, accepts messages only from the Extension and opens only transcript files inside the recordings folder.
13. Extension permissions
| Permission | What for |
|---|---|
| Access to meet.google.com, teams.microsoft.com, teams.cloud.microsoft and teams.live.com, and to the same addresses through the Microsoft Defender for Cloud Apps proxy (ending in .mcas.ms, .mcas-gov.us or .mcas-gov.ms) | Detect when the call starts and ends, record the audio the page receives and read the title and the participants' names. Only on these sites. The proxy addresses are the same Meet and Teams pages when a company opens them through the Defender for Cloud Apps session control. |
tabCapture, activeTab | Tab mode and volume for this tab: only on the tab where you used the shortcut or the popup. |
offscreen | Build the audio file and play the tab's sound in tab mode and with the per-tab volume. |
downloads | Save the recordings to Downloads/Call recordings (Downloads/Gravações de calls in Portuguese). |
storage, unlimitedStorage | Keep the settings and the audio in progress until it is saved, without hitting the quota on a long call. |
notifications | Tell you when a recording is not picking up audio, when a tab needs to be reloaded or when a recording was not saved. |
alarms | Retry saving an interrupted recording. |
nativeMessaging | Talk to the optional local helper, when installed. |
14. Children
The Extension is a work tool and is not directed at children. Enkode collects no data from anyone, children included.
15. Contact
E-mail: jefersonftlopes@gmail.com
Publisher: Enkode
We will reply within a reasonable time and as required by applicable law.
16. Changes to this policy
We may update this policy when the Extension changes (for example, if a feature that sends anything off the computer ever exists, it will be optional, off by default and described here before it applies) or when the law changes. The effective date at the top shows the current version.