Skip to content
Back to home

Legal document

Privacy Policy

Version 2026-11-01.1Published on 2 November 2026

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

Quantum Mind is a private academy run by Allinners LLC (“Allinners”, “the Academy” or “we”). This policy explains which personal data we process when you use the Quantum Mind mobile app and the website https://quantum-mind.mgquantumsystems.com, why we process it, how long we keep it and which rights you have. It is provided under Articles 13 and 14 of Regulation (EU) 2016/679 (“GDPR”).

1. Who we are

The data 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).

For any privacy question and to exercise your rights you can write to support@mgquantumsystems.com.

This policy is addressed to students who use the app, to invited people who have not yet activated their account, to visitors of the website and to people who contact support. The management panel of the website is reserved for the Academy’s authorised staff.

Allinners is based in the United Arab Emirates but offers the service to people located in the European Union, mainly in Italy: for this reason it processes data in compliance with the GDPR (Art. 3(2)). It also complies, to the extent applicable, with United Arab Emirates Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (“PDPL”).

2. In short

  • Quantum Mind is reserved for enrolled students: accounts are created by the Academy, there is no self-registration and the app is for adults.
  • No payment takes place in the app or on the website: we do not collect card or bank account data.
  • If you booked or purchased a Quantum Identity session, GoHighLevel sends us your name, email and language and delivers the account activation link to you; the videos are hosted by Vimeo or VdoCipher, which receive your IP address and technical device data when a video is played (Vimeo also when its cover image is shown); on videos protected by VdoCipher your name and email appear as a watermark (sections 3.8 and 3.9).
  • We use no advertising or tracking tools and no third-party analytics services: internal statistics are calculated on our own data and shown in aggregated form (section 4). We do not sell or hand over your data and we do not use it to profile you for commercial purposes.
  • Data is hosted in European Union data centres (the Netherlands).
  • Reserved content carries a personal watermark with your name, your email and an identification code: it protects the Academy’s work (section 5).
  • Your journal and your exercise answers are private: by default no member of staff can read them (section 6). The only exception is a worksheet you choose to send to the team: from then on the copy you sent is read by super administrators, administrators and support staff until you withdraw it (section 6.1).
  • The Academy may connect external tools (for example a CRM, a sales platform, an automation tool or an artificial intelligence assistant): they receive only account, enrolment, progress and live session data, never the journal, the exercise answers, staff notes or security data (section 3.7). One exception, your choice: if you send a worksheet to the team and the text you read before sending says so, a copy also reaches the team’s private Slack channel (sections 3.7 and 6.1).
  • From the app you can download your data and delete your account immediately: Profile, Privacy and data (sections 10 and 11).

3. Which data we process and where it comes from

3.1 Data entered by our staff

When our staff creates or invites your account it enters: email address, first name, last name (if provided), phone number (optional, visible only to staff and not shown in the app), language, time zone, the programme you are enrolled in with the status and dates of the enrolment, and any internal staff notes (for example the reason for a suspension). You do not enter this data in the app: staff take it from the information you gave us when you enrolled, which happens outside the app. Internal notes are personal data: you can ask for a copy.

3.2 Data you provide

  • Your password, which we store only as an irreversible cryptographic hash, and your optional two-step verification (we store the secret in encrypted form and the recovery codes as hashes).
  • Changes to your profile: first name, last name, language and time zone.
  • Exercise answers and the private journal: free text up to 20,000 characters, choices and ratings from 0 to 10.
  • If you send a worksheet to the team: a copy of your answers as they were when you sent it, with the titles of the exercise, programme, week and lesson, and the proof of your consent (the version of the text you read, the date and time of the send and whether the text you read mentioned the copy on Slack) (section 6.1).
  • Your acceptance of the legal documents: version, date and time, IP address, user agent and device.
  • The messages you send to support.
  • Optional: your consent to push notifications (token) and, on your device, the email remembered for sign-in.

3.3 Data generated by using the service

  • Progress: modules opened, acknowledged and completed; status and percentage of contents; pages viewed; audio segments played; listening position.
  • Live sessions: first and last join, number of joins and the device used.
  • Devices: a random key generated by the app (on the server we store only a hash of it), platform, the device name set in the operating system (it may contain your name), model, operating system and app version, date of last use, last IP address and its country (where detectable).
  • Sessions and sign-ins: date and time, IP address, country (where detectable), user agent and outcome of every sign-in, including failed attempts and the email address typed, even when it does not match any account.
  • Security events (section 5.3) and action log (audit): the log records, with date and time, IP address and user agent, the actions carried out with the account, for example sign-ins and sign-outs, password changes, profile edits, revocation of devices and sessions, opening of documents and audio, joining live sessions, acknowledgement and completion of modules, acceptance of the legal documents, registration of notification tokens, data export and deletion, as well as actions by staff on your account (section 9).

3.4 Website and technical logs

The public pages of the website (home, policies, support, account deletion) set no cookies, load no third-party resources and contain no analytics tools. The hosting provider records technical data of each request (for example IP address, date and time, requested address, user agent) to run and protect the service. Our application logs record for each request the method, requested address, request identifier, outcome and response time, without IP address; they are scrubbed of passwords, tokens and codes and may contain technical errors and internal account identifiers. For the cookies of the sign-in pages and of the panel, see the Cookie Policy.

