Deducr — We deduce what you actually pay. 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: pdmebjghkahpeimndmabnilnneoodlok
Permissions (1)
- Store local data
Related extensions
Frequently asked questions
Is Deducr — We deduce what you actually pay. safe to use?
Our latest automated scan rates the Chrome listing of Deducr — We deduce what you actually pay. at 89/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 Deducr — We deduce what you actually pay. require?
Deducr — We deduce what you actually pay. requests 1 permission. The most significant: Store local data. See the full breakdown in the security report.
Who develops Deducr — We deduce what you actually pay.?
Deducr — We deduce what you actually pay. is published by kyle.huscher. 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.2.0
- Current listed version
- 0.2.0
- 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.