Silk Compute Trust Center
Silk Compute maintains a security program to protect customer data. Here you can find our compliance work, security controls, subprocessors and security documents.
Compliance
- CSA STAR Level 1In progress
- SOC 2 Type IIIn progress
- ISO 27001In progress
Resources
View allControls
View allInfrastructure security19
- Production application access restricted
- Production database access restricted
- Unique production database authentication enforced
Organizational security5
- Unique account authentication enforced
- Administrator MFA enforced
- Administrator actions logged
Product security12
- Data transmission encrypted
- Data encryption utilized
- Support data encrypted at rest
Internal security procedures9
- Change management procedures enforced
- Configuration management system established
- Database changes backed up
Data and privacy6
- Prompts and outputs not stored
- Customer data not used for training
- Customer data deleted upon leaving
Subprocessors
View all- OVHcloudCloud infrastructure
- CloudflareSecurity, content delivery, account emails and encrypted backups
- AI inference infrastructureAI infrastructure
- StripeCard payments
FAQ
View allDo you use customer data to train models?
No. Silk Compute does not store prompts or model outputs and never uses them to train models.
Do you store prompts and responses?
No. Prompts and model outputs pass through our servers and are not stored. We keep billing records, such as token counts and cost.
Are prompts or responses included in logs?
No. Our logs record request metadata, such as the time, model, status and token counts.
How is customer data protected?
We use encryption in transit, restricted and key-only production access, sandboxed services, security monitoring and daily security updates. Support tickets are also encrypted at rest.
Updates
View all- Security
Encryption at rest
The production database is encrypted at rest with AES-256, as is every off-site backup, and all data is encrypted in transit.