3.5 Data exchanged with Expo: notifications and app updates

  • Push notifications: if you turn them on (with “Remind me” on a live session or with the “Live reminders” switch in Profile, Notifications), the app obtains a notification token from Expo. To do so it sends Expo an installation identifier, the native device token (Apple or Google), the app identifier and the Expo project identifier. The token is then saved on our servers together with your account, the platform and the device. When a live session of your programme is about to start, our servers send Expo your token and the text of the notification (the title of the session and the minutes left before it starts), which Expo forwards to Apple (APNs) or Google (FCM) to deliver it to your device. The text contains neither the Zoom link nor the access code. Once you have turned them on on a device, the app renews the token at every launch without asking you again, until you turn them off or sign out; signing out deletes the token and, at the next sign-in (also with another account), notifications stay off until you turn them on again. The permission granted in the device settings alone does not turn them on. Reminders reach only devices where your account has an active session: once you are signed out, also because the session expired or was revoked, that device no longer receives them.
  • App updates (EAS Update): at each launch the app checks whether an update of the code and resources only is available. The request contains a random installation identifier, the platform, the app version, the identifiers of the updates in use or that failed and, if the app closed abnormally last time, a short excerpt (up to 1,024 characters) of the error log, in addition to the IP address and user agent, which are unavoidable in any request. It does not contain your email, name or account identifiers.

3.6 Data we do not collect

We do not collect payment data (no payment takes place in the app or on the website), GPS location, contacts or photos, and we do not access the camera or the microphone. We do not use advertising identifiers. The app contains no third-party advertising, analytics or crash-reporting tools. If you add a live session to the calendar, the event is written only to your device’s calendar: we do not read the events you already have and we receive nothing.

3.7 Data sent to external tools connected by the Academy

The Academy may connect external tools of its choice to the system, for example a CRM, a sales or email platform, an automation tool or an artificial intelligence assistant such as Claude (by Anthropic). The connection works in three ways: an application programming interface (API) to which the tool authenticates with a private key; automatic notifications (webhooks) that our system sends to the address given by the Academy when something happens, for example when a student is created or completes a session; and a connection for artificial intelligence assistants (MCP), which uses the same key. Only super administrators can create and revoke keys and webhooks, and they must confirm their password again. A connection exists only if the Academy creates it.

The data that can be sent to these tools is only the following:

  • Student account data: internal identifier, email, first and last name, account status (for example invited, active, suspended), language, time zone, date of creation, date of activation and date of last activity.
  • Enrolments: programme, status (for example active or revoked), start and end date.
  • Progress: for each session of the programmes you are enrolled in, whether it is completed, in progress, available or still locked and, if completed, when; the notice that a session was completed, with the session title and the date and time.
  • Live sessions: title, description, date and time, duration, status and whether a replay exists; the notice that you joined a live session, with the identifier of the live session and the date and time of joining.
  • Aggregated statistics of the Academy (for example the number of active students and the average progress), without personal data.
  • Account deletion: when you delete your account, the tool receives a notice with the internal identifier only, so that it can delete its copy (section 11).

The same keys can also create or change data in the system, for example invite a student, enrol them in a programme or schedule a live session. These actions are recorded in the audit log with the name of the key used, instead of the name of a person.

Never sent: exercise answers and the journal (Slack receives only a worksheet you choose to send to the team, as described below); internal staff notes; passwords, two-step verification and recovery codes; sessions, devices, IP addresses and user agents; security events and the risk score; the audit log; the Zoom link and access code; content files (audio, documents, images) and their addresses. Staff accounts cannot be reached: keys only see students.

So that it is possible to check that notifications arrived, our system keeps for 30 days a log of every webhook delivery, with the outcome and a copy of the content sent (section 9).

Slack. Slack works differently from the tools described above: it uses no keys, webhooks or assistant, but receives from our system, in the team’s private channel, the copy of a single worksheet, and only when you send it to the team and the text you read before sending mentions the copy on Slack. No other exercise answer and no part of the journal reaches Slack. What the copy contains, who reads it and how you withdraw it is explained in section 6.1.

3.8 People who booked or purchased a Quantum Identity session

If you booked or purchased a Quantum Identity session (the booking and any purchase take place outside the app and the website), the system the Academy uses to manage bookings and communications, GoHighLevel (HighLevel Inc.), automatically sends us your name, your email address and your language, together with the reference of the booking or purchase and the duration of the access. With this data we create your account, if you do not have one yet, and enable you for the corresponding programme.

To deliver the account activation link to you, our servers send it to GoHighLevel, attached to your contact, and GoHighLevel delivers it to you; if you already have an active account, GoHighLevel only tells you that a new access has been added. For each delivery we keep the outcome (sent, failed, skipped), the number of attempts and any technical error, not the link.

The access can be permanent or last a set number of days, counted from the activation of the account (or from the grant of the access, if you already have an active account). The content is available in Italian and English: where the English translation is missing you see the Italian. In this case too no payment takes place in the app or on the website: we do not receive card or bank account data.

