Privacy & Security
This page explains Octoclip's security boundaries across capture, storage, transfer, and display, plus practical controls you can enable.
Data lifecycle
| Stage | Default behavior | Your controls |
|---|---|---|
| Capture | Records clip content generated from copy actions | Exclusion rules and source filtering |
| Storage | Saves history locally | Retention, capacity limits, manual cleanup |
| Transfer | Uses encrypted channels during sync | Enable/disable sync, define scope |
| Display | Shows content previews in history | Redaction and visibility controls |
Security baseline
1
Minimize capture scope
Exclude sensitive apps and unnecessary sources.
2
Minimize sync scope
Prefer metadata-only sync first, then expand only when required.
3
Clean sensitive data regularly
Apply short retention for OTPs, key fragments, and secret-like content.
DANGER
Never expose credentials, keys, or tokens in public repositories, issue trackers, or screenshots.
Risk scenarios
Related docs
Was this page helpful?