ChatGPT Export to Markdown - Local Backup that Checks for Missing Messages 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: pdnhlmemogefnkfeflifmjjkkfcfopmh
Permissions (1)
- Store local data
Related extensions
ChatGPT BackupProductivity
ChatExport – Export ChatGPT to PDF, TXT, Markdown & HTMLProductivity
ChatGPT Exporter — Export Chat to PDF, Markdown, JSON & CSVProductivity
ChatGPT Exporter - Save Chats as PDF & MarkdownProductivity
ChatSave — Export ChatGPT to Markdown & PDFProductivity
ChatGPT Extractor – Export Chats to PDF, Markdown & JSONProductivity
Frequently asked questions
Is ChatGPT Export to Markdown - Local Backup that Checks for Missing Messages safe to use?
Our latest automated scan rates the Chrome listing of ChatGPT Export to Markdown - Local Backup that Checks for Missing Messages at 95/100 (low 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 ChatGPT Export to Markdown - Local Backup that Checks for Missing Messages require?
ChatGPT Export to Markdown - Local Backup that Checks for Missing Messages requests 1 permission. The most significant: Store local data. See the full breakdown in the security report.
Who develops ChatGPT Export to Markdown - Local Backup that Checks for Missing Messages?
ChatGPT Export to Markdown - Local Backup that Checks for Missing Messages is published by Wade. 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
- 0.20.1
- Current listed version
- 0.20.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 0 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.