Cookie Policy

This is short because EzFlip sets exactly one cookie, and it's one the site can't function without.

1. The session cookie

When you sign in with Steam, our server sets a single, cryptographically signed session cookie that keeps you logged in as you navigate the site. It's marked SameSite=Lax and is strictly necessary: without it, the site would have no way to know you're signed in from one request to the next. Under the ePrivacy rules that govern cookies, strictly-necessary cookies are exempt from the consent requirement, which is why there's no cookie banner on this site.

2. Local storage (not a cookie)

Your chosen display currency (e.g. USD/EUR) is remembered in your browser's localStorage, not a cookie. It never leaves your browser and is never read by our servers. The same applies if you close a site announcement banner: we remember which announcement you dismissed (so it stays closed) in localStorage too.

If you build a cart while signed out, its contents (the skins, markets, quantities and any prices you typed) and which list you last used are kept in localStorage as well. Unlike the items above, a cart is sent to our servers to be priced each time you view it. We don't store it: the request is answered and forgotten. When you sign in with Steam, your browser's cart is copied into your account and then removed from your browser.

3. Aggregate traffic analytics (not a cookie)

We use Cloudflare Web Analytics to see how the site is actually used — page views, referrers, and country, in aggregate. It's cookieless by design: it sets no cookie, writes nothing to localStorage, and builds no fingerprint or per-visitor record. Under the ePrivacy rules, that's why it needs no consent banner — there is nothing stored on your device for a banner to ask permission for.

No advertising cookies, no social media pixels, no cross-site tracking. We don't follow you across other sites, and we don't build an advertising profile from your visit.

4. If this changes

Adding any cookie-setting or device-storing tracking script in the future would require asking for your consent first, via a banner, before it's set, and this page would be updated to describe it. See our Privacy Policy for how any collected data would be used.