Docs
Cloud History Sync
Optional, end-to-end encrypted history sync across devices. Your data is encrypted in your browser before upload, and we cannot decrypt it.
How it works
- Client-side encryption: AES-256-GCM, key derived locally from your account identity; key never leaves your device.
- Encrypted blobs only: the server stores encrypted history and basic metadata (timestamps, tool name, character counts).
- Zero-knowledge architecture: we cannot decrypt or read your history.
- Opt-in: disabled by default; enable in Settings → History & Privacy.
- Cross-device: sign in on another device, we fetch and decrypt in your browser.
Retention & limits
- Pro: 100 entries per tool, auto-delete after 90 days.
- Local history: stored in your browser; configurable limit (5/10/25/50/100).
- Delete anytime: per-tool delete, or delete all cloud history in Settings.
- Export: local history export (JSON) and cloud history export (all tools) available in Settings.
Privacy notes
- Do not paste secrets (passwords, API keys, PHI); we cannot decrypt your data, but you should avoid storing sensitive material.
- Encryption keys are never sent to our servers.
- Share/Email features are separate, opt-in flows; those send content to our backend briefly.
Quick start
- Sign in or create an account.
- Go to Settings → History & Privacy.
- Enable “Cloud History Sync” and verify connectivity.
- Export/delete cloud history anytime from Settings.
Need help? Email support@cleantextlab.com.