Cookie Policy

A cookie is a small text file a website asks your browser to keep, so it can recognise you on the next request. Browsers also offer local storage, which works much the same way but is never sent to the server. This page lists both for Liite, so there are no surprises.

Liite sets only cookies needed for something you asked it to do. None are for advertising, profiling or tracking you across sites.

Sign-in session

Keeps you signed in to the dashboard. HttpOnly and Secure, so page scripts can't read it and it only travels over HTTPS. Set on liite.co alone, never on liite.site or a connected domain.

Set on liite.co. Lasts: Until you sign out, or 30 days of inactivity.

Sign-in protection

Short-lived cookies from our sign-in library that stop forged sign-in requests (CSRF) and remember which page to return you to.

Set on liite.co. Lasts: For the sign-in attempt.

Claiming a username

Remembers the username you typed on the home page so it's waiting for you after you sign up.

Set on liite.co. Lasts: 1 hour.

Password-protected pages and links

After a visitor enters the right password, one cookie for that page or site keeps it unlocked. It holds a signed token, not the password.

Set on The protected page's own address. Lasts: 30 days.

Print drops

After someone enters a drop code, lets them open and print that drop's files without typing the code again.

Set on liite.co. Lasts: 30 minutes.

Liite's own analytics for pages, uploaded sites and short links set no cookies. To count unique visitors we hash the IP address and browser string with a secret that changes every day, keep that hash for up to 36 hours and then delete it. Nothing is stored in the visitor's browser. How this works is in our Privacy Policy.

Some choices are kept in your browser's local storage instead of a cookie. They never leave your browser and we can't read them:

• Your own AI key, if you add one to use AI features through your own provider account.
• The name you tick items with on a shared list.
• Your answer to a site's consent banner (see section 5), so it isn't asked again.
• Drafts and settings in our free tools, so you don't lose work on refresh.
• Small dashboard preferences, such as which panel you had open.

Clearing your browser's site data removes all of these.

A page at liite.co/you is compiled by us and runs no code of its own, so by default it sets nothing beyond what section 2 lists. Two things can change that:

• Tracking pixels. A site owner may add Google Analytics, Meta Pixel or similar to their page. Those services set their own cookies under the owner's control and their own policies. Liite gives owners a consent banner to show before any pixel loads; the visitor's answer is kept in local storage on that site.
• Uploaded sites. HTML uploaded to you.liite.site or served on a connected domain is the owner's own code and may set whatever cookies its author chose. Liite never sets its own cookies on liite.site.

If you have a question about cookies on a site built with Liite, contact its owner first. Our Acceptable Use Policy applies to what they may do.

When you pay for a plan, checkout happens on Polar's pages and Polar sets its own cookies there. If you sign in with Google or GitHub, their sign-in pages set theirs. Neither reaches Liite pages. We don't embed advertising networks or social widgets on liite.co.

Because every cookie here does a job you asked for, there is nothing to opt out of in the usual sense. You can still block or delete cookies in your browser's settings. If you do:

• You'll need to sign in again, and you can't stay signed in without the session cookie.
• Password-protected pages will ask for the password on every visit.
• Everything public on Liite keeps working without cookies.

If we add a cookie or change what one does, we'll list it here and change the date at the top. Material changes are also announced in the changelog.