Last updated: 14 October 2026
Awesome Lottie is an independent product, operated from Mauritius. The operator is the data controller for the information described on this page, and can be reached at the address on our Contact page — that is the fastest route for anything in this policy, including the requests in section 12. If you need the operator's name and registered details in writing — for a supplier review, or a data-protection request that requires them — ask at that address and we will provide them.
Awesome Lottie is a hosted service, so your work is stored on our servers rather than only on your computer. Specifically we hold:
When you export, your project is sent to our server, which generates the Lottie file and sends it back to you. We do not keep a copy of the exported file. MP4 is encoded in your own browser from that generated animation.
Access to a project is limited to you, anyone you share it with, and members of a team it belongs to. Our staff do not read project content as a matter of course; we may need to look at a specific project if you ask us to help with a problem in it, or where we are required to.
The service runs on servers rented from Hostinger, which hosts the application and its database on our behalf, in a data centre in the United Kingdom. Other companies are involved only where this policy says so: Lemon Squeezy for purchases (section 7), our email provider for the messages in section 8, and Sentry for error reports, below. None of them is given your project content, and none of them is permitted to use what they do see for their own purposes.
The tutorial videos on our site are hosted on YouTube. Nothing is loaded from YouTube until you press play on one; from then on, that video is played by YouTube, using its privacy-enhanced mode, and YouTube's own privacy policy applies to it.
Sentry, our email provider and Lemon Squeezy are companies based in the United States and process what they receive there, so that data leaves the European Economic Area and the United Kingdom. Each is bound by its own data-protection terms for that transfer.
Like any web server, ours and our host's keep short-lived technical records. Our application keeps a log of faults for up to about 30 days; it holds account numbers, never your projects, and email addresses only in shortened form. To limit repeated sign-in and reset attempts, we keep a scrambled fingerprint of the requesting network address, keyed with a secret that stays on the server, for about one day; it cannot be turned back into the address. Our host also keeps its own standard server logs, which include network addresses, under its own retention period. We do not store the network address a password reset was requested from.
When something goes wrong in the editor, a report is sent to Sentry, an error-tracking service, so that we find out about faults instead of waiting to be told. A report contains the error message, the technical stack trace that says which part of the code failed, the address of the page you were on with any query string removed, the version of the app, and general browser and device information.
It does not contain your projects, your artwork, your name or your email address, and reports are not tied to your account. We have deliberately turned off the features that would collect more — the activity trail, session recording and performance tracing — because in an editor those would pick up your layer names and file names, which are yours.
The editor sets one cookie, which holds your session: it is what signs you in and keeps you signed in. It is required for the service to work — without it every page would ask you to sign in again — and it is not used to track you across other websites. Our public pages set no cookies at all.
The editor also keeps a few things in your browser's own storage, on your device: your interface preferences, such as the timeline view, the order of panels, the animations you used most recently and messages you chose not to see again; and, if saving to your account fails, a copy of the unsaved project so that your work is not lost. None of this is sent to anyone or used to track you, and clearing this site's data in your browser removes it.
We do not use advertising or analytics cookies, and the fonts the editor uses are served from our own server, not by a third party.
Purchases are processed by Lemon Squeezy, our merchant of record. Lemon Squeezy collects your payment details and billing information directly — we do not receive or store your card number. We receive your email address, the subscription's status, plan and renewal dates, and identifiers linking it to your account, in order to give you the plan you paid for and to provide support.
We send email for a small number of things: confirming your address, resetting your password, team invitations, and notifying you when your account's email address is changed. These are part of running the service, not marketing. Delivery is handled by our email provider, which necessarily sees the address and the message.
If you email us for support, we keep that correspondence — including your email address and whatever you send us — for as long as needed to resolve the request and to have a record of prior support history.
We keep your account and projects for as long as your account exists. Cancelling a subscription does not delete anything — the account returns to the free plan and your work stays where it is.
Deleting your account from your account settings removes your projects, your uploaded files and your team memberships. It is immediate and permanent, with no restore window, so export anything you want to keep first.
It also removes your email address from the invitations other people sent to you and from our billing records. What stays of a subscription is the payment record itself — the plan, its status and its dates — with no email address or sign-in link attached to it.
Two things sit outside that. Records we are required to retain — a payment record held by our merchant of record, for instance — are outside our control to delete. And we keep backups of our database for up to 30 days, so a deleted account can still exist inside a backup until that copy is removed in the normal rotation.
A backup is only ever used to recover from a fault. If we have to restore one, we erase again, before anyone can sign in, every account that was deleted after it was taken. To do that we keep, outside the database, a one-way fingerprint of the email address of each deleted account and the time it was deleted. It cannot be turned back into the address, and it is used for nothing else.
You can do both of these yourself, from Account settings in the app, without asking us and without waiting.
The download does not include your password (we only ever store a hash of it, which is of no use to you) or the one-time links used to confirm your email or reset your password.
If you would rather we handled it, or you can no longer sign in, contact us at the address on our Contact page.
If this policy changes, we'll update the date at the top of this page. Continued use of the app after a change means you accept the updated policy.
Questions about this policy can go to the address listed on our Contact page.