3.9 Video, Vimeo and VdoCipher

Some content is video hosted by Vimeo, Inc. (United States). Before each playback we check that your account has access to the content and only then generate the link to the video, which we do not store in our logs. When a video’s cover image is shown or the video is played (the cover image is loaded from Vimeo’s content delivery network, the video by its player, embedded in the app and, when the online academy is on, in the pages of the website that start with /app), your device connects to Vimeo’s servers, which receive your IP address and technical data about the device and the connection (for example device type, operating system and the app it comes from) and may use technical cookies or similar tools needed for playback. Our servers do not send Vimeo any data about your account.

Other videos are protected with the DRM technology of VdoCipher (VdoCipher Media Solutions Pvt Ltd, India). Before each playback we check that your account has access to the content and only then ask VdoCipher for a temporary playback authorisation (valid for about 30 minutes), which we do not store in our logs. With that request we send VdoCipher your name and your email address, which the player shows as a moving watermark over the video to discourage and trace unauthorised copies, and your internal user identifier; on the website the request also states the domain from which the video may be played. During playback, in the app and, when the online academy is on, on the pages of the website that start with /app, your device connects to VdoCipher’s servers, which receive your IP address and technical data about the device and the connection (for example device type, operating system, browser and playback data). We send VdoCipher no other data about your account. In the browser the DRM and the watermark discourage copying but cannot always prevent screenshots and screen recordings (section 5.2).

3.10 Access from the browser (online academy)

When the Academy turns the online academy on, you can also reach your programmes from the browser, on the pages of the website that start with /app. To keep you signed in the website sets technical session cookies, separate from those of the staff panel and described in the Cookie Policy (section 5): for example qm_sat for access, qm_srt for renewing the session and qm_sdid for recognising the device. Requests go through the website to our servers, which handle them like those of the app: the data is the same and the same rights and retention periods apply. The browser is registered as a device of your account, with a name derived from the browser and the operating system, and counts towards the device limit. A browser session ends after a period of inactivity and in any case after a maximum number of days set by the Academy. On the video screens the Vimeo player is embedded in the pages of the website (section 3.9).

For each purpose we indicate the legal basis provided by Article 6 of the GDPR.

  • Managing your account and providing the service: creating and inviting the account, giving you access to the content of your programme (guided audio, workbooks, exercises), saving answers and journal, calculating progress and the unlocking of modules, managing live sessions and attendance. Legal basis: performance of our relationship with you as an enrolled student (Art. 6(1)(b)).
  • Authentication and account security: password, any two-step verification, sessions, authorised devices and their limit, temporary lockout after failed sign-in attempts, password reset. Legal basis: point (b) for authentication; point (f), our legitimate interest in preventing abusive access, for the protective measures.
  • Protecting the content and the service: personal watermark, risk signals and score, audit log, request rate limits. Legal basis: legitimate interest (Art. 6(1)(f)), with the balancing described in section 5.
  • Proof of acceptance: keeping a record of the version of the legal documents you accepted or acknowledged. Legal basis: point (b) for the Terms and Conditions; point (f) for the proof, to defend our rights.
  • Invitation and password reset: delivering your invitation link and reset links. Today the system does not send them by email: our staff hand them to you through the channel agreed with you and, if you have forgotten your password, you can ask for one by writing to support@mgquantumsystems.com. If we turn on automatic email sending in future, through a transactional email provider that will act as our processor, we will name it in this policy. Legal basis: point (b).
  • Support and requests about your data: answering your messages and handling the exercise of your rights. Legal basis: points (b) and (f) for support; point (c) to comply with the obligations on the exercise of rights.
  • App updates and maintenance: distributing fixes and improvements to the app code only, without a new store release. Legal basis: point (f), our interest in keeping the service secure and working.
  • Internal statistics: processing aggregated data, for example how many students complete a module or attend a live session, shown to staff in aggregated form, to improve the programmes. Legal basis: point (f).
  • Connection with the Academy’s tools (API, webhooks, assistants): keeping the data described in section 3.7 aligned with the tools the Academy uses to run its activity (for example records and enrolments, the calendar of live sessions, service communications to students, support, internal reporting, automations), and allowing staff to consult or update it also through an artificial intelligence assistant. These tools serve the management of the relationship with students and of the Academy: they are not used for advertising or marketing and, if in future we wanted to use them for promotional communications, we would update this policy and, where the law requires it, ask for your consent. Legal basis: performance of our relationship with you as an enrolled student (Art. 6(1)(b)) and the Academy’s legitimate interest in organising the management of the programmes efficiently and without errors (point (f)).
  • Quantum Identity programmes: receiving from GoHighLevel the data of people who booked or purchased a session, creating the account or adding the access, honouring its duration and delivering the activation link to you. Legal basis: performance of our relationship with you (Art. 6(1)(b)) and our legitimate interest in managing access correctly and without errors (point (f)).
  • Video playback: giving you access to the videos of your programme through Vimeo or VdoCipher, after checking your access. Legal basis: point (b). Video protection: showing your name and email as a watermark on videos protected by VdoCipher and protecting them from unauthorised copying. Legal basis: legitimate interest in protecting the Academy’s content and the rights of those who created it (point (f)).
  • Live session reminders by push notification (optional): registering the token and using it to send you a single notification for each live session of the programmes you are enrolled in, normally between 25 and 30 minutes before it starts (an automatic check runs every 5 minutes; if a session is created or moved to less than 30 minutes before its start, the notification goes out at the next check). The content is the title of the session and how many minutes are left before it starts. If the Academy moves the time of a session, you receive a new reminder for the new time. A copy of the notification also appears in the notification list of the app. You receive no reminder until you turn them on yourself on that device, even if the notification permission is already granted in the settings, and today we use push notifications for nothing else. Legal basis: your consent (Art. 6(1)(a)), which you can withdraw at any time with the “Live reminders” switch in Profile, Notifications or by signing out of the app (both delete the token from our servers), or from your device’s notification settings. If you turn notifications off from the device only, you stop receiving them, but the token stays registered until you use the switch, sign out of the app, it becomes invalid or 12 months pass without the app registering it again.
  • Worksheets sent to the team (optional): when you choose to send a worksheet, making the copy of your answers readable by authorised staff in the management panel and, if the text you read before sending says so, in the team’s private Slack channel, in order to support you along your path; if needed, the team contacts you outside the app. Legal basis: your explicit consent at each send (Art. 6(1)(a); for any special-category data the answers may contain, Art. 9(2)(a)), which you can withdraw at any time with “Withdraw submission” (section 6.1). To be able to show your consent we keep in the audit log the version of the text you read, the date and time of the send and whether the text you read mentioned the copy on Slack, without the answers: legal basis, our legitimate interest in proving the consent received (point (f)).
  • Legal obligations and defence of rights: answering requests from authorities, establishing or defending a right. Legal basis: points (c) and (f).

