Cookie Policy

This policy explains the cookies Leumos Private Limited sets on leumos.ai and in Leumos AI Studio, and the other browser storage we use alongside them. It sits with our privacy notice, which covers everything else we hold about you.

These are what make a signed-in session possible, and what keep the Studio usable before you sign in. They carry no advertising or tracking purpose, and the service cannot work without them, so they are not subject to a choice.

• __Host-leumos_id and __Host-leumos_at — prove to our servers that the request is yours, so you stay signed in as you move around. They last one hour and are renewed while you are active.
• __Host-leumos_rt — lets your session be renewed without asking you to sign in again. It lasts up to thirty days from when you signed in.
• __Host-leumos_oauth — set only while you are signing in with Google, to make sure the round trip back to us is really yours and cannot be forged by another site. It is cleared the moment sign-in finishes.
• leumos_guest — set only if you open the Studio without signing in. It holds a random identifier for this browser and the time it first opened the Studio, so that how often it can start our servers before you sign in is limited and automated visits can be told apart. It identifies the browser, not you, and lasts up to one hundred and eighty days.

The four sign-in cookies are marked so that page scripts cannot read them, are sent only to leumos.ai, and are sent only over an encrypted connection. Signing out deletes them. Page scripts cannot read the Studio cookie either.

Two analytics services can run here — Google Analytics and Amplitude — to understand how the website and masked Studio controls are used. Neither loads, and no analytics cookie or replay storage is created, until you choose “Allow analytics.” Before that choice this website sends them no analytics or replay request. Each also runs only where it is switched on for the site you are visiting, so you may allow analytics and still meet neither.

Amplitude sets first-party cookies whose names begin AMP_ for its browser and session identifier and AMP_MKTG_ for attribution such as campaign and referrer information. Their default lifetime is up to 365 days. Temporary AMP_TEST_ and AMP_TLDTEST_ cookies may be created and removed while it checks browser support. Session Replay uses IndexedDB rather than a replay cookie.

Replay reconstructs public pages and masked Studio controls. Studio text and form fields are masked; footage, previews, images, file names, project names and account details are blocked. Replay stays off during sign-in and on Projects, billing, payment and test-harness pages.

On the sign-in, Projects and billing pages, where there is no replay, Amplitude still receives a few named events so we can see where signing up and subscribing break down: that a sign-up was started or confirmed, that a sign-in succeeded or failed, that a checkout was started, or that one failed. A failure carries one word for the kind of failure — credentials, transient, oauth, declined or server — and nothing else. No email address, no password, no card details, no amount, no payment provider’s message, and nothing you typed. If you allowed analytics, a completed subscription payment is recorded in Amplitude with the plan, amount and currency, and the payment’s reference, against your pseudonymous identifier.

Elsewhere, if you allow analytics, we record which features were used — which tool was pressed, which preset slot, whether an import or an export succeeded or failed, and how many clips or shots were involved. Every one of these is a word from a fixed list or a plain count. File names, project names, footage, timecodes and color values are never sent: anything outside that fixed list is discarded in your browser before the event is uploaded.

After you sign in, three facts may be attached to your pseudonymous identifier: your plan, how you signed in, and how long the account has existed as a range rather than a date. Your name and email address are never attached.

If you allow it, Google Analytics sets cookies whose names begin _ga. They give your browser an identifier so that repeat visits can be counted as one visitor rather than several, and they record what brought you to the site. They are first-party cookies, set for leumos.ai. Google’s own documentation describes their lifetimes; the property keeps event and user-level data for up to fourteen months.

Ad personalization stays off. Advertising measurement runs only if you accept. How Google uses information from sites that use its services.

We run no ad network, build no advertising profiles, and never sell or share what we collect for anyone else’s advertising. If you accept, Google’s conversion tag may set first-party cookies whose names begin _gcl_ so we can learn whether one of our own ads led to a sign-up or a purchase. It receives that a sign-up or purchase happened, and for a purchase its amount, currency and payment reference, but never your name, email or account. Ad personalization stays off. Decline or withdraw in Privacy choices and these cookies are removed.

If you arrive from one of our own ads, the link carries its campaign tags. Until you sign in, the Studio remembers them in this browser tab’s own memory (sessionStorage) only. It sets no cookie for this, and nothing stays on your device after you close the tab. Once you sign in, we keep the tags with your account to measure our own ads; the privacy notice says how.

Your analytics choice is kept in one cookie, leumos_analytics_consent, shared by leumos.ai and the Studio, so you are asked once and a change on either site applies on both. It holds only your choice, when you made it, and which wording of the cookie banner you answered, so that we can ask again if that wording changes. It lasts one hundred and eighty days from when you made it. Your browser sends it with requests to leumos.ai; we do not use it for anything other than remembering your choice. The same choice is also kept in this browser’s local storage, and the newer of the two wins.

• Clearing only cookies, or only local storage, will not reset your choice. Clearing all site data for leumos.ai will, and we will ask again.
• If your browser blocks both cookies and local storage, the choice lasts only for the page you are on, and we will ask again on your next visit.

The choice is per browser and per device, so allowing analytics on a laptop does not allow it on a phone.

Open “Privacy choices” in the footer of any page. You can allow analytics there, or withdraw it: on withdrawal, analytics storage is denied, Session Replay stops, and the first-party Google Analytics and Amplitude cookies already on your browser are removed. You can do this as often as you like, and withdrawing does not affect anything collected before you did.

Every major browser lets you see the cookies a site has set, delete them, and block them — usually under Settings, then Privacy. Browser help pages for Chrome, Safari, Firefox and Edge each describe it for that browser.

Blocking cookies for leumos.ai will stop you being able to sign in and stay signed in, because the essential cookies above are how a session is held. Blocking or deleting only the analytics cookies has no effect on the service.

If what we set changes, this policy changes with it and the “last updated” date at the top moves. Questions go to studio@leumos.ai. For the fuller picture of what we hold and why, read the cookies section of our privacy notice and the notice itself.