Drive GO Terms

Legal

Privacy Policy

Last updated: March 31, 2026

Back to home Contact support

Overview

Drive GO is a Chrome extension that helps users work with Google Drive from the Chrome side panel. The extension is designed to use the user's Google account and Google Drive data only when needed for the features the user chooses to use. Data that is not needed for a Google action stays stored locally in the user's browser on their device. Drive GO is designed so that the developer does not operate a backend service that receives or stores the user's Google Drive files, Google Drive metadata, or local extension state for the core product workflow.

How we protect sensitive data

  • Data sent between the extension and Google services is transmitted over HTTPS and TLS-protected connections.
  • Authentication uses Google OAuth and browser identity APIs so that access tokens are requested only when needed for the relevant feature.
  • Drive GO is designed to keep settings, transfer state, and other local extension data on the user's device in browser-provided storage instead of sending that data to developer-operated servers.
  • Access to Google Drive data is limited to the extension features the user chooses to use, such as browsing files, uploads, activity, sharing, or file management actions initiated by the user.
  • Drive GO does not use user Google Drive data for advertising, profiling, or sale to third parties.
  • No third-party advertising trackers are included in the extension, and no outside analytics services are used for the core extension workflow.
  • When local data is no longer needed, the user can remove it by clearing extension storage, removing queued items, revoking Google access, or uninstalling the extension.

Information we process

  • Google sign-in tokens and Google permission information needed to sign the user in and connect to Google services.
  • Basic Google account information, such as the current account email, when needed to identify the signed-in user.
  • Google Drive metadata and content that the user explicitly accesses, uploads, edits, shares, restores, trashes, or manages through the extension.
  • Activity data from Google Drive when the user turns on activity features.
  • App settings stored locally, such as theme, language, chosen save folders, activity preferences, transfer preferences, and read state.
  • Transfer data stored locally, including upload status, progress, history, temporary upload data, and data needed to continue an upload.
  • Content explicitly chosen by the user through context menu actions, such as a screenshot of the current tab, selected text, or an image chosen for upload to Google Drive.

How we use information

  • To sign the user in and provide access to the Google Drive features they request.
  • To show files, search results, transfer progress, recent activity, sharing controls, and other Google Drive actions requested by the user.
  • To store app settings and local state so the extension works as expected across sessions.
  • To upload files and user-selected content to the user's Google Drive when the user initiates those actions.
  • To show browser notifications and optional sounds for activity events when enabled by the user.
  • To keep the extension reliable, resume eligible transfers, and handle errors locally on the user's device.

Chrome Web Store data handling summary

  • Drive GO does not send user data to the developer's own servers for analytics, advertising, profiling, or resale.
  • Data leaves the browser only when the user signs in with Google or performs a Google Drive action that requires communication with Google services.
  • Settings, app state, and transfer data stay on the user's device unless the user starts an action that sends data to Google.
  • The extension is not designed to transfer Google Drive files or extension state to developer-operated servers for storage, analytics, or profiling.

Where data is stored

  • App settings and interface state are stored locally in the browser.
  • Upload queue records, temporary upload data, upload progress, and transfer history may be stored locally until they are completed, removed, or cleared.
  • This locally stored data remains on the user's device and is not copied to outside services that are not needed for the extension to work.
  • Data sent outside the browser is sent to Google services only when required to authenticate the user or perform the Google Drive action requested by the user.
  • The developer does not provide a general cloud storage backend for extension data. Core settings and queue state are intended to stay in browser-managed local storage on the user's device.

Access controls and least privilege

  • Drive GO requests Google permissions and browser permissions only for features the user chooses to use.
  • Sensitive actions such as uploads, sharing changes, trash operations, and activity access are performed only after the user initiates the feature or enables the related option.
  • Google account access can be revoked by the user at any time from their Google account permissions settings.

Data sharing

Drive GO uses official Google APIs to perform actions requested by the user. The extension does not sell personal data and does not share user data with advertising networks, analytics providers, or other outside parties that are not needed for the service. Outside of Google services required for the extension to work, user data stays local in the user's browser and on their device. Data is sent to Google only when needed for Google sign-in, Google Drive access, uploads, activity features, and other user-requested Drive actions, or when required by law.

No third-party trackers

Drive GO does not use advertising trackers or outside analytics tools inside the extension. The extension is not used to build advertising profiles about users.

Data retention

Settings and local app state may remain stored until the user clears the extension data, removes saved jobs, or uninstalls the extension. Temporary upload data may remain locally until a transfer completes, fails, is removed, or the browser storage is cleared. In general, app data that is not part of Google services stays only in the user's local browser storage.

User controls and deletion

  • The user can revoke Google OAuth access from their Google account security settings.
  • The user can delete local extension data by clearing extension storage or uninstalling the extension.
  • The user can remove transfer records or other locally stored state from inside the extension where those controls are available.

User choices

  • The user can remove Google access in their Google account permissions settings.
  • The user can remove the extension from Chrome at any time.
  • The user can contact support with privacy questions.

Permissions and feature scope

Drive GO asks for browser and Google permissions needed for features such as Google sign-in, Google Drive access, the side panel, transfer storage, context menu actions, browser notifications, and user-initiated capture or upload actions. Some permissions are only used when the related feature is turned on or started by the user.

Contact

For privacy-related questions, contact app.drivego@gmail.com.