Privacy Policy — DriveDeck for Google Drive

Last updated: June 29, 2026

This privacy policy explains how the DriveDeck Chrome extension ("the extension") handles your information. By installing and using the extension, you agree to the practices described below.

Summary

The extension reads the metadata of your Google Drive files (such as their names, file IDs, types, and last-modified dates) solely to display a searchable list in your browser sidebar. When you use the Create New feature, it creates a blank file in your Drive on your behalf. It does not read the contents of your files, and it does not collect, store, sell, or transmit any of your data to the developer or any third party.

Information the extension accesses

To provide its functionality, the extension requests the following Google account access via Google OAuth 2.0:

• drive.metadata.readonly — read-only access to file metadata in your Google Drive. The extension uses this only to query for your files (Docs, Sheets, Slides, Word, Excel, PowerPoint, and PDFs) and retrieve each file's name, ID, type, last-modified time, and owner name for display in the list.
• drive.file — permission to create files in your Google Drive. The extension uses this only when you explicitly click "New Google Sheet", "New Google Doc", or "New Google Slides" in the sidebar. It creates a single blank file of the requested type and opens it in a new tab. No other files are accessed, read, or modified via this scope.

The extension never requests access to the contents of your files, and it cannot modify or delete any of your files.

How the information is used

• File metadata is fetched from the Google Drive API and rendered in the sidebar on your device.
• Your search queries are sent to the Google Drive API to filter results server-side.
• When you click a file, the extension opens it in a new browser tab using the file's standard Google Drive link.
• When you use the Create New feature, the extension sends a single request to the Google Drive API to create a blank file of the chosen type, then opens it in a new tab. No content is written; the file starts empty.

All of this processing happens locally in your browser. The extension has no backend server of its own.

Data storage and retention

• The extension does not maintain a database or send your data anywhere outside of Google's own APIs.
• OAuth access tokens are managed by Chrome's built-in chrome.identity service and are cached by the browser, not by the extension. Tokens are cleared when you sign out or when they expire.
• To power the "Recent" shortcuts, the extension saves a short list of the files you have most recently opened — limited to each file's name, ID, type, and link — in your browser's local extension storage (chrome.storage.local). This data stays on your device, is never transmitted anywhere, and is overwritten as you open newer files. You can clear it at any time by removing the extension or clearing its data in Chrome.
• To power the Favorites feature, the extension saves a list of files you have starred — limited to each file's name, ID, type, and link — in your browser's local extension storage (chrome.storage.local). This data stays on your device, is never transmitted anywhere, and is updated immediately when you star or unstar a file. You can clear it by removing the extension or clearing its storage data in Chrome.
• To let you switch between accounts you have used, the extension saves a list of those accounts — limited to each account's email address, display name, and profile photo URL — and the email of the most recently used account, in the same local extension storage. This is used only to populate the account switcher and to reload your last account when you reopen the sidebar. It stays on your device and is never transmitted anywhere. Signing out removes the active-account record, and removing the extension clears all of it.
• No file contents are ever read or stored by the extension.

Data security

The extension is designed to protect your data — including data obtained through sensitive Google account scopes — using the following mechanisms:

• Encryption in transit. All communication with Google's APIs takes place over HTTPS/TLS. Your file metadata and OAuth requests are never sent over unencrypted connections.
• No developer backend or central data store. The extension has no server of its own. Your Google Drive data and metadata are never transmitted to, collected by, or stored on any developer-controlled infrastructure, so there is no central database that could be breached, sold, or exposed.
• Secure, local-only storage. The limited data the extension caches (recently opened files, starred favorites, and the list of accounts you have used) is kept in the browser's sandboxed chrome.storage.local, which is isolated to this extension and protected by Chrome's and your operating system's security model. It never leaves your device.
• Secure token handling. OAuth access tokens are managed by Chrome's built-in chrome.identity service and are not persisted by the extension. They are cleared when you sign out or when they expire.
• Data minimization. The extension requests only the file metadata required to display your list. It never accesses file contents, and it does not retain sensitive-scope data beyond the in-memory session and the minimal on-device caches described above.
• User control and deletion. You can revoke the extension's access to your Google account at any time from your Google Account permissions page, and you can remove all locally stored data by clearing the extension's storage in Chrome or uninstalling the extension.

Data sharing

The extension does not share your data with anyone. The only network requests it makes are directly to Google's APIs (https://www.googleapis.com) to retrieve your file list and, when you request it, to create a new blank file — all authenticated with your own Google account.

Google API Services User Data Policy

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

Permissions

The extension requests the following Chrome permissions:

• identity — to authenticate you with Google via OAuth 2.0.
• sidePanel — to display the extension's interface in the browser side panel.
• storage — to save your recently opened files, starred favorites, and the list of accounts you have used locally, so the "Recent" shortcuts, Favorites, and account switcher persist between sessions.
• host_permissions for https://www.googleapis.com/* — to call the Google Drive API.

Changes to this policy

If this policy changes, the updated version will be published at this page and the "Last updated" date above will be revised.

Contact

If you have questions about this privacy policy, please contact the developer at: knkgen@knk24.com