Security & Privacy
Your data security and privacy are fundamental to how mimic is designed.
Data Handling Principles
mimic is built with privacy-first principles. We understand that recordings may contain sensitive business information, and we've designed our systems accordingly.
encrypted Encryption
All data is encrypted in transit (TLS 1.3) and at rest (AES-256).
home Local Processing
Screenshots are processed locally before upload when possible.
auto_delete Data Retention
Recordings are automatically deleted after processing unless you choose to save them.
Sensitive Mode
mimic includes a Sensitive Mode toggle that pauses all capture when enabled. Use this when:
- Entering passwords or authentication credentials
- Viewing confidential financial or medical information
- Accessing documents with restricted access
- Typing personal information you don't want recorded
What Is Not Captured
mimic is designed to avoid capturing certain data by default:
- Full clipboard contents: Only a short preview is logged, not complete copied text.
- System passwords: OS-level authentication prompts are excluded.
- Background applications: Only the active window is captured in screenshots.
Access Controls
Your mimic account is protected by email-based verification codes. Each session requires authentication, and tokens expire after a set period. Team administrators can manage who has access to shared recordings and automation scripts.
Permissions Required
mimic requires the following system permissions to function:
| Permission | Why It's Needed |
|---|---|
| Screen Recording | To capture screenshots of your workflow |
| Accessibility | To detect mouse clicks, keystrokes, and window changes |
| Microphone (optional) | To record voice narration during sessions |
Compliance & Auditing
For enterprise deployments, mimic supports audit logging of all recording sessions. Contact our team for information about SOC 2 compliance, data processing agreements, and on-premises deployment options.