Privacy Policy
Last Updated: June 9, 2026
1. Introduction
gdrive-dup ("we", "our", or "us") is committed to protecting your privacy. This Privacy Policy explains how our application accesses, uses, stores, and shares your Google user data.
2. Google User Data We Access
gdrive-dup requests access to your Google Drive to function. Specifically, we request the
https://www.googleapis.com/auth/drive scope.
- Metadata Access: We read the metadata (names, sizes, hashes, and creation dates) of your files to identify duplicates.
- File Deletion: With your explicit permission, we move duplicate files you select to your Google Drive Trash or delete them.
3. How We Use Google User Data
Your Google Drive data is used strictly for the purpose of identifying duplicate files and freeing up storage space on your behalf.
4. Data Storage and Sharing (Local Only)
gdrive-dup is a strictly local application. All processing is done on your own device. We do not transmit, upload, or store your Google user data on any external servers. Your data is never shared with third parties.
5. Data Retention and Deletion
Because gdrive-dup processes all data locally on your device, our data retention practices are as follows:
- File Metadata (names, sizes, hashes, dates): Temporarily held in your device's memory only while a scan is actively running. It is automatically cleared from memory when the scan completes or the application is closed. We never retain file metadata after the scan session ends.
- OAuth Authentication Token: Stored locally on your device in a
token.jsonfile within the application directory. This token is retained until you manually delete it or revoke access. We do not have access to your token — it remains solely on your device. - Server-Side Data: We do not transmit, upload, or store any of your Google user data on any external servers. There is no cloud storage, no analytics, and no third-party data processing.
How to Delete Your Google User Data
You have full control over your data at all times. To delete your data managed by gdrive-dup, you can:
- Delete the local token: Locate and delete the
token.jsonfile from the gdrive-dup application directory on your device. This will remove your stored OAuth token and require you to re-authenticate the next time you use the application. - Revoke application access via Google: Go to your Google Account Security > Third-party apps with account access page. Find "gdrive-dup" and click "Remove Access". This immediately revokes the application's ability to access your Google Drive data.
- Uninstall the application: Deleting the application from your device will remove all locally stored data, including the OAuth token and any cached metadata.
Any of these actions will take effect immediately. Since we do not store your data on any servers, revocation, token deletion, or uninstallation ensures complete removal of your Google user data from gdrive-dup.
6. Security and Data Protection Mechanisms
We implement specific mechanisms to protect your sensitive data. In transit: All communication between gdrive-dup and Google Drive APIs is securely encrypted using HTTPS/TLS protocols. At rest: Your OAuth tokens are stored locally on your device, protected by your operating system's built-in file access controls. We strongly recommend keeping your device secure and utilizing full-disk encryption to further protect your locally stored data.
7. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. If we make material changes to how we access, use, store, or share your Google user data, we will notify you by prominently posting a notice on our website and within the application before the changes take effect. We encourage you to periodically review this page for the latest information on our privacy practices.
8. Contact Us
If you have any questions about this Privacy Policy, please contact us at jwtiyar@gmail.com.
gdrive-dup