Cookie Policy

1. What is used#

LIA uses cookies for account security and browser storage for requested features and preferences. The current application and documentation contain no advertising pixels or analytics trackers. Reading an article does not require a LIA account. Search in the documentation is performed locally in your browser; the query is not sent to a search provider.

Storage rules can apply to localStorage and IndexedDB as well as cookies. Where a local law requires consent for an optional purpose, that purpose must remain off until the required choice is obtained. Accepting the Terms of Service is not a general cookie consent.

2. Account cookies#

Blocking these cookies can stop account sign-in from working. Documentation on docs.lia.ad does not need the account cookie from lia.ad. Telegram’s own websites and application may use their own storage under Telegram’s rules.

• __Host-lia_session: an opaque account-session identifier used on the application host. Maximum lifetime is 24 hours; the server ends the session after two hours without activity. Signing out revokes it.
• __Host-lia_oauth: a short-lived browser binding used to complete Telegram web sign-in securely. It lasts up to five minutes and is cleared when the callback is processed.
• Development environments use the names lia_session and lia_oauth. Production cookies are Secure and HttpOnly, have SameSite=Lax and are scoped to their host; they do not contain project text or images.

3. Preferences and the terms notice#

The app remembers your chosen theme, viewer quality and motion settings so it can apply them on later visits. Documentation remembers its own system, light or dark choice in the localStorage entry lia.docs.theme.v1 on its separate origin. These preferences remain until changed, cleared or removed by the browser.

The terms notice stores the accepted edition and acceptance time locally. Closing it without accepting uses session storage for that visit. Neither record is a login credential, proof of verified age or permission for new processing purposes. An account acceptance is separately recorded by the server after an explicit action.

4. Guest materials#

Without an account, the app keeps bookmarks and the unfinished text draft in localStorage. Saved projects and prepared images use the browser’s IndexedDB database. These materials are not automatically copied into an account when you sign in.

Browser data can be removed by private-browsing rules, storage limits, site-data clearing or another person using the same device. Download important projects before clearing storage. This documentation host cannot read guest project storage on the application host.

5. Your controls#

You can change preferences in LIA, delete guest projects individually or clear the application’s site data in your browser. Clear docs.lia.ad separately if you also want to remove its local preferences. Clearing browser data signs you out locally but does not delete a server account; use Delete Account for that.

If optional analytics, advertising or other nonessential storage is introduced, the purpose, supplier, lifetime and required controls must be disclosed before it is used. There are no dormant advertising categories for you to approve today.