1. What DriveDock Is
DriveDock is an open-source macOS app for uploading files and folders to Google Drive. It is released under the MIT License. This policy explains what the app stores locally, what it sends to Google, and what the developer does not receive.
2. Data the Developer Does Not Collect
DriveDock has no developer-operated analytics or data collection service. The app does not send the developer:
- Your name, email address, or Google profile information
- The names, contents, or metadata of your files
- Usage analytics, interaction logs, or device identifiers
- Crash reports or diagnostic telemetry
- Your Drive folders, destinations, or upload history
3. Google Sign-In and Permissions
DriveDock opens Google's OAuth 2.0 sign-in flow. Your Google password is entered on Google's page and is never visible to DriveDock.
The app requests https://www.googleapis.com/auth/drive.file to create and upload files. It also requests https://www.googleapis.com/auth/drive.readonly to browse existing files, folders, and Shared Drives when you choose a destination. The read-only permission cannot modify or delete existing Drive items.
Access and refresh tokens are stored in macOS Keychain. They are not written to a regular settings file, sent to the developer, or stored by this website.
4. File Transfers
When you upload an item, DriveDock reads it from your Mac and sends it to Google Drive's API. The website is not involved in the transfer, and the developer does not receive a copy.
DriveDock keeps local upload records so you can review file names, sizes, destinations, progress, speed, and status. Those records remain in the app's container on your Mac.
5. Local Storage
DriveDock stores only the local data needed to operate:
- OAuth credentials in macOS Keychain
- App settings in the app's sandboxed preferences
- Upload history and queue state inside the app container
To remove this local data, delete DriveDock's app data and its Keychain entries from your Mac.
6. Network Services
The app connects to Google's authentication and Drive API services for sign-in, token refresh, Drive browsing, folder creation, and uploads. DriveDock contains no advertising SDK, analytics service, or third-party crash reporter.
7. Google's Terms
Google's services are governed by Google's Privacy Policy and the Google APIs Terms of Service. After an upload reaches Google Drive, Google's policies apply to that stored file.
8. Source Code and Security
The DriveDock source code, release history, and security policy are public. Report sensitive security issues through the repository's private Security reporting flow. Use GitHub Issues for non-sensitive bugs or questions.
9. Policy Changes
If DriveDock's data handling changes, this page will be updated with a new date and the relevant release notes will explain the change.