AI Meeting Notes & Google Meet Recorder extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: leikppilnchhhmebcmgejjmieddhbboa
Permissions (8)
- View open tabs
- Capture tab content
- Execute scripts in pages
Related extensions
AI Meeting Note TakerProductivity
AI Note Taker & Live Transcription for Google Meet, Zoom & TeamsProductivity
Acta: AI Meeting Notes for Google Meet, Teams & Zoom – No BotProductivity
AI Meeting Assistant — Live Meeting NotesProductivity
AI Meeting Note Taker - Transcripts, Summaries & TasksProductivity
AI Meeting AssistantProductivity
Frequently asked questions
Is AI Meeting Notes & Google Meet Recorder safe to use?
Our latest automated scan rates the Chrome listing of AI Meeting Notes & Google Meet Recorder at 69/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does AI Meeting Notes & Google Meet Recorder require?
AI Meeting Notes & Google Meet Recorder requests 8 permissions. The most significant: View open tabs, Capture tab content, Execute scripts in pages. See the full breakdown in the security report.
Who develops AI Meeting Notes & Google Meet Recorder?
AI Meeting Notes & Google Meet Recorder is published by AC SOFTWARE SOLUTIONS. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 1.10.9
- Current listed version
- 1.10.8
- Scan date (UTC)
- Assessment status
- Completed
The current store version differs from the checked package. These results describe version 1.10.9; they do not verify version 1.10.8.
Recorded findings: 0 critical and 3 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.