We do not use your data for advertising, commercial profiling or marketing, and we do not sell it.

Live sessions, Zoom and recordings

Live sessions take place on Zoom. The link and the access code are shown in the app only to enrolled students who have accepted the legal documents, from 30 minutes before the start (unless set otherwise) until the end of the session. When you join we record your attendance (first and last join, number of joins, device). We send Zoom no data about your account: the name you use in Zoom and what Zoom collects are processed by Zoom under its own privacy notice.

Some sessions may be recorded and made available as replays to enrolled students. If you take part with your microphone or camera on, or speak or write in the chat, your voice, your image and your contributions may appear in the recording. Zoom notifies participants when recording is in progress: if you do not wish to appear, keep your microphone and camera off and do not speak. Legal basis: legitimate interest in making lessons available to those who could not attend (Art. 6(1)(f)). You can object and ask us to remove or obscure your contribution by writing to support@mgquantumsystems.com.

5. Content protection, watermark and security controls

5.1 Personal watermark

PDF documents and workbook pages are shown as images generated at the time of the request, with a personal watermark that shows your name (or, if missing, your email), your email and a six-character code derived from your account identifier (“ID”); on content with reinforced protection it also shows the wording “Quantum Mind — Confidential” and the date and time (UTC) of viewing. A similar line (“Licensed to …”, with name, email, ID and the same wording) is overlaid on the screen over documents and the audio player. The watermark is generated each time and is not stored. On content with the highest protection level it may be denser and include a nearly invisible marking with your ID code. If reserved content were disclosed without authorisation, this information makes it possible to trace the account it came from.

Downloadable documents. The Academy may mark some PDF documents as downloadable. If you choose to download one, you receive the original file, without your personal watermark (a form to fill in, for example, stays fillable), and you save it on your device, where we can no longer protect it: the permitted use is described in the Terms and Conditions (section 5). Every download is logged in the audit log: who downloaded it (your account, with IP address and user agent), which document, when and the size of the file. It is the only element that makes it possible to trace the account if the file were disclosed without authorisation; the same legal basis (legitimate interest, section 5.4) and the same retention period as the audit log (section 9) apply. We do not keep a copy of the file for you, nor a version personalised with your data: the original stays in the Academy’s library and we do not see what you do with it once you have saved it. A download also counts as opening the document in your progress.

5.2 Blocking of screenshots and screen recordings

On screens that show protected content the app asks the operating system to prevent or blank screenshots and screen recordings and to hide the preview in the app switcher, where the system allows it. On iOS and on Android 14 or later the app notices on the device that a screenshot was taken while protected content is open and shows you a warning: the event is not recorded or sent to our servers and the app does not see what you captured. Traceability depends solely on the personal watermark. In the browser (online academy) this protection does not exist: a browser does not allow screenshots and screen recordings to be prevented, so they cannot be blocked. When the window loses focus or the tab is hidden, documents are blurred and the personal watermark appears on every content; here too traceability depends on the watermark.

5.3 Security signals and risk score

The system records “security events” when it detects anomalous signals: a number of devices above the limit or an attempt to exceed it; simultaneous sign-ins from different IP addresses; a sign-in from a country different from those used before (only where the country can be detected); unusually numerous or fast requests for pages or audio segments, typical of automated copying; repeated failed sign-in attempts; reuse of a session token that had already been replaced, a possible sign of theft; a request for content from an IP address different from the one it was authorised for. Each signal is assigned a score and the sum of the open signals of the last 30 days forms the account’s risk score.

