MakeQR

Cookie Policy

Última actualización October 3, 2026

Este documento todavía no está en tu idioma. Se muestra la versión en inglés, que es la que se aplica.

En resumen

  • We only use cookies and browser storage that the site needs to work.
  • No analytics, no advertising and no tracking across websites — which is why there is no cookie banner to click.
  • People who scan your codes get no cookies from us at all.

1. What cookies are

Cookies are small text files a website stores in your browser. Websites can also store information in the browser in other ways — local storage, session storage and IndexedDB. The rules are the same for all of them, so this policy covers them all, and we call them "cookies" for short.

2. Why there is no cookie banner

The Norwegian Electronic Communications Act and the EU ePrivacy rules require consent before a website stores or reads information in your browser — unless it is strictly necessary to provide a service you have asked for. Everything MakeQR stores is of that kind. We do not use analytics, advertising or social media cookies, and we do not track you across other websites.

If that ever changes, we will ask for your consent before setting anything that is not strictly necessary, and update this page first.

3. What we store

NameTypePurposeHow long
NEXT_LOCALECookieRemembers the language of the pages you are reading, so links and redirects stay in that languageUntil you close the browser — or 12 months if you choose a language in your account settings
firebaseLocalStorageDbIndexedDBKeeps you signed in to your accountUntil you sign out
firebase:*Local and session storageUsed by our sign-in provider to complete sign-in, including "Continue with Google" and "Continue with Microsoft"Until you sign out, or until you close the tab
makeqr:draftSession storageCarries the code you designed over to your new account, so you do not have to start againDeleted as soon as it is used, when you close the tab, or after one hour

A logo you add to a code stays in your browser and is never uploaded or stored.

4. People who scan a code

The redirect behind a dynamic code, and the menus, PDFs and link pages we host, set no cookies and store nothing in the browser. Once someone is sent on to the destination, that website's own cookie policy applies.

5. When you leave MakeQR

Payment and subscription management open on Stripe's own pages (checkout.stripe.com and billing.stripe.com), and "Continue with Google" or "Continue with Microsoft" opens their sign-in pages. These services set their own cookies — for example to prevent fraud — under Stripe's cookie policy and the privacy policies of Google and Microsoft. We do not control them and receive nothing from them other than the result: that you paid, or that you signed in.

6. How to control them

You can see and delete cookies and site data in your browser's settings, usually under Privacy or Site data. If you delete them, you will be signed out, and a code you were in the middle of creating will be lost. Blocking them will stop sign-in from working, but you can still create static codes without an account.

7. Questions

Write to hei@makeqr.ai. Read more about how we handle personal data in our Privacy Policy.