Upload decisions before sharing decisions
Google Photos Backup Folders: A Privacy Check
On Android, review Google Photos → profile → Photos settings → Backup → Back up device folders, including Back up all device folders. Disable unwanted folder backups before creating sensitive exports, and check the actual item’s backup status. Turning backup off does not remove copies already uploaded or control another backup service.
By Qingxin Studio, the developer of HushPic · Updated
Check the account and folder policy first
Confirm the Google account shown in Photos before inspecting Backup and its device-folder settings. Google documents individual folder switches and an all-folders control; enabling the latter also backs up newly created device folders. Available folders can differ by device and storage access.
Review where camera images, screenshots, downloads, and editor exports actually appear. Do not assume a folder named private is excluded. If the intended folder is not controllable or you cannot verify the behavior, reconsider automatic backup before placing sensitive material there. This checklist changes no account settings for you.
Distinguish the original from the prepared copy
A locally processed sharing copy does not replace its original. If either sits in a backed-up location, its upload decision remains separate from the masks or metadata changes applied to the other file. Review both items instead of assuming cleanup prevents cloud storage.
HushPic keeps photo processing on-device, but cannot configure Google Photos or other apps’ backup policies. Saving a result into a library does not promise that the library stays local. Check your destination before saving; keep independent backup choices consistent with the information you intend to store.
Inspect an item’s status, not just its thumbnail
Google documents opening a photo, choosing More → About, and looking under Details for its backup status. Check a neutral sample in the relevant folder if you need to understand your setup; do not deliberately upload a confidential picture as a test.
Record what the item’s actual status says. An image being visible in the Photos app does not, on its own, tell you whether it exists only locally or was backed up. Do not infer cloud absence from a temporary progress state or a small icon without its context.
Keep upload, sharing, and deletion separate
Disabling future backup is not an instruction to delete cloud or device files. Existing uploads, album sharing, and recipients’ downloads need separate decisions. This guide deliberately avoids delete or free-up-space operations, which can affect copies you meant to keep.
The browser checker reads supported local metadata categories only; it cannot query backup status, inspect account permissions, review pixels, clean an image, or generate a verified copy. If you prepare a supported photo in HushPic, review suggestions, regenerate after changes, and retain the original. Purchases and diagnostics may use the network without receiving photo contents; that disclosure is separate from an external gallery’s backup.
Sources
This guide is published by Qingxin Studio, the developer of HushPic. Product claims describe our supported workflow, not independent certification. Our review checklists are practical first-party guidance; linked platform sources support only the mechanisms they describe. Automatic checks may miss details. Read our content and corrections policy.