The score only serves to flag the situation to authorised staff, who assess it case by case, for example by asking you for clarifications. No account is suspended, blocked or restricted automatically because of the score: we do not take decisions based solely on automated processing that produce legal effects on you or similarly significantly affect you (Art. 22 GDPR). The score is a form of profiling limited to security (Art. 4(4)): you can object and ask for a person to intervene (section 10).

There are, however, automatic technical protective measures: temporary lockout after repeated failed sign-in attempts, closing a session if a token that had already been replaced is reused, a limit on the number of authorised devices (normally three) and rate limits on requests. They do not assess you as a person and apply to everyone in the same way; if you find yourself locked out by mistake write to support@mgquantumsystems.com.

5.4 The balancing of interests

For the watermark, the security signals and the audit log we rely on legitimate interest (Art. 6(1)(f)). The interest is to protect reserved educational material, the result of the work of the Academy and its authors, from unauthorised copying and disclosure, and to ensure the security of accounts and of the service. We consider the processing necessary and proportionate because:

  • it shows each person only information that already concerns them (name and email) and only on the content they access;
  • it does not read what is on your screen, nor your files or your other apps;
  • the watermark is not stored and the risk score produces no automatic decision;
  • access to this data is limited to authorised staff and actions are logged;
  • the data is kept for limited periods (section 9);
  • less intrusive measures would not offer equivalent protection.

For this reason we consider that your interests and rights do not override ours. You can nevertheless object to the processing on grounds relating to your particular situation (section 10): we will assess the request case by case.

6. Private journal and exercises

Your exercise answers and your journal are yours and private. We use them only to save them, show them to you, calculate whether an exercise is completed and include them in the export of your data. The only exception is a worksheet you choose to send to the team (section 6.1).

By default the Academy’s management tools do not allow any member of staff to read the content of your journal. There is a setting, switched off, which, if the Academy turned it on, would allow reading only to accounts of the highest administration level (super administrator) holding a specific permission; every read would be recorded in the audit log and, before turning it on, we would update this policy. Ordinary administrators, support staff and instructors do not have this permission. Staff can only see progress data (for example whether you completed a module) and aggregated statistics. A data export carried out by staff at your request also leaves out the journal under the same conditions: you can always export it yourself from the app.

The journal is a free space. We invite you not to write information that is not needed for your programme, in particular data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic or biometric data, data concerning health or sex life or sexual orientation, or identifiable data of other people. If you choose to write it, we process it only to keep it and show it back to you, on the basis of your explicit consent (Art. 9(2)(a)). You can withdraw it at any time by deleting your account or by writing to support@mgquantumsystems.com to ask for your answers to be erased; withdrawal does not affect the lawfulness of processing already carried out.

6.1 Worksheets sent to the team

Some exercises are worksheets that you can choose to send to the Academy team. Sending is optional and does not affect your access to the content or the completion of the exercise.

Private until you send. The answers you write in a worksheet are private like any other answer and stay private until you press “Send to the team”. Before sending we show you a text that explains who reads the answers, why, whether a copy also goes to Slack and how to withdraw the submission, and we ask you to confirm with a checkbox: sending is an explicit act, repeated for each worksheet and each new send. Answers you change after sending never reach the team until you send again.

What the team receives. A copy of the worksheet as it was at the moment you sent it: the titles of the exercise, programme, week and lesson, the questions and your answers, in your language. If the Academy later edits or deletes the exercise, the copy already sent does not change.

Who reads it. Super administrators, administrators and support staff, from your page in the management panel; instructors cannot. Each time staff open a worksheet to read the answers, the opening is recorded in the audit log (who and when); the list with titles and dates is not. If the text you read before sending says so, a copy of the worksheet, with your name and email, also reaches the team’s private Slack channel (sections 3.7 and 7.2): a private channel, not shared with other organisations, which the Academy reserves for the people authorised to read worksheets and from which it removes anyone who leaves the role or loses it. Reads inside Slack are not logged.

Why and on which basis. To support you along your path: if needed, the team contacts you outside the app, by call or message. Legal basis: your explicit consent at each send (Art. 6(1)(a)). The answers may reveal special-category data (for example about health, private life or beliefs) or concern other people: we invite you not to write other people’s names or details about your health; if you write them and send the worksheet, we process them on the basis of your explicit consent (Art. 9(2)(a)). The team reading a worksheet is not therapy or a diagnosis (Terms, section 11).

Withdrawing. You can withdraw a submission at any time, from the exercise with “Withdraw submission” or in Profile, Privacy and data, “Sent worksheets”; withdrawing is possible even after your access to the programme has ended. Withdrawing means the copy is deleted from the panel and the Slack message is deleted (if the deletion does not succeed at once the system retries and, for persistent errors, the Academy completes it by hand). Your answers stay in your private space. If you send a worksheet again, the new copy replaces the previous one and the previous Slack message is deleted. Withdrawing withdraws your consent; withdrawal does not affect the lawfulness of processing already carried out. You can also ask staff to delete a copy by writing to support@mgquantumsystems.com: it is deleted from the panel and from Slack.

