Privacy Policy

What data we access

To show you your recent files and detect changes from collaborators, the extension requests read-only access to two Google APIs on your behalf:

Both scopes are read-only. The extension cannot create, edit, move, or delete any files.

Where your data goes

Nowhere outside your device. GDrive CommanderZ has no backend server. The extension communicates directly between your browser and Google's APIs — the data never passes through any third-party infrastructure.

What is stored locally in your browser (chrome.storage.local):

• File names, types, and modification timestamps — to display the list
• The timestamp of when you last viewed each file — to calculate change indicators
• The time of the last API poll — to manage polling frequency

This data never leaves your device and is cleared when you sign out or uninstall the extension.

Authentication

Sign-in is handled entirely by Google OAuth 2.0 via the Chrome Identity API (chrome.identity.getAuthToken). The extension never sees your Google password. Your OAuth token is managed by Chrome itself and stored in Chrome's secure token cache — not by our code.

Third-party services

The extension contacts only Google's own APIs:

• www.googleapis.com — Google Drive API v3 and Drive Activity API
• docs.google.com — to detect which file is currently open

No analytics, crash reporting, advertising, or any other third-party services are used.

Data retention

Locally cached file data is automatically overwritten on every polling cycle (every 3 minutes). Signing out via the extension clears all stored data immediately. Uninstalling the extension removes all local storage.

Children's privacy

This extension is not directed at children under 13 and does not knowingly collect information from children.

Changes to this policy

If we make material changes, we will update the "Last updated" date above and, where appropriate, notify users via the Chrome Web Store listing.