Presently – Recording, Attendance & AI Notes for Google Meet™ 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: kldniiihggpmolgcjlefnnkfonfoicmh
Permissions (10)
- Capture tab content
- Execute scripts in pages
- Manage downloads
Related extensions
AI Note Taker & Live Transcription for Google Meet, Zoom & TeamsProductivity
Record MeetingProductivity
Annotate & Record for Google Meet: Visible to everyone including presenterProductivity
Meeting Notes AssistantProductivity
AI Meeting Notes & Google Meet RecorderProductivity
AI Meeting AssistantProductivity
Frequently asked questions
Is Presently – Recording, Attendance & AI Notes for Google Meet™ safe to use?
Our latest automated scan rates the Chrome listing of Presently – Recording, Attendance & AI Notes for Google Meet™ at 79/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 Presently – Recording, Attendance & AI Notes for Google Meet™ require?
Presently – Recording, Attendance & AI Notes for Google Meet™ requests 10 permissions. The most significant: Capture tab content, Execute scripts in pages, Manage downloads. See the full breakdown in the security report.
Who develops Presently – Recording, Attendance & AI Notes for Google Meet™?
Presently – Recording, Attendance & AI Notes for Google Meet™ is published by snabawy@gmail.com. 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.0.1
- Current listed version
- 1.0.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 1 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.