Privacy Policy

GDriveSync uses Google account access only to read supported Google Drive files that you explicitly connect through the VS Code extension or CLI. GDriveSync can store multiple connected Google accounts locally, but it remains one-way and read-only with respect to Google Drive content. Optional image enrichment can run locally on your device, or it can call a user-configured OpenAI or Anthropic API directly from the user's machine.

What data is accessed

• Google account authorization tokens for the connected Google account or accounts
• Google Drive metadata for the supported Google files the user links
• Markdown, presentation, or spreadsheet export data, or downloaded file contents for the linked Google files

Where data is stored

• OAuth tokens are stored locally in VS Code secret storage or the local CLI auth store
• Linked file metadata, including bound-account metadata, is stored locally in a workspace `.gdrivesync.json` file
• Optional image-enrichment cache files are stored on the local machine only
• No server-side database is used

What is not collected

• No analytics or telemetry are included
• No linked Google file contents are stored on the companion website
• No image enrichment data is sent to GDriveSync-operated servers
• Cloud image enrichment only uses user-configured OpenAI or Anthropic credentials and is disabled by default
• No linked documents are shared with third parties by the extension

Contact

Questions about GDriveSync or this policy can be sent to the maintainer of the release.