Privacy Policy
Meet Attendance Tracker (Chrome extension) · Effective 9 October 2026 · Applies to version 2.1.0 and later
In short: Meet Attendance Tracker works entirely on your computer. It reads the names of people in Google Meet calls that you attend and keeps attendance records in your own browser. It has no servers, makes no network requests, and the developer never receives, sees, sells or shares any of your data.
1. Who we are
Meet Attendance Tracker is an open-source browser extension published by SahinurDEV. The source code is public at github.com/SahinurDEV/Meet-Attendance-Tracker, so anyone can check that this policy matches what the extension does.
2. What the extension processes
The extension only runs on https://meet.google.com/* pages. While you are in a call, it reads information that Google Meet already shows on your screen:
| Information | Why |
|---|---|
| Display names of meeting participants (as shown by Meet) | To build the attendance list |
| When each participant appears and disappears, and Meet's on-screen "speaking" indicator | To calculate first seen, last seen, time in call and approximate speaking time |
| Meeting code, meeting title (if shown) and start/end time | To label and group meetings |
| Chat messages shown in Meet's chat panel (sender, time, text), only if "Save meeting chat" is on | To include the chat in your meeting record and exports |
| Information you type into the extension: rosters (names and optional emails), tags, notes, settings | To mark expected attendees as Present, Late or Absent and organise your meetings |
The extension does not access audio, video, camera, microphone, screen content, your Google account, your contacts, your browsing history, or any website other than Google Meet. It does not use cookies, fingerprinting, analytics, advertising or tracking of any kind.
3. Where the data is stored
Everything is stored only in your browser's local extension storage (chrome.storage.local) on your device. It is not synced to your Google account and is never uploaded anywhere. Uninstalling the extension deletes this storage.
4. Sharing and transfer
The extension makes no network requests: it contains no code that sends data off your device, and it loads no remote code. The developer has no server and receives no data. Nothing is sold, shared with or transferred to third parties.
Files you export (CSV, Excel, PDF, JSON) or copy to your clipboard are created on your device by your own action. What happens to them afterwards (for example, emailing a report) is up to you.
5. Permissions
- storage: to save your settings, rosters and attendance history locally.
- Content script on meet.google.com: to read the participant list, speaking indicators and (optionally) chat on Google Meet pages only.
- Keyboard shortcuts use Chrome's
commandsAPI, which requires no permission.
6. Your control
- Turn auto-save, chat capture and other features on or off in Settings.
- Delete any single meeting, or all meetings at once, from the dashboard.
- Export a JSON backup of your data, or remove everything by uninstalling the extension.
7. Limited Use
The use of information processed by this extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide the extension's single purpose, taking attendance in Google Meet, and is never used for advertising, credit-worthiness or lending, or any purpose unrelated to that feature, and is never read by humans other than you.
8. Your responsibility when recording attendance
You are responsible for using the extension in line with your organisation's policies and applicable laws, including informing participants where required.
9. Children
The extension does not knowingly collect personal information from anyone, including children, because it collects nothing at all; all processing stays on the device of the person who installed it.
10. Changes
If this policy changes, the updated version will be published on this page with a new effective date. Any future optional feature that sends data off the device (for example, optional Google Sheets sync on our roadmap) would be strictly opt-in and described here before release.
11. Contact
Questions or concerns: see the support page, open an issue on GitHub, or email infosahinur@gmail.com.