Storage & Retention

1. Guest projects on your device#

Saved guest projects and their prepared images are held in IndexedDB in your current browser. Bookmarks, an unfinished text draft and preferences use browser storage. They are not a cloud backup, and another browser or device cannot recover them by signing in.

Guest records remain until you delete them or the browser removes the site’s data. Private browsing, storage pressure, changing browser profiles and clearing website data may remove them. Download important projects before clearing data. Unsaved selected photographs are held only for the active editing session.

2. Account projects and images#

For an authenticated account, saved projects, images and library data are stored on LIA’s server. The current limit is 25 projects. An uploaded reference is converted to a smaller JPEG, up to 2048 pixels on its longest side, with a smaller preview. The source file’s EXIF and similar metadata are not copied to the stored image.

The current project image limit is approximately one megabyte of JPEG data; the encoded request size is also limited. Resolution or compression may be reduced to fit. LIA therefore does not preserve an archival original or promise lossless photo storage.

Account materials remain in the active database while you keep them. Deleting a project removes its stored record; deleting the account removes linked projects, library data, acceptance records and active sessions. Account deletion has no built-in undo function.

3. Sign-in and security records#

A session can last at most 24 hours and ends after two hours without activity. One-time web-sign-in transactions have a five-minute validity period. Expired session and one-time records are cleared by the server’s periodic cleanup when the server is running.

The application avoids logging request URLs, authentication codes, cookies and signed Telegram proofs. It uses IP addresses for request limits. This does not describe or override logging by a future hosting provider, reverse proxy or Telegram.

4. Generated worlds and processing records#

When world creation is enabled, LIA keeps a private record of each accepted job. Its description and prepared reference are retained while needed to submit that job. After the provider submission is successfully recorded, the temporary job copy of that text and image is removed; any separately saved project remains until you delete it. A job whose submission cannot be confirmed may retain that input for reconciliation rather than being submitted again automatically.

Completed 3D splats, an available collision mesh and a thumbnail are copied into private LIA storage, subject to download and storage limits. Job records retain the title, settings, status, timestamps, provider identifiers, error category and available usage information. Results and records remain while you keep the generated world, subject to disclosed service and provider retention requirements. No indefinite-storage guarantee is made. Video and audio storage are not offered.

Deleting a generated world removes access in LIA immediately and schedules deletion of its stored assets and the corresponding World Labs world. Cleanup requires the server worker and provider to be available, so physical removal can finish later. A request already accepted by the provider may continue processing; its result is then removed rather than published in your account. Limited technical identifiers remain while deletion is being completed.

To prevent duplicate submissions and abuse of generation limits, limited deletion records and daily usage counters are scheduled for removal after 35 days, during server maintenance. Counters use a server-keyed pseudonymous identifier derived from the Telegram account, not a copy of the input image or description; they can remain after account deletion so deleting and recreating an account does not reset the same-day limit. A cleanup record can remain longer while provider deletion or an uncertain request still needs reconciliation.

World Labs’ world-deletion API removes the world and associated assets. This does not establish a fixed deletion period for every provider log, backup or prior model-training use. Provider retention and any reuse or opt-out arrangements follow the applicable provider terms and account agreement. A provider’s temporary download link is not a permanent backup. If LIA cannot identify a provider job after an interrupted submission, the operator must reconcile it before confirming provider cleanup.

5. Backups, infrastructure and legal retention#

Hosting provider, database region, infrastructure log retention and backup expiry: Information not provided. No unverified “deleted everywhere in 30 days” or similar guarantee is made. These settings must be determined and disclosed before public launch.

If backups are introduced, deleted data must not silently become active again after a restore. Access and expiry must be limited, with a process to reapply deletion. Any preservation needed for a legal obligation or specific dispute must have a documented basis, defined scope and review period; it must not become indefinite retention of every project.

6. Downloads and copies you share#

An exported project or account file may contain personal material, including its stored image. Save it in a secure place. Deleting a project in LIA does not remove copies you downloaded or sent to another person.

If public sharing becomes available, its audience and controls must be visible before publication. Private account storage does not automatically grant permission to add the content to a public gallery.