Authenticated product routes
The public marketing site is separated from authenticated product routes, and app routes are excluded from the public sitemap.
Security and trust
Security and audit data handling at Snap.
Audit firms should evaluate AI software with the same skepticism they apply to audit evidence. This page states only what Snap can support publicly and identifies the diligence topics firms should review.
Trust surface
What we can state publicly today.
Evidence traceability
Snap is designed so testing outputs can be reviewed against the source evidence used to support each result.
Diligence-ready posture
Security, retention, model-use, and access-control details should be reviewed directly during procurement and pilot diligence.
Diligence checklist
Topics to review before using any AI audit testing software.
Access controls and user permissions
Data retention and deletion
Encryption and network protections
Sub-processors and model-use policy
Audit logs and activity history
Evidence traceability and reviewer workflow
FAQ
Security questions for audit firms.
Does Snap publish a SOC 2 claim?
No public SOC 2 claim is made on this site. Audit firms evaluating Snap should request current security and compliance materials during diligence.
How should firms evaluate AI audit software security?
Firms should review access controls, retention, encryption, sub-processors, model-use policies, audit logs, and how outputs are tied back to source evidence.
Why does reviewability matter for trust?
Reviewability lets an auditor verify AI-assisted work by tracing a conclusion back to the source evidence and reasoning instead of accepting a black-box answer.
Next step
See how Snap handles real audit testing workflows.
For a pilot or diligence review, bring your firm's security questionnaire and a representative testing workflow so the technical and audit-review requirements can be evaluated together.