Security overview
Scans only read. Provider access and refresh tokens are stored server-side only and encrypted at rest when real auth is enabled.
Sessions use HTTP-only cookies. Production cookies are configured for Secure and SameSite=Lax. Connecting a drive grants file access that only a paid cleanup uses, and only to move files to the provider's recoverable trash.
API routes check scan ownership before returning cleanup plans or deleting scan data. File contents are not downloaded for exact duplicate detection.
Deleting a drive removes its stored authorization tokens, scan history, and related scan data. Google and Dropbox authorization is also revoked at the provider. It does not sign the user out of the provider or browser.
Contact and support
Questions, support requests or security reports: email support@clearcopies.com. We answer within two business days. Account and data deletion is described on the data deletion page.
Production control review · August 2026
Checked across scan, payment and cleanup
Production scans only read, keeps provider tokens server-side, moves files only after a verified payment, and revalidates every selected item before moving it to recoverable trash.
- Read-only
- scans
- After payment
- file moves
- Per file
- cleanup revalidation
These controls were reviewed against the deployed workflow rather than only the marketing copy. Cleanup remains governed by the independent server safety gate.
Written by ClearCopies Editorial · Technical review by ClearCopies Engineering