Skip to content
Back to home

Legal document

Cookie Policy

Version 2026-11-01.1Published on 2 November 2026

Last updated: 1 November 2026 (version 2026-11-01.1)

This Cookie Policy explains which cookies and similar tools the website https://quantum-mind.mgquantumsystems.com uses and what the Quantum Mind mobile app does on your device. It complements the Privacy Policy.

1. In short

  • We use only technical cookies that are strictly necessary for the operation and security of sign-in.
  • We use no profiling, advertising or statistical analytics cookies, nor cross-site tracking tools. The only third-party services involved are the Vimeo and VdoCipher video players, which in the app and, when the online academy is on, in the browser may use technical tools needed for playback (section 7).
  • For this reason we show no consent banner: it is not required for strictly necessary tools.
  • The public pages of the website set no cookies and do not use the browser’s local storage.
  • When the online academy is on, to sign in from the browser (the pages that start with /app) we also use the technical session cookies described in section 5 and, on the video screens, the Vimeo player (section 7).
  • Videos are played with the Vimeo or VdoCipher player, which may use their own technical tools during playback (section 7).
  • The mobile app does not use cookies of its own: it keeps a few items in the device’s secure storage (section 7).

2. Controller

The controller is Allinners LLC, a company registered in Sharjah Media City, United Arab Emirates (Office 10, Level 1, Sharjah Media City, Sharjah, UAE — PO Box 487177). Contact: support@mgquantumsystems.com.

3. What cookies are

Cookies are small text files that a website saves in the browser. By “similar tools” we mean other technologies that store or read information on the device, such as the browser’s local storage. Technical cookies are needed to make the site work or to provide a service you asked for, for example keeping you signed in; they are not used to track you.

4. Public pages

The home page, the Privacy Policy, the Cookie Policy, the Terms and Conditions, the account deletion page and the support page set no cookies, do not use local storage, load no third-party resources and contain no analytics tools. Even the fonts are served from the same domain as the site.

5. Technical cookies of the sign-in pages and the panel

The following cookies are set only when you open the sign-in pages (sign-in, forgotten password, password reset, invitation) or the management panel reserved for staff. Students normally use the mobile app and these pages are for opening an invitation or password reset link; when the online academy is on they can also sign in from the browser, with the cookies described below. In production the name of each cookie is preceded by the prefix __Host-, which binds it to our domain and to the HTTPS protocol.

  • qm_csrf: protection against forged requests (CSRF), that is, unwanted actions carried out in your name. Readable by the page; SameSite Strict. Duration: session (deleted when the browser is closed).
  • qm_did: random device key, used to recognise an already authorised device and apply the device limit; on the server we keep only a hash of it. HttpOnly; SameSite Lax. Duration: 400 days. It is set at the first sign-in attempt from that browser, even if it fails.
  • qm_mfa: temporary challenge of two-step verification. HttpOnly; SameSite Strict. Duration: 5 minutes.
  • qm_at: access token that keeps the session authenticated. HttpOnly; SameSite Lax. Duration: about 15 minutes, renewed as long as the session is active.
  • qm_rt: refresh token that allows the session to be kept. HttpOnly; SameSite Lax. Duration: normally 12 hours and in any case no longer than 7 days.

All these cookies have the Secure flag. When you sign out of the panel qm_at, qm_rt and qm_mfa are deleted; qm_did remains until it expires and qm_csrf until the browser is closed. None of these cookies is used to track you or for advertising or statistical purposes.

Online academy (pages /app). When it is on, students can also sign in from the browser. In that case we set the technical cookies below, separate from those of the staff panel, so the two sessions do not affect each other. In production the name of the access cookie is __Host-qm_sat and the others follow the same pattern, with a prefix that binds them to our domain and to the HTTPS protocol. The qm_csrf cookie is the one described above.

  • qm_sat: access token that keeps the student’s session authenticated. HttpOnly; SameSite Lax. Duration: about 15 minutes, renewed as long as the session is active; if you do not choose “Stay signed in” it is also deleted when the browser is closed.
  • qm_srt: refresh token that allows the session to be kept. HttpOnly; SameSite Lax. Duration: the browser session or, if you choose “Stay signed in”, up to a maximum number of days set by the Academy (normally 30). An inactive session ends after a period set by the Academy (normally 8 hours).
  • qm_srem: indicator present only if you chose “Stay signed in”, which keeps the refresh cookie persistent when it is renewed. HttpOnly; SameSite Lax. Same duration as the refresh cookie.
  • qm_sdid: random device key, used to recognise an already authorised device and apply the device limit; on the server we keep only a hash of it. HttpOnly; SameSite Lax. Duration: 400 days.
  • qm_smfa: temporary challenge of two-step verification. HttpOnly; SameSite Strict. Duration: a few minutes.

