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
Data Minimization
Choose capture channels deliberately and retain only the media your workflow needs. The released RTStream V2 indexing flow requiresstore=True when a continuous VLM output will be indexed.
- Live monitoring dashboards with deliberate channel selection
- Privacy-sensitive contexts that minimize captured inputs
- Workflows with documented retention controls
Retention Patterns
Define Your Retention Policy
- Document what is captured, why it is retained, and who can access it
- Use the capture SDK’s per-channel
storecontrol to minimize collection - Confirm product- and account-specific retention controls before making guarantees to users
Manual Deletion
Recommended Patterns
API Key Security
Key Management
- Never embed keys in client applications
- Use environment variables
- Rotate keys periodically
- Use separate keys for dev/prod
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
Map consent and capture records to your own user identity, then implement authenticated access and deletion-request workflows in your application. Python can list capture sessions by collection and status, but it has noend_user_id filter and CaptureSession.delete() is not available. Keep the user-to-resource mapping and deletion orchestration in your application until a supported lifecycle API is available.
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
- Minimize stored channels when storage is not needed
HIPAA
- Minimize captured and stored data 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
- Minimize collection - 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