Last updated 12 November 2026. MUNOS is provided by Zuhayr Siddique, trading as MUNOS.
Whose data and what
- Delegates: name, country or position, school, committee, attendance, speaking and scoring records, and resolution and amendment submissions (document links, and an uploaded file if used). Conference staff enter these details; delegates submit documents through a QR form without an account.
- Staff and Chairs: name, role, committee, an email address if the organiser enters one, and a device identifier created when an access code is used.
- Organisers: name, email and billing details from the order form.
- Anyone using the service: IP address and browser details in our hosting providers' access logs.
Why, and who is responsible
We process the data to run the conference the organiser asked us to run. The organiser is the controller of the conference data: the organiser decides what is entered and is responsible for having a lawful basis to enter it, including any parental or guardian consent needed for minors. We act as the organiser's processor, only on their instructions and only to provide the service.
Who can see it
- The conference's staff, through access codes.
- Our administrators, for support.
- Anyone holding a committee's QR submission link can see the names and email addresses of that committee's Chairs, so delegates know who to contact. Organisers who do not want this can leave Chair email addresses blank.
We do not sell the data and do not use it for advertising. We do not use it for analytics beyond checking that the service is working.
Where it is held
Each conference has its own database. The database and file storage are hosted by Supabase, and the application is served by Vercel. Both run in Mumbai, India, so the data is held outside Qatar. Data is encrypted in transit (HTTPS only) and encrypted at rest by the providers. Staff access codes are stored only as one-way digests.
On staff devices
The conference app keeps working data in the browser's own storage so it works on poor connections: the sign-in session, unsaved drafts and help preferences. It sets no advertising or tracking cookies. This website (mun-os.com), served by Cloudflare, uses no cookies or analytics of its own. Its launch video loads from YouTube, in privacy-enhanced mode, only when you choose to play it.
How long
We keep the data for the hosting period, which ends 7 days after the last day of the conference unless the organiser changes it. The organiser then receives an export. We delete the data within 3 days of the organiser confirming they received it, or 14 days after sending it if they do not confirm. Provider backups and access logs may persist briefly after deletion, under the providers' own retention.
Security incidents
If we become aware of a breach affecting conference data, we tell the organiser promptly, with what we know, so they can meet any duty to notify.
Your rights and contact
Write to [email protected]. Delegates and staff should ask their conference organiser first; the organiser tells us what to change or delete.
Changes
We date each version of this notice and tell organisers of material changes by email.