Export and erasure. The worksheets you sent are part of the export of your data (also of the export carried out by staff at your request, if the person carrying it out can read worksheets) and are deleted, together with their Slack messages, when you delete your account (sections 10 and 11).

How long we keep it. Until you withdraw it, staff delete it at your request or you delete your account (sections 9 and 11).

7. Who can access the data

7.1 Academy staff

Authorised staff access data according to their role and only as far as needed. Administrators and support see profile, enrolments, devices, sessions, sign-in history, security events and acceptances; instructors manage the content and see only aggregated statistics; access to the journal is described in section 6. Worksheets you send to the team can be read by super administrators, administrators and support staff, not by instructors (section 6.1); administrators and super administrators can delete them at your request. Staff accounts require two-step verification, sensitive operations require the password to be confirmed again and actions are logged. Creating and revoking API keys and webhooks (section 3.7) is reserved for super administrators: ordinary administrators, support staff and instructors do not have this permission.

7.2 Providers and other recipients

  • Railway Corporation (United States): hosting of the web and API services, the database, content storage, backups and technical logs. The data is hosted in the European Union (the Netherlands, with storage in Amsterdam). It acts as processor (Art. 28 GDPR).
  • Expo, 650 Industries, Inc. (United States): push notification and app update service (EAS Update); it receives the data described in section 3.5, including the text of live session reminders (title and minutes left). It acts as processor.
  • Apple (APNs) and Google (Firebase Cloud Messaging): deliver notifications to iOS and Android devices and receive the native device token and the text of the notifications, which passes through their servers. The Apple App Store and Google Play distribute the app and process data under their own notices. They act as independent controllers for their own services.
  • Zoom Video Communications, Inc. (United States): only when you choose to take part in a live session. It processes data under its own terms and privacy notice, which we invite you to read.
  • GoHighLevel (HighLevel Inc.) (United States): management of bookings and communications; it sends us the name, email and language of people who booked or purchased a Quantum Identity session and receives from us the account activation link in order to deliver it to you (section 3.8). It acts as processor (Art. 28 GDPR) on behalf of the Academy.
  • Vimeo, Inc. (United States): video hosting and playback; it receives the data described in section 3.9 when a video’s cover image is shown or the video is played. It acts as processor on behalf of the Academy; for the technical data collected by the player its terms and privacy policy also apply.
  • VdoCipher Media Solutions Pvt Ltd (India): hosting of DRM-protected videos and playback with a watermark; it receives the data described in section 3.9 (name and email as a watermark, user identifier, IP address and technical data during playback). It acts as processor on behalf of the Academy; for the technical data collected by the player its terms and privacy policy also apply.
  • Slack (Slack Technologies, a Salesforce company; United States): the team’s messaging tool. It receives, in the Academy’s private channel, a copy of a worksheet (with your name, your email and your answers) only when you send the worksheet to the team and the text you read before sending says so (sections 3.7 and 6.1). It acts as processor (Art. 28 GDPR) on behalf of the Academy; for transfers see section 8.
  • External tools connected by the Academy (for example CRMs, sales or email platforms, automation tools, artificial intelligence assistants such as Claude by Anthropic): they receive the data described in section 3.7, and only that, for the purposes stated in section 4. We choose them so that they process the data on behalf of the Academy, as processors under an agreement compliant with Art. 28 GDPR, and not for their own purposes; for artificial intelligence assistants we use only services and settings in which the data is not used to train the provider’s models. Because these tools change over time, we do not name them one by one in this policy: you can ask for the up-to-date list of those that receive your data by writing to support@mgquantumsystems.com.
  • Transactional email provider: today no automatic email sending is active, so no email provider receives any data. If the Academy turns it on to send invitations and password reset links, it will appoint the provider as processor and we will name it in this policy.
  • WhatsApp (Meta) or your email provider: only if you choose to contact us through those channels; they handle the data as independent controllers.
  • Authorities and advisers: only where the law requires it or where necessary to establish or defend a right.

We do not sell or hand over your data for advertising or marketing and we do not share it with advertising networks, data brokers or social networks.

8. Transfers of data outside the European Economic Area

Data is hosted in the European Union. Some providers, however, are based in the United States (Railway, Expo, Zoom, Apple, Google, GoHighLevel, Vimeo, Slack) and may receive data or access it from outside the Union. For these transfers we rely, depending on the provider, on the European Commission’s adequacy decision on the EU-US Data Privacy Framework, where the provider participates in it, or on the standard contractual clauses adopted by the European Commission (Art. 46 GDPR), together with the necessary supplementary measures.

The external tools connected by the Academy (section 7.2) may also be based, or process data, outside the European Economic Area, in particular in the United States. VdoCipher is based in India, a country for which there is no European Commission adequacy decision: for the data we send it we rely on the standard contractual clauses (Art. 46 GDPR) provided for in the data processing agreement with the provider, together with the necessary supplementary measures. Before connecting one we check that the transfer takes place with the safeguards described in this section (adequacy decision on the EU-US framework or standard contractual clauses).

