Support
Need help? We're here for you. Check the FAQ below or reach out directly.
Contact Us
Frequently Asked Questions
Why does SOC2Snapp need access to all URLs?
SOC2Snapp needs this permission so it can take screenshots on any webpage you're auditing. It does not read, change, or interact with page content in any way. It only takes a screenshot when you explicitly trigger a capture.
Where are my screenshots stored?
Screenshots are stored locally in your browser. They never leave your device unless you explicitly download them to disk. There is no cloud storage or server-side retention of your images.
How does export work?
Save individual captures as image + signature files, or use Save as PDF to combine all captures into a single report. Everything stays on your machine — there are no server-side components or cloud uploads.
How do I uninstall SOC2Snapp?
Right-click the SOC2Snapp icon in your Chrome toolbar and select "Remove from Chrome", or go to your Chrome extensions page and click Remove. All local data (screenshots, audit logs, settings) is deleted when the extension is removed.
What compliance frameworks does SOC2Snapp support?
SOC2Snapp includes built-in presets for SOC 2 Type II, SOC 1 Type II, HIPAA, and ISO 27001. Each preset configures the appropriate metadata, signing, and redaction settings. You can also create a custom configuration.
Is SOC2Snapp open source?
SOC2Snapp is not currently open source, but our permissions, data handling, and architecture are fully transparent. See our Security Architecture page for complete details.