When to Reference This
Use this page when you’re:- Designing systems with privacy requirements
- Choosing storage and retention policies
- Implementing consent workflows
- Securing API access patterns
Quick Example
Next Steps
Capture Session
Secure desktop capture patterns
API Reference
API key management
Storage Modes
Persistent Storage (Default)
Media and derived data are stored for retrieval and search:- Video archives and libraries
- Searchable knowledge bases
- Long-term agent memory
Ephemeral Processing
Process in real-time without persistent storage:- Live monitoring dashboards
- Real-time alerts without storage
- Privacy-sensitive contexts
Retention Patterns
Default Retention
- Media stored until explicitly deleted
- Indexes and metadata stored with media
- No automatic expiration
Manual Deletion
Recommended Patterns
| Use Case | Pattern |
|---|---|
| Temporary analysis | Ephemeral mode |
| GDPR compliance | Implement deletion on user request |
| Meeting recordings | Define retention policy, batch delete |
| Security footage | Time-based archival and deletion |
API Key Security
Key Management
- Never embed keys in client applications
- Use environment variables
- Rotate keys periodically
- Use separate keys for dev/prod
Key Operations
Client Token Pattern
For desktop and mobile clients, use short-lived tokens instead of API keys:- Tokens expire automatically
- Tokens have limited scope
- Compromised tokens have limited blast radius
- API key never leaves your backend
Consent Patterns
User Consent for Capture
Before capturing screen, mic, or camera:Data Subject Access
Implement endpoints for user data requests:Network Security
HTTPS
All API communication uses HTTPS. No configuration needed.Webhook Security
Verify webhook payloads to prevent spoofing:Compliance Considerations
GDPR
- Implement data access endpoints
- Implement deletion endpoints
- Document data processing purposes
- Use ephemeral mode when storage isn’t needed
HIPAA
- Use ephemeral mode for sensitive content
- Implement strict access controls
- Audit all data access
- Consider on-premise deployment for PHI
SOC 2
- VideoDB maintains SOC 2 compliance
- Implement access logging
- Use separate keys per environment
- Regular key rotation
Best Practices Summary
- Never expose API keys - Use client tokens for untrusted clients
- Default to ephemeral - Only persist data when needed
- Implement deletion - Honor data deletion requests
- Short token lifetimes - 10-15 minutes for desktop capture
- Audit access - Log who accesses what data
- Encrypt at rest - VideoDB encrypts stored data
- Get consent - Always get user permission before capture