Privacy and local data
PrintLilt’s photo workflow runs in your browser. Knowing which data is temporary, which is saved locally, and which you download helps you control each copy.
Your photos
Selecting a file lets the browser read that file for the current task. Photo processing and export do not send its bytes or filename to a remote processing service. PrintLilt has no photo account or cloud image library.
The working preview uses temporary browser memory. A new local project does not include the original by default. If you explicitly choose to include it, the original is stored in this browser’s local image database so the project can reopen it without another file selection.
Your data
Saved project parameters and source-file descriptions use local browser storage. They can include your project name, the original filename, type, byte size, dimensions, orientation, and layout choices. Treat a downloaded project JSON as a file that can reveal those details to anyone you share it with.
Project JSON does not embed image bytes, a thumbnail, or a reusable blob URL. Raster and PDF downloads do contain the exported image when you choose a photo output. Your browser and operating system decide where those downloaded files are stored.
Site search runs against the published content index in the browser. It does not search your private photos or local projects. A query placed in the address bar can remain in browser history or a URL you choose to share.
Privacy details
The current site does not run advertising or analytics scripts, and it does not use a contact-upload form. Loading the website still requires ordinary web requests; network and hosting systems can handle request information independently of the local photo workflow. See the Privacy page for the full explanation.
External source links open other organisations’ websites. Their policies and requests are separate from PrintLilt. The demonstration photograph is served as a local site asset rather than fetched from a photo platform when you edit your own image.
Remove local data
Use the project controls to delete a saved project or remove an included original. To remove all browser-held site data, use the browser’s site-data controls. That can also remove local preferences and prevent stored projects from reopening.
Downloads are separate copies and must be deleted from their actual folders. Clearing browser storage does not remove them. Keep any original or project file you want to retain before clearing local data, and do not rely on browser storage as your only backup.