In the Uhale app, Delete and Withdraw do not remove the same data. Delete in the sending History removes the local history record from the phone but does not delete the delivered photo from the frame. Withdraw removes the history record and requests deletion of the delivered photo from the frame, provided the history record still exists and the frame is online over its 2.4GHz Wi-Fi connection.
The distinction matters because one photo can exist in several places during the sharing workflow: the original phone library, the app’s local History, the transit path, and the receiving frame. Choosing the wrong action can clear a record without removing the displayed photo, or remove a frame copy when the intention was only to tidy the app.
The Four Locations Behind One Sent Photo
A deletion action is meaningful only when the specific location is identified. Uhale photo sharing involves separate data locations with separate controls:
-
The original on the phone: The photo selected from the sender’s local camera roll. Uhale History controls do not delete that source image from the phone’s photo library.
-
The app History record: Displays information about a sending task. It can be deleted or cleared locally without changing the frame copy.
-
The transfer copy: Follows one of two routes. On the same local area network subnet, the phone sends the photo directly to the frame through an encrypted local transfer. On different networks, a stateless cloud relay server forwards the photo, deletes the temporary RAM copy immediately after delivery, and does not retain it as a permanent backup.
-
The frame copy: The delivered media stored and managed on the physical digital photo frame’s internal memory. It can be removed through the frame’s native Gallery or through a successful app-side Withdraw action when documented conditions are met.
Details regarding account setup and media workflows are available in the bound account management and privacy guidelines.
What Delete Does in Uhale History
Delete removes local History data from the app. It does not remove the photo already delivered to the frame.
This action is appropriate when the sender wants to clean up the phone’s sending record while leaving the frame display unchanged. After Delete, the recipient can continue to see and manage the delivered photo on the frame in the native Gallery.
Deleting the record also affects future options that depend on that record. Official guidance states that Withdraw works only while the History entry is retained and the frame remains online. Removing the local record first can therefore eliminate the app-side path used to withdraw that item later.
Before tapping Delete, ask one question: Should the photo remain on the frame? If the answer is yes, deleting the local history record matches that goal. If the answer is no, review the Withdraw conditions first.
What Clear Does in Uhale History
Clear removes History information from the app without deleting a sent photo from the frame. It is a record-management action, not a remote media-deletion action.
The practical difference between deleting one record and clearing a larger set is the volume of local History being removed. Neither action should be used as proof that delivered frame media has been erased.
Clearing History can be useful on a shared or older phone, but it should be deliberate. Once the record is gone, the sender may no longer be able to use that entry for a later Withdraw request. The frame holder would then need to manage the photo directly on the receiving device via the native Gallery.
What Withdraw Removes
Withdraw removes the local History record and deletes the delivered photo from the frame when the required conditions are satisfied. The frame must be online, and the relevant sending History record must still exist in the app.
This action is designed for a sender who wants to recall a specific delivered item (such as a photo or a short video up to 2 minutes) rather than merely remove the task record from the phone. A successful result affects both the sender-side History entry and the receiving frame copy.
Withdraw should not be described as a universal deletion of every possible copy. It does not mean that the original photo disappears from the sender’s phone library. It also cannot control copies that someone may have exported to external MicroSD media (formatted to FAT32 up to 32GB) or otherwise saved outside the documented Uhale workflow.
If the frame is offline, the requested frame deletion cannot complete at that moment. The sender should not assume that the photo has been removed until the frame is online and the action succeeds.
Delete From Gallery Is a Frame-Side Action
Deleting a photo in the frame’s native Gallery removes the selected device-side media. It is different from deleting the app’s History record.
On current frame software, the native Gallery is the designated interface for viewing and managing photos and short video clips stored on the frame. A person with physical access to the frame can select unwanted media and use the available delete action.
Frame-side deletion does not serve as a command to erase the sender’s original phone photo. It also does not clear the sender’s local app History record. The frame and app keep separate records and controls because they serve different users and locations.
This is why the same word, Delete, can produce different results depending on where it appears:
-
Delete in App History: Removes the local sending record from the mobile phone.
-
Delete in Frame Gallery: Removes the selected media directly from internal frame storage.
-
Withdraw in App History: Removes the History record and requests deletion from the online frame.
Hide Is Not Delete
Hiding a photo removes it from the normal slideshow presentation without erasing the file from the frame. It is useful when the image should remain available on the device but should not appear in the active display rotation.
Hide should not be used when the compliance goal is to remove the frame copy completely. A hidden photo remains locally stored and may remain visible through the native Gallery interface to someone operating the frame touchscreen panel.
The choice is based on intent:
-
Use Hide to keep the file stored but stop normal slideshow display.
-
Use Gallery Delete to remove the local frame copy permanently from internal flash memory.
-
Use History Delete or Clear to remove app-side records while leaving the frame copy untouched.
-
Use Withdraw to remove the app record and the delivered frame copy simultaneously when documented conditions allow it.
Complete rules regarding local media management are detailed in the guide on local photo storage management and Gallery usage.
Account Removal Is Another Separate Choice
Removing a bound app account from the frame revokes that account’s ability to send new content. It is an access-control action rather than another name for Withdraw.
Unbinding an account is performed on the touchscreen panel under Settings > Account Management (with the explicit option to delete associated shared photos uploaded by that account). This explicitly allows the display owner to revoke future transmission rights and purge that user’s historical media uploads from the frame’s internal memory and native Gallery.
Uhale operates on a flat account model without master/sub-account structures or Admin, Member, and Viewer roles. Bound accounts are reviewed on the frame under Settings > Account Management. Removing one account does not delete the Uhale app from that person’s phone, erase the original phone camera roll, or close the person’s broader mobile profile.
Choosing the Correct Uhale Photo Action
Three common scenarios show why the final media location must be verified:
-
Tidying Mobile History: A sender wants to clean up an old phone without changing a relative’s slideshow. Deleting or clearing the local History record is appropriate because the frame photo should remain. The sender should understand that the app may no longer provide a later Withdraw option for that item.
-
Recalling a Sent Photo: A private image was sent to the wrong frame. The sender should keep the History entry, confirm that the frame is online via 2.4GHz Wi-Fi, and select Withdraw. After the action completes, the frame holder can check the native Gallery to verify that the item is gone. The sender must separately decide whether the original photo should remain on their phone.
-
Clearing Local Storage: The frame holder wants to free internal memory while the sender wants to keep an app record. Deleting from the native Gallery removes the device copy without altering the sender’s mobile History. Each person retains or removes the record they control.
These scenarios explain why screenshots of a clean app or clean Gallery provide only location-specific evidence. Data protection verification should cover every location relevant to the user’s objective.
Use the desired final state to choose the action rather than relying solely on the button label:
-
If the photo should stay on the frame but the phone’s task record is no longer needed, use Delete or Clear in History.
-
If the sender wants the delivered frame photo removed and still holds the History entry, use Withdraw while the frame is online.
-
If the frame holder wants to remove media locally, use Gallery Delete.
-
If the image should stop appearing in slideshows but remain stored, use Hide.
For data-sensitive photos, verify the result at the location that matters. A clean app History does not prove that the frame is clear, and a clean frame Gallery does not prove that the phone’s original file was deleted. Overall platform standards and safety certifications can be reviewed under global platform compliance and safety certifications.
Product specifications are subject to change without notice. For the latest software details, please consult official platform documentation.