Resources
Security
Security practices, compliance controls, and data protection at Tork.
Security Overview
Tork is built with security as a foundational principle. We implement industry-leading security practices to protect your data and help meet compliance requirements.
SOC 2 Type II
Not certified — controls designed to align
Encryption
AES-256 at rest, TLS 1.3 in transit
Privacy
GDPR and CCPA compliant
API Key Security
Best practices for managing your API keys:
Use Environment Variables
Never hardcode API keys in source code
Rotate Keys Regularly
Rotate production keys every 90 days
Scope Permissions
Use the minimum permissions required
Monitor Usage
Set up alerts for unusual API activity
Separate Environments
Use different keys for dev, staging, and production
An API key is only needed to reach the Tork cloud API. There is no Python cloud client — from Python, call the REST API directly with a Bearer token. The cloud client class TorkClient ships in @torknetwork/sdk (npm), which is a different package from the on-device tork-governance family.
tork-governance makes the governance decision on your machine. PII detection, redaction and the returned verdict are computed on-device. With no API key it makes zero network calls: prompts, completions and detected PII values never leave the machine, and nothing appears in your dashboard.
Data Handling
How we handle your data:
| Data Type | Retention | Encryption |
|---|---|---|
| Audit Logs | 90 days (configurable) | AES-256 |
| Policy Configs | Until deleted | AES-256 |
| Agent Metadata | Until deleted | AES-256 |
| Content (if stored) | 24 hours | AES-256 |
| PII (detected) | Not stored | N/A |
Content passing through Tork is processed in memory and not persisted unless explicitly configured for audit purposes.
Network Security
Infrastructure security measures:
Infrastructure
- Infrastructure providers (Supabase, Vercel) hold SOC 2 Type II certification
- VPC isolation for all services
- Regular penetration testing
- WAF and DDoS protection
Compliance
- Tork is not SOC 2 certified — controls designed to align with SOC 2 Type II
- GDPR compliant
- CCPA compliant
IP Allowlisting
Restrict API access to specific IP addresses:
Webhook Security
Secure your webhook endpoints:
Security Incidents
If you discover a security vulnerability:
Responsible Disclosure
Please report security vulnerabilities to:
We respond to all reports within 24 hours and aim to resolve critical issues within 72 hours.
Request Audit Documentation: Enterprise customers can request current compliance documentation and completed security questionnaires from security@tork.network. SOC 2 Type II is in progress — see the Trust Center for current status.