Privacy policy
Upload to Google Photos (Chrome extension) · last updated 19 September 2026
Summary
The extension has no server, no analytics and no accounts of its own. The only data it handles is the image you explicitly choose to upload, and it sends that image to exactly one place: your own Google Photos library.
What data is processed
- The image you right-click. When you choose "Upload to Google Photos", the extension downloads that image's bytes and sends them to Google Photos. The bytes are held in memory only for the duration of the upload.
- A Google OAuth access token. Obtained through Chrome's built-in identity system for the scope
https://www.googleapis.com/auth/photoslibrary.appendonly. Chrome stores and refreshes this token; the extension never writes it anywhere. - Your settings. Whether albums are enabled and the album name, saved in Chrome's synced extension storage. The resolved album ID is cached in local extension storage.
What the extension can do in Google Photos
The appendonly scope allows the extension to add new
photos and to create albums. It cannot read, list, modify, share or
delete anything already in your library.
What is never collected
- No browsing history, page content, or list of sites you visit.
- No usage analytics, crash reports or telemetry.
- No personal information. The extension does not know your name or email address.
Permissions
- Read and change data on a site is requested per image host, only when you first upload an image from that host, and only so the extension can download the image bytes. You can decline; the extension then tries to read the image through the page instead.
- Active tab / scripting is used solely to show the upload progress toast on the page you right-clicked.
- Notifications are used only when the toast cannot be shown (for example on Chrome's internal pages).
Third parties
The only third party that receives any data is Google, through the Google Photos Library API, and only the image you chose to upload. Google's handling of that data is governed by the Google Privacy Policy.
Revoking access
Remove the extension from chrome://extensions, and revoke
its access at
myaccount.google.com/permissions.
Photos already uploaded stay in your library until you delete them there.
Contact
Questions: open an issue at github.com/craigfoo/google-photos-chrome-extension/issues.