Cookie Policy

Why there is no banner

Consent banners exist because of cookies that are not necessary: third-party analytics, advertising, tracking across sites. We set none of those, on any page.

What is left is the cookie that remembers you are signed in, which is exempt from consent everywhere it is regulated because the service cannot work without it. Showing you a banner for it would be theatre.

The cookies we set

One, today. If our sign-in library ever needs a second one to do the same job, it is still a strictly necessary cookie and this table is where it appears — the page is updated before the cookie ships, not after.

Name	What it does	How long it lasts
__Secure-better-auth.session_token	Holds your signed-in session. Set when you sign in, sent only to this site, unreadable to JavaScript, and marked secure so it travels only over HTTPS — which is what the __Secure- prefix in the name declares. Over plain HTTP, which is only ever local development, the same cookie is named better-auth.session_token.	Up to a week, renewed while you keep using the site. Deleted when you sign out.

Public pages set no cookie at all. You can read every page of this site, including the store size pages and this one, without anything being stored.

How we count page views without a cookie

We do measure which pages are read, and it is the reason this page still says there is nothing to consent to: the counting is done by Plausible, running on a server we operate, and it stores nothing in your browser — no cookie, no local storage entry, no identifier of any kind that survives the page you are on.

What it records is a total: the page, the site that linked to it, the country, and the kind of browser and device. Your IP address is used to work out the country and is not stored, there is no profile of you to build, and nothing about it follows you to another site. Consent rules attach to what is stored on your device; here nothing is, which is why there is no banner and no opt-out toggle to hunt for.

If you would rather not be counted at all, any content blocker that blocks Plausible stops it, and the site works exactly the same without it.

What Paddle sets during a checkout

When you open the checkout to buy a plan, it runs inside a frame served by Paddle, who are the merchant of record for the sale. Paddle sets its own cookies there to run the payment and prevent fraud. Those are theirs, governed by their privacy policy, and they are set only when you open a checkout.

We never see them, and no payment cookie is set by browsing this site.

What the editor stores in your browser

Not a cookie, but it is your data on your machine and it belongs in this document: the studio saves the looks you choose to keep in your browser’s local storage, under the key easyappscreens:styles, so you can start a new app from a style you built for an old one.

It never leaves your browser, it is not sent to us, and clearing your browser data removes it. Your projects themselves are stored on the server, not here, so clearing local storage does not lose your work.

How to remove them

Signing out removes the session cookie. Clearing site data in your browser removes both the cookie and the saved styles.

Blocking cookies for this site is your right and it will stop you signing in, because there would be nothing to remember you by. Any question about this page goes to support@easyappscreens.com.