Cookie Policy — GuestQR
Last updated: September 25, 2026
A cookie is a small file a website leaves in your browser so it can recognise you (or your device) on your next visit. This page lists what GuestQR actually uses them for — there's no hidden tracking beyond what's listed here.
1. Cookies we set ourselves
All of them are strictly necessary: they make signing in work and keep it safe.
| Purpose | What it does | How long it stays |
|---|---|---|
| Sign-in session | Keeps you logged in between page loads, so you don't have to sign in on every page. | Until you sign out, or the session expires |
| Return address | Remembers which page to bring you back to after you sign in. | 10 minutes, or until you're signed in |
| Google sign-in check | A one-time security code that makes sure a Google sign-in was started on our page and not somewhere else. | A few minutes; deleted as soon as it's used |
We don't run our own analytics, advertising or tracking cookies.
2. Cookies set by someone else
- Signing in with Google. The "Sign in with Google" button on our sign-in page is provided by Google. When it loads, Google may use its own cookies, under Google's privacy policy. If you sign in with email and a password instead, the button still appears, but you don't have to use it.
- Bot check on the sign-in and contact forms. The sign-in, sign-up and password-reset forms include an automatic check that they're filled in by a person, not a program. It runs in a small frame supplied by our abuse-prevention provider, which reads only the technical signals it needs to spot bots — not to track you or show you ads. Usually you won't see it at all; now and then it asks you to tick a box. The contact form on our contact page has the same check; it only starts once you begin filling the form in.
- Paying. Checkout doesn't happen inside our pages: it takes you to the checkout page of Link, the reseller of our plans, on its own address. Whatever cookies it needs are set there and covered by its privacy notice, not this one.
3. What about the guides your guests read?
Guest-facing guides don't set cookies at all. Visiting one doesn't require a cookie banner, sign-in, or any tracking — we spot unusual traffic patterns using a hashed IP on our server, not anything stored in the guest's browser. The one thing a guide remembers is the language the guest picked, kept in the browser's local storage so the guide opens in that language next time. It holds nothing but the language code.
4. Managing cookies yourself
Because the cookies we set are strictly necessary, there's nothing to opt out of within the product. If you'd rather not have them at all, you can block or delete cookies in your browser settings — just know that you won't be able to stay signed in.
5. Changes to this policy
If what we use changes, we'll update this page. Anything that adds new non-essential cookies will come with a way to say no, not just a policy update.
6. Contact
VIVO Aromi s.r.o. (full registered details on our Company Details page) Email: support@getguestqr.com