What cookies are
Cookies are small text files a website stores in your browser. They let the site remember things between pages and visits, for example that you are signed in or which language you chose.
This policy covers qdestera.com, the Qdestera app, the pages that open when someone scans a Qdestera QR code, and Qdestera digital menus. How we handle personal data in general is explained in our privacy policy.
Cookies we use
All of these cookies are first-party cookies set by Qdestera and are strictly necessary for the feature you use.
| Name | Purpose | Duration / type |
|---|---|---|
| .AspNetCore.Cookies | Keeps you signed in to the app (authentication). | Session cookie, or up to 14 days (renewed while you use the app) when you stay signed in |
| .AspNetCore.Correlation.… and .AspNetCore.OpenIdConnect.Nonce.… | Protect sign-in with Microsoft or Google against forged requests. | Temporary, only while signing in |
| .AspNetCore.Antiforgery.… | Protects forms against cross-site request forgery. | Session cookie |
| .AspNetCore.Mvc.CookieTempDataProvider | Shows one-time status messages after an action, for example “saved”. | Session cookie, removed once the message is shown |
| .AspNetCore.Culture | Remembers the language of the website and the app. | Persistent, 1 year |
| tatlink_tenant | Remembers the workspace you selected in the app. | Persistent, 30 days |
| menu_lang | Remembers the language a guest chose on a digital menu. | Persistent, 1 year |
| go_lang | Remembers the language a visitor chose on a hosted QR code page. | Persistent, 1 year |
Why there is no cookie banner
Privacy laws such as the EU ePrivacy rules and Turkey’s KVKK allow cookies that are strictly necessary to provide a service the user asked for without prior consent. Every cookie in the table above falls into that group: without them you could not sign in, submit forms safely or keep your language and workspace.
Because we do not use any optional cookies, there is nothing to accept or reject, so we do not show a consent banner. If we ever add optional cookies, we will ask for your consent first and update this page.
Cookieless website analytics
On our public website and sign-in pages we may use a privacy-friendly analytics tool (Plausible or Umami) that we host ourselves. It counts page views without setting cookies and without building profiles of individual visitors, and it is not used on hosted QR pages or digital menus.
Scan statistics that account owners see for their own QR codes and short links are collected on our servers when a code is scanned. They do not rely on cookies.
Local storage
Some features keep small pieces of information in your browser’s local storage instead of a cookie. On a digital menu, the guest’s cart and recent orders are kept on the guest’s own device so they survive a page reload. In the app, we remember whether you collapsed the sidebar. This information is not used for tracking.
Sign-in and payment providers
If you sign in with Microsoft or Google, you are briefly sent to their sign-in page, where their own cookie policies apply.
When you open the checkout on our billing pages, the checkout is provided by our payment provider Paddle. Paddle may use its own cookies there, for example for payment security and fraud prevention, as described in Paddle’s policies.
Managing cookies
You can delete or block cookies in your browser settings. If you block the cookies listed above, you will not be able to sign in, and language and workspace choices will not be remembered.
Changes and contact
If our use of cookies changes, we will update this page and the date at the top. Our contact details will be published on this page before launch; until then, you can reach us through our contact page.