Current Status
Pabble does not currently publish a verified SOC 2 Type II report on the marketing site.
Until a formal audit, certification, or trust report is completed and documented, Pabble should not claim SOC 2, ISO, HIPAA, formal penetration testing, specific data residency, or specific encryption-at-rest algorithms in public marketing copy.
Future trust center
Show where verified reports, subprocessors, security contacts, and compliance documents will appear once available.
Recommended visual: 1440 x 900
What Pabble Can Discuss Today
Pabble can describe product-level boundaries that are visible in the codebase and application:
- Teams, projects, forms, and responses are modeled as separate resources.
- Form responses are collected and reviewed in the dashboard.
- Integration credentials and response data are handled through separate product concepts.
- Webhook endpoints must use HTTPS.
These are product facts, not third-party compliance claims.
Trust Requests
Customers or prospects who need vendor documentation should contact the Pabble team with the specific requirement. If a document is not available, the response should say so clearly instead of implying certification.