Photos and editing
Photos you choose are opened and processed in your browser. This editor does not upload your photos or designs to our server. Image exports are created in your browser and downloaded to your device.
Your cookie and storage choice
Optional browser storage is off until you select Accept. Accepting enables local design recovery, the image cache, a session cookie that connects your project tabs, saved appearance, drag-step and alignment-snap preferences, and a record that you have already started or skipped the guided tour. Refusing leaves browser saving off. The light/dark switch still works for the current page. You can still create designs and download images or editable design files; your work stays in the open editor, and reloading starts a fresh canvas.
Use here or in the footer to change your choice. Refusing after accepting stops browser saves and removes saved browser designs, cached photos, your saved appearance, editing preferences, the remembered tour choice and the editor’s session cookie. The canvas already open in a tab remains available to download. It does not delete downloaded files.
A necessary cookie, lhtpics_storage_consent, remembers Accept or Refuse for 180 days. It contains only that choice. We do not use analytics or advertising cookies.
Keeping your designs
With your permission, the editor keeps separate recovery copies of your designs and recent changes in this browser for the browser session. Each project has its own address, with its ID after the #. This part of the address stays in the browser and is not sent to the server. Reloading that address, or opening it in another tab in the same browser session, restores that project, including its images. It is not uploaded to our server and does not update a design file you previously downloaded.
Recovery uses local browser storage for designs and an IndexedDB image cache for larger photos. The optional lhtpics_editor_session cookie lets your tabs access the same projects; it contains a random session identifier, with no photos or design contents. Project addresses are local recovery links, not public sharing links. They expire with the browser session, although browsers may preserve sessions when restoring tabs. If shared storage is blocked, recovery may only be available in the current tab. While storage is accepted, drafts and cached images inactive for more than seven days are cleared the next time the editor is used. You can remove browser copies sooner by refusing in Cookie settings or clearing this website’s data in your browser settings. If browser storage is blocked or full, the editor shows that recovery is unavailable.
Save design always lets you download a file containing the editable settings and your original images, whether you accept or refuse browser storage. Keep an updated file for use after the session ends. That file can contain personal information from the images you chose, including embedded image metadata. Keep it somewhere private and only share it intentionally. To remove downloaded files, delete them from your device.
Website requests
Your browser requests pages, fonts and LHT artwork from this website. The application does not use advertising scripts, tracking cookies or external font services. Hosting infrastructure may keep ordinary request and error logs, which can include IP addresses. Photos and design contents aren't included in those requests.
Usage counts
We keep aggregate daily counts of designs started, editable design files saved, editor images downloaded and images downloaded from the library. Counts are grouped by the public template and canvas format. When you save a design file or download an editor image, we also count enabled features and quantities, such as text layers, canvas sections, image use, borders, gradients, patterns and the LHT logo. These become separate daily feature totals; we do not retain individual design snapshots or the settings needed to recreate your design. No entered text, image data, filenames or image references are sent for analytics. This does not use cookies or browser storage and works independently of your optional storage choice. Analytics does not store visitor identifiers, IP addresses, project addresses, your design names, text or images. These counts show actions, not individual people.
External links
Links to other websites take you outside LHTpics. Those websites have their own privacy practices.
Donations
Clicking Donate with Xaman sends your chosen currency and amount to our server to create a payment request with Xaman. The QR code and live payment updates connect your browser to Xaman. You review and approve the payment in your wallet; we never receive your private keys. We check the payment with Xaman and the public XRP Ledger before showing it as successful.
We keep payment request details, amounts, currencies, timestamps and outcomes on our server. For confirmed payments, we also keep the public wallet address and transaction ID as a donation record. Short-lived, hashed network identifiers help limit abusive requests. Starting a donation sets a necessary, secure session cookie, __Host-lht_donation_session, containing a random access key. It contains no wallet or payment details and cannot be read by JavaScript. The private code after the # in the support address works only with that browser session; copying the address to another browser or incognito session does not restore the donation window. This cookie is separate from optional design storage.
Private access ends when the browser discards its session cookie. Browsers that restore previous sessions may preserve it after quitting. After payment, Close and forget immediately revokes access to that donation window across tabs, including restored tabs. This does not remove the payment record or invalidate public cards already shared.
A small notice may show the latest confirmed donation. It displays only the first four and last four characters of the wallet address, separated by an ellipsis, and how recently the donation was confirmed. It does not display the amount or link to the full wallet or transaction.
After a confirmed payment you can choose to share a public supporter card. The card does not show your wallet address or transaction ID. Its amount is hidden unless you select Include my donation amount. Anyone with a share link can view it; links already created keep their original amount setting, and social platforms may cache their previews. Transactions on the XRP Ledger are public independently of these cards. Xaman and X have their own privacy practices.
Password-protected templates
Opening a private template link uses required, secure session cookies to protect the password form and remember access to that template for up to 8 hours. These cookies cannot be read by JavaScript and are separate from optional design storage. Short-lived, hashed network identifiers limit password attempts. Once unlocked, your copy is edited in your browser and follows your existing save and download preferences.
Updated 4 October 2026.