Allinners is based in the United Arab Emirates, a country for which there is no European Commission adequacy decision, and its staff access from there the data hosted in the Union. Because Allinners is directly subject to the GDPR (Art. 3(2)), it applies the GDPR safeguards to this data; where the access amounts to a transfer, we base it on appropriate safeguards under Articles 46 and following (in particular the standard contractual clauses) or, in the limited cases where they apply, on the derogations of Article 49, such as a transfer necessary for the performance of the contract with you.

You can ask for information on the safeguards adopted by writing to support@mgquantumsystems.com.

9. How long we keep data

We keep data only for as long as needed for the purposes stated. An automatic operation run every day deletes data that has passed the following terms.

  • Account and programme data (profile, enrolments, progress, answers and journal, attendance at live sessions, acceptances of documents): for as long as the account exists; deleted or anonymised immediately when you delete the account (section 11).
  • Sign-in sessions: 30 days after the session expires or is revoked; history of refresh tokens already replaced: 30 days after replacement.
  • Invitation and password reset links already used or expired: 30 days.
  • Sign-in history (outcome, IP address, user agent, email typed): 12 months.
  • Security events: 24 months.
  • Audit log (relevant actions, including failed sign-ins, with author and email, IP address and user agent): 24 months.
  • Devices: deleted 12 months after last use.
  • Push notification tokens: removed when you turn reminders off with the switch in Profile, Notifications, when you sign out of the app or when Expo reports that they are no longer valid; otherwise deleted after 12 months without the app registering them again.
  • In-app notifications (including the copy of live session reminders): 12 months from creation, or immediately if you delete your account.
  • App update data held by Expo: under Expo’s terms.
  • Webhook delivery log (outcome and a copy of the content sent to the connected tools, which may include email and name): 30 days from creation, then deleted; if you delete your account, the copies that contain your data are deleted immediately (section 11).
  • Copies held by the connected tools: the tools that have already received your data keep it under their own rules and the agreement with the Academy; when you delete your account, the Academy arranges for your copy to be deleted, as far as technically possible (section 11).
  • Quantum Identity booking and access data (reference of the booking or purchase, duration of the access, outcome of the deliveries to GoHighLevel): for as long as the account exists; deleted when you delete your account (section 11). Copies held by GoHighLevel, Vimeo and VdoCipher are kept under their own rules and the agreement with the Academy.
  • Worksheets sent to the team (the copy of the answers, with titles, programme, week and lesson) and the corresponding Slack message: until you withdraw them, staff delete them at your request or you delete your account (section 11); they have no automatic expiry. The audit log entries about sending, withdrawing, deleting and staff openings do not contain the answers and follow the retention of the audit log. Any technical copies held by Slack are kept under its own rules and the agreement with the Academy.
  • Technical logs of the hosting service: for the period set by the provider’s settings and in any case only for as long as strictly necessary for security and for diagnosing malfunctions.
  • Correspondence with support: for as long as needed to handle the request and, afterwards, for the period strictly necessary to protect our rights.
  • Backup copies: the database is copied periodically and the copies are kept for a limited period and then overwritten. After an account is deleted its data may remain in backup copies until they rotate; if a backup had to be restored, the deletions already carried out would be applied again.

We do not automatically delete inactive or never-activated accounts. After the relationship with the Academy ends, the account can be anonymised by staff at your request or on their own initiative when the data is no longer needed. If you were invited and do not want to activate the account, write to support@mgquantumsystems.com and we will delete your data.

10. Your rights and how to exercise them

You have the right to:

  • access your data and obtain a copy (Art. 15);
  • rectification of inaccurate or incomplete data (Art. 16);
  • erasure (Art. 17);
  • restriction of processing (Art. 18);
  • portability of the data you gave us, in a structured, machine-readable format (Art. 20);
  • object to processing based on legitimate interest, on grounds relating to your particular situation (Art. 21);
  • withdraw consent at any time, without affecting processing already carried out (Art. 7(3)): for notifications with the “Live reminders” switch in Profile, Notifications, by signing out of the app or from your device settings; for worksheets sent to the team with “Withdraw submission” (section 6.1);
  • not be subject to decisions based solely on automated processing with legal or similar effects (Art. 22): we do not make them.

How to exercise them

  1. From the app, in Profile, Privacy and data: “Download my data” immediately produces a JSON file with a copy of your data (up to 3 requests per hour) and “Delete my account” deletes the account. “Sent worksheets” lists the worksheets you sent to the team and lets you withdraw them. In Profile you can also edit your first name, last name, language and time zone and manage Authorized devices, Active sessions and Notifications.
  2. By email to support@mgquantumsystems.com, also to rectify your email address or phone number, ask for restriction or object, or obtain the intervention of a person. If you no longer have the app you can also find the instructions to request deletion on the page https://quantum-mind.mgquantumsystems.com/account-deletion.

The export includes your profile data, enrolments (including any internal staff notes), progress, journal, attendance, devices, sessions, sign-in history, acceptances, security events, notifications, the worksheets you sent to the team (as the team received them) and the audit log entries that concern you. It does not include your password, security secrets or data of other people. The file is created temporarily on your device and handed to the system share sheet: you choose where to save it or whom to send it to; the app removes it shortly afterwards.

