Cookies
CookiePolicy
Azelify sets one cookie, and it is the one that keeps you signed in. Here is that cookie, everything else stored in your browser, and why.
Last updated September 12, 2026
In short
There is no cookie banner on this site because there is nothing to consent to: Azelify sets exactly one cookie — the one that keeps you signed in — and runs no advertising or analytics trackers of any kind. Everything else it keeps lives in your browser's own storage, for your preferences and a local media cache. All of it is listed below.
1.The one cookie we set
Most cookie policies exist to disclose tracking. This one exists to tell you there is none. Azelify sets a single cookie, and its only job is to keep you signed in. There is no advertising cookie, no analytics cookie, no Google Analytics, no advertising pixel, and no cross-site tracking anywhere on this site or in the product.
We set it ourselves, on our own domain, at the moment you sign in, and we delete it when you sign out. It is marked HttpOnly, so the page's own JavaScript cannot read it; SameSite=Lax, so your browser does not send it from anyone else's site; and Secure, so it never travels over an unencrypted connection — which is also why its name carries the __Secure- prefix. It carries a random session identifier and nothing else — no name, no email address, no account details. Browsing this site signed out sets no cookie at all.
| What | Where | Why |
|---|---|---|
| Sign-in session | A cookie named __Secure-azelify.session_token, set on azelify.com | Keeps you signed in for up to seven days of continued use. Signing out deletes it, and so does clearing your cookies for this site. |
2.What else is stored in your browser
None of these is a cookie. They live in your browser's local storage and IndexedDB, they stay on your device, they are never transmitted to us, and clearing your browser data removes them — resetting your preferences and emptying the local media cache.
| What | Where | Why |
|---|---|---|
| Interface preferences | Local storage | Light or dark theme, panel layout, preview quality, and similar choices you made. |
| Editor recovery state | Local storage | Lets the editor recover an unsaved project if a tab crashes or you go offline mid-edit. |
| Cached project media | IndexedDB | Holds imported video and images locally so playback and scrubbing do not re-download them on every frame. |
3.Third parties on their own pages
One vendor sets cookies of its own, and it does so on its own domain rather than ours: Stripe, for fraud prevention when you reach checkout. Those cookies are governed by its privacy policy, not this one, and we cannot read them.
4.How to control any of it
Every browser can clear cookies and site data for a single site, usually under a "cookies and site data" or "clear site data" setting. Doing that for Azelify signs you out, resets your interface preferences, and drops any locally cached media, which will be re-fetched when you next open the project.
You can also block storage for this site entirely. The product will not work if you do — sign-in has nowhere to keep your session — but nothing about the choice is hidden from you.
5.Why there is no consent banner
Under the ePrivacy rules, consent is required for storage that is not strictly necessary to deliver a service you asked for. Everything listed above is strictly necessary in that sense — the session that keeps you signed in, your own settings, and a local media cache — and none of it is used for tracking or advertising. Storage that is strictly necessary does not require a banner. If that ever changes, a consent control will appear here before the storage does, not after.
6.Changes to this policy
If the product starts setting further cookies, or adds analytics, this page changes first and the date at the top moves. It is written against what the code actually stores, and it is meant to stay that way.
Spotted something in your browser that is not listed here? Tell us at [email protected].