Privacy

Last updated: 2026-05-09

zz-drop is a command-line program that runs entirely on your machine. The hosted services we operate are this website and the OAuth callback domain. This page describes what we do and don't collect across both.

What we don't collect

What stays on your device

What the cloud provider sees

For the four active providers in v1 — Nextcloud, Google Drive, OneDrive, Dropbox — file content is uploaded as-is. The provider sees the file the same way it would if you used their own client. zz-drop does not add an additional encryption layer on file content in v1; that is on the v1.1 roadmap.

OAuth

For Google Drive and OneDrive, zz-drop uses OAuth 2.0 device flow (RFC 8628): your browser is sent to the provider's authorization page, you approve there, and the CLI polls the provider directly for the resulting tokens. For Dropbox, zz-drop uses paste-code (Authorization Code + PKCE without redirect_uri): the provider shows you a code, you paste it into the CLI. None of these flows sends a redirect to a host we operate; we have no OAuth callback server. Tokens are written only to your local encrypted profile and are never seen by any zz-drop-operated server.

This website

The site is static HTML and CSS, served from a single OVH virtual machine in Gravelines, France. No JavaScript is required to read any page. No fonts, scripts, or images are loaded from third-party CDNs.

Contact

Questions, corrections, requests: privacy@zz-drop.net.