Source copies, results, diagnosis, and QA evidence persist on the computer running the local service.
Know exactly where restoration images and records can exist
OldRestore Pro uses local persistent storage, but generation is not fully offline. The privacy boundary distinguishes local files from external AI processing.


Before generation, the product discloses that images may be sent to the configured external service and waits for confirmation.
Comparison tasks require a preferred result while QA risk and output evidence stay visible.
Keep the source, result, and review boundary together


photo restoration privacy
Stored on the local machine
Persistent source copies, restored outputs, task history, diagnosis, and QA evidence are written to the configured local project directory.
Sent for external processing
After explicit confirmation, originals and necessary results can be transmitted to the configured provider for diagnosis, image editing, and QA.
Deletion has a defined scope
Deleting local files removes local pixel data. It does not automatically delete data that an external provider may retain under its settings, policies, or backups.
Frequently asked questions
Are images embedded inside task records?
No. Records keep file references and metadata rather than hidden Base64 image copies.
Does deleting a local image remove its preview?
Yes. The remaining record can still show text metadata, but it cannot reconstruct or display deleted pixels.
Does OldRestore Pro guarantee zero cloud retention?
No. The current architecture sends images to a configured external provider, whose retention and backup terms must be reviewed separately.
Apply the same review standard to your own old photo.
Upload the source, choose a restoration route, and inspect likeness, composition, and quality evidence before delivery.