Transparency is the foundation of trust. Review our compliance status, security architecture, data handling practices, and subprocessor relationships -- all in one place.
Compliance Status
Certifications and frameworks.
Real-time visibility into our compliance posture. We publish status honestly -- including what is in progress, not just what is complete.
SOC 2 Type 1In Progress
Active SOC 2 Type 1 readiness program: 8 core policies published at panguard-ai/security-policies, real-time subprocessor list, security.txt vulnerability disclosure, and incident response SLA in effect. Vanta / Drata vendor evaluation in progress; CPA engagement and formal attestation target Q4 2026 / Q1 2027.
CERTIFIED SECURE2026
ISO 27001Planned 2027
Sequenced after SOC 2 Type II. ISMS controls being designed alongside Type 1 prep so certification becomes a formalization.
PROTECTED BY PANGUARD AI
GDPR / Taiwan PDPAActive
We process minimal personal data (email + workspace name + anonymized telemetry). Data Processing Agreement available on request.
ENTERPRISEGRADE
HIPAANot in scope
Panguard does not process Protected Health Information. HIPAA-regulated customers should not transmit PHI through Panguard.
Security Architecture
Defense in depth.
Our security model is layered. A failure at any single layer does not compromise the system. Each layer operates independently with its own controls.
Data Layer
AES-256 encryption at rest (Threat Cloud)
TLS 1.3 for all data in transit
Local file permissions (0600) for CLI configuration
Skill content never leaves your machine unless you opt in
SHA-256 anonymized fingerprints only when telemetry is enabled
Application Layer
Input validation and sanitization
Local configuration file permissions (0600)
CLI authentication via local tokens
Infrastructure Layer
Local-first architecture -- all data stays on your machine
Threat Cloud hosted on SOC 2 Type II certified provider
Immutable audit log for admin actions (365-day retention)
Automated dependency vulnerability scanning
DDoS protection at provider edge
Data Handling
How we treat your data.
Every data handling practice is documented, enforced through policy, and verified through automated controls.
Data Encryption
AES-256 at rest, TLS 1.3 in transit. Local encryption for configuration and credential storage.
Data Residency
All data stored locally on your device. No cloud storage unless you opt in to Threat Cloud.
Data Retention
Configurable retention policies per data type. Automatic purging with cryptographic verification.
Access Controls
File-system permissions restrict access to configuration and data. Runs as unprivileged user where possible.
Audit Logging
Immutable audit trail for all administrative actions. Logs retained for a minimum of 12 months.
Incident Response
72-hour breach notification commitment. Written IR runbook. External tabletop exercises planned alongside SOC 2 Type 1 in Q3 2026.
Subprocessors
Third parties we work with.
We limit subprocessor usage to essential services only. Each subprocessor undergoes security review before onboarding and is re-evaluated annually.
SubprocessorPurposeLocation
AWSInfrastructure compute and storageUnited States / Global
AnthropicLLM semantic analysis (Claude API)United States
OpenAILLM semantic analysis (GPT API, opt-in)United States
SupabaseCustomer account database and authenticationSingapore / United States
StripePayment processing and billingUnited States
VercelWebsite and dashboard hostingUnited States / Global edge