We reply without undue delay and in any case within one month of the request. The term may be extended by a further two months if the request is complex or if we receive many: in that case we will tell you. To protect you we may ask you to verify your identity, for example by replying from the account’s email address. Exercising your rights is free of charge, except for manifestly unfounded or excessive requests. If the request concerns data already sent to external tools connected by the Academy (section 3.7), we communicate the rectification, erasure or restriction to those tools, unless this proves impossible or involves disproportionate effort (Art. 19 GDPR).

If you believe the processing breaches the law you can lodge a complaint with a supervisory authority: in Italy the Garante per la protezione dei dati personali (Piazza Venezia 11, 00187 Rome, https://www.garanteprivacy.it) or the authority of the European Union country where you live, work or where the alleged infringement took place. We ask you, if possible, to write to us first so that we can resolve the matter. If you are subject to the UAE PDPL you can exercise the rights it grants through the same channels.

11. What happens when you delete your account

Deletion from the app is immediate and irreversible: there is no review by staff. To confirm we ask for your password (and the verification code, if you turned on two-step verification). Staff accounts cannot be deleted from the app: write to support@mgquantumsystems.com.

  • We delete: sessions, devices and notification tokens, invitation and reset links, recovery codes, sign-in history (also for the email you had used) and security events about you, notifications and preferences, exercise answers and journal, the worksheets sent to the team (together with their Slack messages), progress, attendance and enrolments, and the copies in the webhook delivery log that contain your data (section 9).
  • We anonymise the account: the email is replaced by an unusable placeholder address, password and two-step verification are removed, the name becomes “Utente eliminato”, phone and internal notes are removed. You will no longer be able to sign in.
  • We keep, in pseudonymised form, the acceptances of the legal documents (version and date, without IP address, user agent and device, linked only to an internal identifier of a now anonymous account) as proof to defend our rights (Art. 17(3)(e)). The audit log entries generated by your actions remain until the 24 months expire, but without email, IP address and user agent; in email-change entries the old and new addresses are removed. Entries generated by staff actions on your account (for example a suspension or a change to an enrolment) also remain for up to 24 months; they may carry a reason written by staff but not your email.
  • On the device: the app signs out of the account and removes the session token, the remembered email and the notification token.
  • Connected tools: those configured to receive it get a deletion notice with the account’s internal identifier only, which no longer holds any personal data, so that they can delete their copy; the Academy arranges for it to be deleted as far as technically possible. We cannot delete data that a tool has already received ourselves: that depends on the tool (section 9).
  • Backup copies: see section 9.

12. Data security

  • Communications between the app or the browser and our servers are encrypted (HTTPS); traffic between our own services stays on the hosting provider’s private network.
  • Passwords are stored only as strong cryptographic hashes and session tokens on the server only as hashes; the secret of two-step verification is encrypted.
  • In the app the refresh token is kept in the system’s secure storage (Keychain on iOS, Keystore on Android), accessible only while the device is unlocked and not transferable to other devices; the access token stays in memory only. The app does not save protected content on the device, with one exception: the PDF documents the Academy marks as downloadable, which you can save yourself by choosing the download button (section 5.1).
  • Two-step verification is mandatory for staff and, when active on an account, is requested at sign-in; reuse of a session token causes the session to be revoked.
  • Permissions are assigned by role, sensitive operations require the password to be confirmed again and relevant actions are recorded in a log protected against unauthorised changes.
  • Audio is served encrypted and without providing the original files; content is kept in private storage, never public.
  • API keys are stored only as a hash (the key in clear is shown once, at creation), have limited permissions, an optional expiry and an optional list of allowed IP addresses, can be revoked at once and have a limit on requests per minute. Webhook notifications are signed, are sent only to https addresses on the public internet (never to internal or reserved networks) and the signing secret is stored encrypted.
  • Application logs contain no passwords, tokens or codes.

In case of a personal data breach that results in a risk to your rights and freedoms we will notify the competent authorities and, if the risk is high, we will also inform you, in the ways and within the times required by law.

13. Minimum age

The service is reserved for people who are at least 18 years old. We do not knowingly collect data of minors: if we find that an account belongs to a minor, we may suspend it and delete the data. If you think this has happened, please write to us.

14. Mandatory and optional data

To create and keep the account we need the data provided by the Academy (email and name) and the password: without them we cannot give you access. Some technical data (IP address, user agent, device data) is unavoidable to run and protect the service. Notifications, the email remembered on the device and adding live sessions to the calendar are optional; what you write in the exercises and the journal is up to you, and sending a worksheet to the team is your choice, always revocable (section 6.1).

15. Changes to this policy

The version in force is always the one published on the website and in the app, with its date and version number. In case of substantial changes, for example new purposes, new recipients or new retention periods, we ask you to acknowledge them in the app before you continue to use it.

16. Contacts

Allinners LLC, a company registered in Sharjah Media City, United Arab Emirates (Office 10, Level 1, Sharjah Media City, Sharjah, UAE — PO Box 487177). Email for privacy and support: support@mgquantumsystems.com. Website: https://quantum-mind.mgquantumsystems.com.