Cookies

Last updated 15 September 2026

This is the complete list. If something isn't here, Qrious doesn't set it.

Cookies

Two cookies, both strictly necessary. They are the same on a Qrious page someone shared with you and on qrious.ae itself. No advertising, analytics or social-media cookie is set anywhere.

  • __cf_bm

    Set by
    Cloudflare, the network in front of qrious.ae and in front of our file storage.
    What it holds
    A security token that helps tell people from automated bots.
    How long
    30 minutes.
    Why it's there
    Security. It is strictly necessary, and Cloudflare does not use it to track you.

  • __dpl

    Set by
    Our hosting provider, when a page loads.
    What it holds
    Which version of the site your browser loaded. It is the same for every visitor loading at the same moment, so it says nothing about you.
    How long
    Up to 24 hours.
    Why it's there
    It keeps your browser on one version of the site while we publish an update, so a page doesn't break halfway through.

Things kept in your browser

These aren't cookies — they stay in your browser's local storage and are never sent to us as they are.

  • qrious:visits:<page>

    Set by
    A Qrious page, in your browser's local storage — only outside the EU, the EEA and the UK.
    What it holds
    For that one page: the day you first opened it, how many days you have opened it, and the last day.
    How long
    Until you clear your browser's site data.
    Why it's there
    It lets the page's owner see whether people come back. It never leaves your device: the page sends only 'first visit', '2–3' or '4 or more'. It is not written at all in the EU, the EEA or the UK, when we can't tell your country, or when your browser asks not to be tracked.

  • qrious:consent

    Set by
    qrious.ae's own pages (home, pricing, templates and these pages).
    What it holds
    Whether you chose Accept or Refuse, and when.
    How long
    Until you clear it, or change your choice from Cookie choices in the footer.
    Why it's there
    So we don't ask you again on every page.

  • sb-…-auth-token

    Set by
    The dashboard, when you sign in to your own account.
    What it holds
    Your signed-in session.
    How long
    Until you sign out.
    Why it's there
    It keeps you signed in. Visitors to a Qrious page never get it.

  • qrious.dashboard-theme

    Set by
    The dashboard.
    What it holds
    Whether you chose light or dark.
    How long
    Until you clear it.
    Why it's there
    It remembers your choice.

What Accept turns on

Today, nothing. qrious.ae's own pages ask first so that if we ever measure visits to them, it happens only after you say yes. Refusing is one click, and closing the question counts as refusing. You can change your answer at any time from Cookie choices at the bottom of the page. A Qrious page someone shared with you never asks, because it sets nothing that needs your consent.

Things that load only when you tap

A video on a Qrious page loads from YouTube, Vimeo or TikTok only when you tap play. Until then nothing is requested from them. Once you do, that service's own cookies and rules apply. Signing in with Google works the same way: it involves Google only when you choose it.

More about what we collect and why is in the privacy notice.