How ReclaimLLM maps technical security controls to SOC 2, GDPR, HIPAA, PIPEDA, and Québec Law 25 requirements. Protect proprietary intellectual property, ensure auditability, and govern developer AI workflows.
ReclaimLLM does not make false certification claims. SOC 2 Type II examination is planned for Q4 2026. This page provides the factual mapping between ReclaimLLM's shipped technical controls (pre-execution hook DLP, AES-256 session encryption, immutable audit trails, zero model training, and private VPC deployment) and standard regulatory frameworks.
Control Mappings
Review how our data isolation, encryption, and DLP enforcement features satisfy specific regulatory requirements.
Pre-execution regex and Shannon entropy masking redacts .env files and API keys before they touch model APIs or storage.
Automated risk classification flags sessions with high-risk tokens and isolates them from public or shared team views.
Raw session blobs encrypted with AES-256. Decryption keys are held by the organization, never stored in plaintext on our servers.
Structured logs capture who ran what tool, what prompt was executed, and what diffs were generated, with SIEM HTTPS export.
Contractual and technical guarantee that developer code, prompts, and tool diffs are never used to train frontier models.
Run the entire ReclaimLLM server inside your private VPC perimeter using Docker or Kubernetes Helm charts.
No. ReclaimLLM is committed to complete transparency: our SOC 2 Type II examination is targeted for Q4 2026. We do not claim active SOC 2 certification today. ReclaimLLM provides the technical control mappings and architectural features—including immutable audit logging, AES-256 encryption, and private VPC self-hosting—that enable your organization to satisfy SOC 2 Trust Services Criteria.
ReclaimLLM enforces strict zero-training policies, provides EU data residency for paid accounts, offers complete data export and permanent deletion tools (Right to Erasure), and redacts credentials and PII locally before external transit.
ReclaimLLM enforces confidentiality by default, immutable logging of all external model transfers, and pre-execution DLP masking. For Canadian public sector or healthcare buyers requiring in-country data residency (PIPEDA and Québec Law 25), ReclaimLLM offers private VPC deployment within Canadian cloud regions (such as AWS ca-central-1 or Azure Canada Central).
Yes. Enterprise customers can deploy ReclaimLLM's capture and governance server entirely inside their private AWS, GCP, or Azure VPC using Docker or Kubernetes Helm charts, ensuring no session data ever touches multi-tenant infrastructure.
Review architecture blueprints or schedule a private VPC deployment walkthrough.