Skip to content
Shopsy

Legal

Cookies

The cookies the platform sets, what each one is for, and why analytics needs none of them.

Last updated

The short version

  • Storefronts set no cookies at all. Not one — which is why no shop running on Shopsy shows you a cookie banner.
  • The only cookies anywhere keep a merchant or an operator signed in to their dashboard. There are four, plus two that exist for a few seconds during a Google sign-in.
  • Analytics uses no cookie and no identifier that survives a day.
  • Fonts, images and scripts are served from our own servers, so opening a page here contacts nobody else.

Shops set no cookies

Browse a shop, fill a basket, check out and track the order, and not a single cookie is written. There is no advertising cookie, no analytics cookie, no cross-site identifier, and nothing to consent to — which is why you are reading a page about cookies rather than dismissing a banner about them.

The same is true of these marketing pages. Every font, image and script is served from this site’s own servers, so loading a page here makes no request to Google, to a font host, to a tag manager or to a CDN that could see you.

What is stored in your browser instead

A shop still has to remember your basket between pages. It does that in your browser’s own storage rather than in a cookie, which means it is never sent to a server, never sent anywhere else, and clearing it is entirely yours to do.

Browser storage used by a storefront
WhatYour basketWhereLocal storage, one per shopWhySo a basket survives closing the tab.How longUntil you empty it, order, or clear your browser.
WhatA discount code you enteredWhereSession storageWhySo it is still applied when you reach checkout.How longUntil the tab closes.
WhatYour order number and email, after orderingWhereSession storageWhySo refreshing the confirmation page does not lose your receipt.How longUntil the tab closes — deliberately, so a shared computer keeps nobody’s receipt.
WhatLight or dark modeWhereLocal storageWhySo the site opens the way you last left it.How longUntil you change it or clear your browser.

Every cookie, in full

These exist only in the merchant dashboard and the admin console. If you have never signed in to either, you have never received one of them.

Every cookie the platform sets
Nameshopsy_atWhat it doesKeeps you signed in.WhereMerchant dashboardLifetime15 minutes
Nameshopsy_rtWhat it doesRenews that session. Sent only to the single endpoint that consumes it, and nowhere else.WhereMerchant dashboardLifetime7 days
Nameshopsy_admin_atWhat it doesKeeps an operator signed in.WhereAdmin consoleLifetime15 minutes
Nameshopsy_admin_rtWhat it doesRenews that session, on the same narrow path.WhereAdmin consoleLifetime7 days
Nameoauth2-redirect-stateWhat it doesProves the Google sign-in that comes back is the one you started, and not somebody else’s.WhereOnly if you press “Continue with Google”LifetimeDeleted the moment you land back
Nameoauth2-code-verifierWhat it doesThe other half of the same protection, so an intercepted sign-in code is useless.WhereOnly if you press “Continue with Google”LifetimeDeleted the moment you land back
  • Every one of them is HttpOnly — your browser will not let any JavaScript read them, so a scripting bug in a page cannot steal a session.
  • Every one is SameSite=Lax, which is what stops another site making requests as you, and Secure in production so they only ever travel encrypted.
  • None of them identifies you to anybody else, and none is used for advertising or measurement.
  • Signing out clears the pair for the app you signed out of. There are two pairs because the merchant dashboard and the admin console are separate sessions that must be able to coexist.
  • The two Google ones are not a sign-in. They exist for the seconds between pressing the button and coming back, and they are cleared as soon as you do — whether the sign-in worked or not.

Why there is no cookie banner

Consent is required for cookies that are not strictly necessary — the ones that measure, profile or advertise. There are none here. The ones above are what "strictly necessary" means: without them, signing in does not work.

Analytics would normally be the exception that forces a banner. It is not, because it uses no cookie: a visitor becomes a salted code with the date mixed in, thrown away and remade every day. Privacy explains exactly what that stores.

So a banner here would be asking permission for something we are not doing. If that ever changes, the banner arrives with the change, and this page says so first.

Pages that are not ours

Paying for an order takes you to your payment gateway’s own page — Paystack, Flutterwave, Monnify or Stripe. That page is theirs, it sets its own cookies, and their policies govern it. We cannot see what they set and would not want to.

A merchant may also link their shop to Instagram, WhatsApp or elsewhere. Following one of those links takes you to that company’s site, on that company’s terms.

Clearing any of it

Every browser can clear cookies and site data for one site, and doing that here costs you a basket, a theme preference and a sign-in — nothing more, because nothing more is there. Blocking cookies for this site entirely will stop the dashboard being able to sign you in; a storefront will keep working perfectly.

The other policies