Hiding an item is not recalling a copy
Google Photos Locked Folder: What Stays Private?
Locked Folder restricts access to selected Google Photos items; it does not sanitize metadata or recall copies saved by recipients. Distinguish the protected item, edited copies, and its backup setting before relying on it. Do not move sensitive files merely to test how sharing behaves.
By Qingxin Studio, the developer of HushPic · Updated
Find the copies outside the protected item
Google documents that moving an item to Locked Folder does not move previously created or edited copies with it. Make a private inventory of the original, editor outputs, and attachments you already created. Similar thumbnails do not establish that all copies share one protection setting.
For example, moving a camera photo does not answer where yesterday’s cropped export is stored. Inspect that export in its own location. Avoid deleting either version during this check; deciding what to retain is different from establishing which copy a control affects.
Review backup separately from the lock
Open Google Photos → Collections → Locked and review available Locked Folder backup controls for the account you actually use. A lock is not proof that an item exists only on the device. Account eligibility and managed-device restrictions can affect availability.
Google warns that unbacked items can be lost through actions such as clearing app data or removing the app. Do not use reset, uninstall, or storage cleanup as a privacy test. Decide on retention and backup deliberately, rather than treating protection and recoverability as identical.
Understand the sharing boundary
Google says protected items are unavailable to third-party sharing apps while in Locked Folder. If sharing is necessary, first decide whether exposing a separate prepared image is appropriate. Moving an item out changes isolation; it does not remove private content.
A recipient’s previously saved copy is independent. Moving your version into Locked Folder cannot promise to retract it. Address an earlier disclosure through the actual recipient and delivery channel; changing a library location is not a recall procedure.
Prepare a deliberate sharing copy
Review the intended output at readable size and check hidden fields independently, leaving the original unchanged. Our browser checker reads supported local metadata categories only; it cannot inspect Locked Folder status, see pixels, clean files, or produce verified copies. Parsing failure supplies no reassuring result.
HushPic prepares separate supported copies on-device and checks written output within scope. Review suggestions because they can miss details, and regenerate after adjustments. It does not manage Google accounts or recall other copies. Purchases and diagnostics may connect without receiving photo contents.
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.