Cookie policy.
We set only the cookies that keep you signed in, and one that remembers a discount code if you followed a link with one. There is no analytics, advertising or tracking on mockupflo.com, which is why you will not see a cookie banner.
Last updated · 12 September 2026
Cookies we set
When you sign in, our authentication provider, Supabase, sets session cookies on mockupflo.com (their names begin with sb-). They hold an encrypted session token so the editor knows who you are between page loads. They are strictly necessary for the service, so no consent is asked; they expire when the session ends or you sign out.
If you arrive through a link carrying a discount code (?coupon=), we remember that code in a cookie named mockupflo-coupon so the offer price follows you around the site and is applied when you check out. It holds only the code, is never used to identify you, and expires after 30 days or once you have bought a plan.
Cookies set by others
If you buy a plan, the checkout happens on Polar's domain, which sets its own cookies under Polar's policy. If you sign in with Google, Google sets cookies on its own domain during sign-in under Google's policy. Neither is set by us, and neither is used on our pages for tracking.
Storage that is not a cookie
The editor keeps your work and preferences in your browser's own storage, not in cookies: projects, media and autosaves in IndexedDB; the theme, timeline and export settings in local storage under keys beginning with mockupflo. Nothing in this storage is sent to us.
What we do not use
- No analytics or measurement cookies.
- No advertising or retargeting cookies.
- No social media pixels or embedded widgets that set cookies.
Your choices
You can block or delete cookies in your browser's settings. Blocking the session cookie means you cannot stay signed in to the editor. Clearing site data for mockupflo.com also removes the projects and preferences stored on your device.
Questions
Write to hi@support.mockupflo.com.