Privacy Policy

1. Information we process

To provide Leo, we may process Google account identifiers, basic profile information, Google OAuth tokens, Google Drive file metadata, derived duplicate signatures, scan status, cleanup-plan exports, and action history such as Trash and restore requests.

• Metadata can include file names, IDs, MIME types, sizes, timestamps, folder paths, ownership, capabilities, dimensions, rotation, and Trash state.
• Derived signatures can include Google-provided checksums and our own SHA-256, pHash, TLSH, Google-native content, and Chromaprint signatures where supported.
• Eligible file bytes and Google-native exports may be downloaded transiently to calculate a signature. Leo stores the resulting signature, not a retained copy of the downloaded content.
• Leo does not persist camera make, camera model, location, or photo-capture timestamps merely to rank image results.

2. Why we process it

We process this information to authenticate you, scan the Drive content you authorize, identify exact or likely duplicate groups, explain review decisions, export cleanup plans, move files you select to Trash, restore them when requested, disconnect your account, prevent abuse, and maintain the service.

3. Google API data and permissions

Google data is used only to provide or improve the prominent user-facing features you request. Selected-file access can use https://www.googleapis.com/auth/drive.file. Full-Drive discovery uses https://www.googleapis.com/auth/drive.readonly. Trash and restore actions use https://www.googleapis.com/auth/drive after separate approval. Leo does not currently connect to Google Photos.

Leo's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

4. Storage and retention

OAuth tokens, indexed metadata, derived signatures, scan status, OAuth state, and cleanup history are retained only as long as reasonably needed to provide connected Drive features, maintain security, and resolve support issues. Hosted OAuth tokens are designed to be stored through Google Secret Manager, with service data held in the configured Google Cloud environment.

The Disconnect Drive action revokes Leo's Google grant and removes its stored OAuth token, indexed Drive metadata, derived signatures, OAuth state, and cleanup history. It does not delete files from Google Drive or erase billing and transaction records that must be retained for accounting, fraud prevention, disputes, or legal compliance.

5. Sharing and service providers

We do not sell Google user data, use it for advertising, or allow humans to read file content except with your affirmative agreement for support, when needed for security, when required by law, or when otherwise permitted by Google's API Services User Data Policy.

Google and Firebase support authentication and Drive access. Google Cloud hosts the intended service. Stripe handles checkout and subscription records when billing is enabled; Leo does not receive or store full card numbers.

6. Security and product limits

Connections to Google APIs use HTTPS. Service data is isolated by authenticated user ID, and destructive actions are checked against live Drive ownership and capability metadata. No system can guarantee perfect security or perfect duplicate detection. You should review important files before cleanup, particularly similarity results that are not proof of file identity.

7. Your choices and requests

You can decline optional permissions, disconnect Drive inside Leo, or revoke Leo from your Google Account. You may contact support@leodrivecleaner.com with access, deletion, correction, privacy, or support requests.

8. Changes

We may update this policy as Leo changes. Material updates will be reflected by revising the effective date. If Google user data will be used for a new purpose, we will provide the required notice and obtain consent before that use.