Privacy

DrivePack Privacy Policy

DrivePack is a desktop app by Good Tools in Saskatchewan, Canada. It lets you choose existing Google Drive folders and save their contents in a ZIP archive on your computer, preserving folder names and structure.

Effective October 21, 2026

Google user data we access

With your consent, DrivePack requests the Google Drive read-only permission (https://www.googleapis.com/auth/drive.readonly). Google describes this permission as viewing and downloading all your Drive files. DrivePack uses it to list folders in My Drive, Shared with me, and accessible Shared Drives; read file and folder IDs, names, types, sizes, parent/child structure, modification times, shortcut targets, download capabilities, and owner display names or email addresses shown with shared folders; and download the contents of files inside folders you select. Google Docs, Sheets, Slides, Drawings, and supported Apps Script files can be exported to standard formats for the archive.

DrivePack also receives OAuth access and refresh tokens from Google to maintain the connection. It does not receive your Google password. It does not request Gmail, Google Contacts, Calendar, or permission to edit or delete your Drive files.

How we use that data and why this permission is needed

Metadata powers the folder browser, selection, size estimates, progress, and preservation of directory structure. File content is downloaded only for the archive job you start and written to the destination you choose. Read-only Drive access supports recursive backup of existing folder trees, including descendants and shared folders that were not individually created by or opened with DrivePack. Metadata-only access cannot download file contents. Per-file access would restrict the existing folder-backup workflow to individually authorized files; it does not provide the broad existing-folder access this workflow uses. DrivePack does not request full read/write Drive access.

Google data is not used for advertising, profiling, selling data, credit decisions, or training generalized AI or machine-learning models. DrivePack does not automatically upload your archives or operate a background cloud backup service.

Sharing, transfer, and disclosure

DrivePack communicates directly from your computer with Google OAuth and Google Drive APIs. Good Tools does not receive or store your Drive file contents, folder listings, or OAuth tokens on its servers, and does not sell, rent, or share them with advertisers, analytics services, AI providers, or data brokers. File data is not sent through a Good Tools proxy. Downloads, exports, and authentication are handled by Google under its own terms and privacy policy.

You control any later sharing of the ZIP or files. Saving to a folder managed by iCloud, OneDrive, Dropbox, another sync provider, or a shared/network disk may cause that provider or other authorized users to receive the saved files under your own settings. If you voluntarily email support, we receive the information and attachments you include; please omit tokens and private file contents. Software update checks are separate from Drive processing and do not include your Google Drive data.

Data protection

Connections to Google use HTTPS. OAuth sign-in opens Google's authorization page in your browser and returns to a loopback listener on your own computer with a randomly generated state value. Tokens are saved in the app's local user-data directory with owner-only file permissions requested. DrivePack uses Electron's operating-system-backed safeStorage encryption when available. Existing builds can fall back to local token storage without encryption if that service is unavailable. Protect your operating-system account and enable full-disk encryption; do not use a shared or untrusted account for sensitive Drive data.

Downloaded ZIPs are ordinary local archives and are not password-encrypted by DrivePack. Your device, destination folder permissions, disk encryption, and any sync settings govern protection of those files. No system can guarantee absolute security.

Retention and deletion

Folder listings and job metadata are held locally in memory while browsing or running a job. Downloaded files and any temporary job files are stored on your computer while the archive is built. DrivePack attempts to remove temporary downloads after use and incomplete output when a job is cancelled or fails; an unexpected crash may leave local files to remove manually. Completed ZIPs remain at your chosen destination until you delete them. There is no Good Tools server copy of your Drive data to retain or delete.

OAuth tokens remain in local app storage until you disconnect or remove the app's data. Disconnect attempts to revoke the Google token and removes the local token file; if revocation fails or you no longer have the app, revoke DrivePack directly in Google Account connections. Removing the app alone may leave its user-data folder, so remove that folder as well when clearing local app data. On macOS, existing DrivePack builds use ~/Library/Application Support/drive-bundle. Deleting local archives or tokens does not delete the original files in Google Drive. Operating-system backups and cloud-synced copies must be managed separately.

Google API Limited Use

DrivePack's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Contact and changes

For questions or privacy requests, contact hello@goodtools.ca. Good Tools cannot delete files held only on your device, but can help you locate local app data and revoke access. We will publish policy changes on this page and update the effective date.