BROWSER EXTENSION / PRIVACY
Your photos. Your device.
Updated 27 October 2026
This page explains the PichaLite browser extension. It does not describe the separate Android app or the main website’s analytics. The extension contains no advertising, analytics or session-recording code.
What the extension accesses
PichaLite accesses photos you select in Google Photos, their individual page links and file bytes, and embedded metadata when present. Metadata can include capture dates, orientation and GPS location. It reads the active account’s email address from Google Photos’ account control to keep batches separate and help prevent operations in the wrong account.
While an original download is explicitly in progress, the extension observes the attachment response in its dedicated Google Photos work tab to obtain the original download address. It does not request access to your general browsing history or monitor unrelated sites.
What stays on your computer
Compression runs locally in your browser. Original and compressed image bytes, photo identities, account identifiers, file sizes, hashes, progress and recovery records are retained in the extension’s local browser storage. These records are used to verify replacements and resume interrupted batches. They are not sent to a PichaLite server.
Use Forget locally on a batch item to remove its local record and stored image copies. A selection that has not yet been added to a batch can be removed by selecting it again in the toolbar. Browser storage controls can also clear extension data. Temporary work data has no automatic expiry in this preview.
Google Photos’ normal download action can also save a file in your browser’s Downloads folder. Forget locally and removing the extension do not delete those downloaded files; manage them separately.
What is sent to Google
The extension downloads selected originals from Google and uploads compressed replacements directly to your Google Photos account. Embedded metadata retained in the compressed file, including GPS location when present, is sent with that replacement. Verification downloads the replacement again and compares its bytes with the locally compressed file.
The extension uses your existing Google Photos sign-in. It does not ask for or store your Google password. Google handles the photos and authenticated requests under its own policies.
Cleanup requires your approval
After replacement verification, you can approve moving the listed originals to Google Photos trash or bin. Both original and replacement are checked again before each cleanup action. PichaLite does not automatically empty trash or permanently delete items. Google Photos deletion can affect synced devices; Google’s recovery rules apply.
Replacements are new Google Photos items. Google-only dates, albums, favourites, comments, edits and shared links are not automatically transferred. File-size reduction is separate from Google storage quota reclaimed.
Why browser permissions are needed
- Google Photos and media-host access: selection, original downloads, replacement uploads, verification and approved cleanup.
- Local storage: selected items, image copies, progress and recovery records. Chromium and Firefox builds request storage capacity for working batches; physical disk space still limits storage.
- Page scripting: the selection controls and upload-file input bridge in Google Photos.
- Side panel or sidebar: the PichaLite workspace alongside Google Photos where the browser supports it.
- Download request observation: identify the original attachment response during an explicitly requested download.
The extension does not contain remote executable code, telemetry, advertising or profiling features. Its local image processing does not involve an AI service.
Questions or problems
Use the PichaLite issue tracker for support. Do not attach private photos, account credentials or sensitive metadata to public issues.