All these cookies have the Secure flag. When you sign out of the online academy qm_sat, qm_srt, qm_srem and qm_smfa are deleted; qm_sdid remains until it expires. They are strictly necessary to keep you signed in and to protect access; none is used to track you or for advertising or statistical purposes. Signing out of the staff panel does not end the online academy session and vice versa.

6. Browser local storage

The panel reserved for staff saves in the browser’s local storage the preference qm.sidebar.collapsed (side menu closed or open). It is an interface preference, it stays on your device, it is not sent to our servers and it contains no personal data. The public pages do not use it. When the online academy is on, the /app pages use the browser’s storage for two small technical items: the qm-lms-signout key (local storage), a timestamp that tells the other tabs of this browser that you signed out, and the qm-lms-landed key (session storage, deleted when the tab is closed), which remembers for that tab the session and programme identifiers already opened, so the same welcome screen is not shown again. For the same purpose the tabs exchange a message on a BroadcastChannel (qm-lms), which stores nothing. They stay on your device, are not sent to our servers and are not used to track you.

7. Mobile app

The app does not use cookies of its own and contains no advertising or third-party analytics tools; the only technical exceptions are the Vimeo and VdoCipher video players, described below. On your device it saves, in the system’s secure storage (Keychain on iOS, Keystore on Android, accessible only while the device is unlocked), only the data needed to work:

  • the session refresh token, until you sign out of the app;
  • a random device key, used to recognise an already authorised device;
  • the indication that you completed the initial introduction;
  • the push notification token, only if you turned notifications on, until you turn them off or sign out of the app;
  • the email address of the last sign-in, only if you chose “Remember me”, until you sign in again without that option or delete the account.

The app update service (EAS Update, by Expo) also saves on the device a random installation identifier, used to distribute updates; it is not linked to your account (see the Privacy Policy, section 3.5). This data is strictly necessary to provide the service you asked for or is saved at your choice.

Some content is video hosted by Vimeo and played with its player, embedded in the app and, when the online academy is on, on the video screens of the /app pages of the website. When you start a video, Vimeo receives your IP address and technical device data and may use technical cookies or local storage needed for playback, which it manages under its own privacy policy (see also ours, section 3.9). Video cover images are also served by Vimeo’s network: when a cover image is shown, Vimeo receives your IP address and technical device data. Videos protected with DRM are played with the VdoCipher player (India), embedded in the same way: when you start the video VdoCipher receives your IP address and technical device data and may use technical cookies or local storage needed for playback and for the DRM protection, which it manages under its own privacy policy (see also ours, section 3.9). They are strictly necessary to show you the video you asked for; we do not use them to track you and the players are not present on the public pages of the website and, in the online academy, are loaded only on the video screens. People who booked or purchased a Quantum Identity session see the same videos in the same app.

8. What we do not do

  • No profiling or advertising cookies.
  • No analytics or audience measurement tools on the website, ours or third-party; no third-party analytics tools in the app.
  • No embedded social network buttons or content or maps; the only embedded third-party content is the Vimeo and VdoCipher video players, shown in the app and, when the online academy is on, on the /app pages of the website, only on the video screens (section 7).
  • No cross-site or cross-app tracking and no disclosure of data to advertising networks.

If in the future we wanted to introduce tools that are not strictly necessary, we would update this policy and ask for your consent before using them.

Technical cookies and similar tools that are strictly necessary do not require consent (Art. 122 of the Italian Personal Data Protection Code, Legislative Decree 196/2003; Art. 5(3) of Directive 2002/58/EC; the Italian Data Protection Authority’s Guidelines on cookies and other tracking tools of 10 June 2021), but they require this notice. Any personal data processed through them is processed for our legitimate interest in running and protecting the service (Art. 6(1)(f) GDPR) and to provide the service you requested (point (b)).

10. How to manage or delete cookies

You can view, block or delete cookies from your browser settings. If you block the technical sign-in cookies you will not be able to sign in to the panel, to the online academy from the browser or use the sign-in pages, because the session cannot be kept; the public pages keep working. To remove what the app saves on the device, delete the app. Signing out of the app removes the session token and the notification token (the latter also when you turn reminders off in Profile, Notifications); the remembered email stays until the next sign-in without “Remember me” or until the account is deleted. On iOS some data saved in the secure storage (for example the random device key) may remain after uninstalling: to remove the credentials, sign out of the account first.

The website and the app contain links that you open voluntarily (for example the link to a live session on Zoom, a WhatsApp message to support, the stores). When you open them you leave our site: the cookies of those services are governed by their own notices.

12. Changes

If we change the tools we use we update this policy, with date and version number.

13. Contacts

For questions write to support@mgquantumsystems.com.