Legal
Cookies and Browser Storage
This page explains the cookies and similar browser storage that LottieFyr uses for consent, authentication, session continuity, functional feedback, and optional analytics.
Effective date: June 16, 2026
How LottieFyr uses storage
LottieFyr uses a small amount of first-party browser storage to keep core features working. That includes the consent record, auth-related storage used by Firebase, and session storage used to restore in-progress UI states.
Analytics behavior depends on regional rules and the choice you make through the consent banner or the footer's Cookie settings control. In places where consent is required, analytics storage stays limited until you allow it.
Consent cookie
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
| lottiefyr_consent_v1 | First-party necessary cookie | Stores consent version, analytics choice, and last update timestamp. | 182 days |
Essential auth and session storage
- Firebase Authentication uses browser storage to keep you signed in and maintain account session state.
- Core service behavior may also rely on temporary browser storage to restore UI progress after navigation or checkout return.
- These storage items are treated as essential because the related feature was requested by the user or is needed for core site operation and security.
Anonymous Lottie Repair feedback
If you use the thumbs-up or thumbs-down control on the Lottie Repair page, LottieFyr creates a random anonymous browser token and stores it in local storage under lottiefyr:lottie-fix:voter-token. Your latest choice is stored under lottiefyr:lottie-fix:vote so the page can remember it.
Only a hash of the browser token, your current vote, and creation and update timestamps are saved in our database. This functional feedback works independently of optional analytics consent. You can replace your vote by selecting the other button, or remove the local copy by clearing this site's browser storage.
Lottie assessment limits and reports
The public Lottie assessment does not place the uploaded file or returned report in cookies or browser storage. The report is held in page memory and is cleared when you reload or leave the page.
To enforce the anonymous hourly limit, the server derives a salted hash from the request network address and stores only that hashed identifier with an hourly count. This necessary security measurement works independently of optional analytics consent and does not store the raw network address in the assessment-limit record.
Session storage keys used by the current product
lottiefyr-svg-resume-v1: Temporarily restores in-progress Animate SVG work during the current browser session.lottiefyr-checkout-resume-v1: Keeps checkout-related resume state so the app can restore the UI after a purchase flow.lottiefyr-home-lane-v1: Remembers the selected converter lane during the current browser session.
Analytics storage and measurement
When analytics storage is enabled for your browser, LottieFyr uses Google Analytics and related measurement storage. Common cookie names may include:
_ga_ga_*_gid
These cookies help us understand aggregated traffic, navigation paths, and product usage trends. In regions that require consent, they are not loaded until you allow analytics. Refusing analytics does not block use of uploads, login, billing, support, or feedback features.
How to change your choice
You can reopen the consent controls at any time by selecting Cookie settings in the site footer. Changing analytics from on to off updates your stored preference and is intended to stop further analytics measurement from that browser.