Privacy & Security
Use this page to understand the data boundaries around capture, local storage, sync, and reuse in Octoclip, plus the settings to adjust first when clips may contain sensitive content.
Data lifecycle
| Stage | What happens | User controls |
|---|---|---|
| Capture | Octoclip may record clipboard or supported source content into local history | history toggle, source exclusion, filter rules |
| Local storage | Clip history is kept in the app's local data area | retention, cleanup, delete, app/platform storage controls |
| Nearby Sync | Content transfers between paired/nearby devices over the local path | enable/disable sync, pairing, local network permissions |
| Cloud Sync | Selected data syncs through the configured WebDAV / S3 path, end-to-end encrypted with a key you hold | provider choice, credentials, your encryption key, sync scope; config import/export varies by version |
| Display and reuse | Clips appear in history, search, Quick Input, aliases, or previews | visibility, deletion, favorites, filters |
Boundaries to know
- Cloud Sync uses the WebDAV / S3 path you configure. You are responsible for checking that provider's account access, permissions, region, retention, and backup behavior.
- Nearby Sync is for local or nearby device transfer. Stability depends on the local network, pairing, local network permissions, and firewall rules.
- Do not treat Cloud Sync as default storage on Octoclip-owned cloud infrastructure. The actual path depends on the sync mode and provider you configure.
- Do not treat any clipboard tool as an absolutely secure vault. Keep OTPs, tokens, keys, passwords, and other sensitive clips short-lived, local-only, or excluded from capture.
Assumptions to avoid
- Every platform captures, pastes, and syncs in exactly the same way.
- Turning on sync means every clip reaches every device in real time.
- A feature keeps the full experience after a required permission is disabled.
- Sensitive content captured by mistake can be left for sync or storage settings to handle automatically. Delete the item and add exclusion or filter rules.
Security baseline
1
Minimize capture scope
Exclude sensitive apps or sources whenever possible.
2
Minimize sync scope
Start with collections and aliases before syncing full clip history.
3
Keep sensitive clips short-lived
Use short retention, manual deletion, or local-only workflows for OTPs, tokens, keys, and secrets.
4
Keep support logs clean
Do not send passwords, tokens, API keys, or private clipboard content in screenshots, logs, or forum posts.
Risk scenarios
Related docs
Data & Security overview
Entry to the feature-side notes on local, cloud, backup, and privacy.
Privacy and sensitive content
Practical controls for sensitive clips, exclusions, and sync scope.
Cloud Sync
Understand WebDAV / S3 sync scope and behavior.
Account and license
Understand paid features and activated devices.
Was this page helpful?
