Encrypted OAuth tokens
Access and refresh tokens are encrypted at rest with AES-256 before they are stored. We never store your cloud passwords.
Transfers run on our workers. Your files land in your cloud accounts — we do not keep copies.
Access and refresh tokens are encrypted at rest with AES-256 before they are stored. We never store your cloud passwords.
Bytes pass through workers during an active transfer only. We keep job metadata (URL, status, bytes) — not file contents.
Connections use each provider's official OAuth flow. You can revoke SaveToDrive access anytime from the provider's security settings.
Files land in accounts you own, under that provider's terms. Disconnect a drive and we stop using its tokens.
Heavy transfer work runs in a dedicated worker process, separate from the HTTP API, so request serving and data movement do not compete.