Privacy

What MUN Conference is

MUN Conference is software for running Model UN conferences. Schools, universities and clubs use it to build committees, run debate from the dais, take attendance and score speeches.

This page describes what the software stores, who can see it, and what it deliberately does not do. It describes the product as it is built today. Where something is not implemented, this page says so plainly instead of promising it.

Who has an account

Accounts belong to staff. On the conference side that means directors, secretariat, chairs and volunteers. On the organization side it means admins, editors and viewers.

Delegates do not have accounts. Nothing in the product asks a delegate to sign up, sign in, or create a password.

Sign-in is hosted by Base44, the platform the app runs on. The app never sees or stores a password. Google sign-in is offered by that hosted sign-in page.

What the app stores about delegates

For each delegate the app can hold a display name, the country or character they are assigned, their school, their grade, an optional email address, a meal preference, allergies and dietary notes, attendance status with the times it changed, and ratings on the speeches they give.

All of it is entered by conference staff, either typed into the app or imported from a CSV file the organization prepares. Delegates do not fill in their own details, and the app collects nothing from a delegate directly.

The allergies and dietary field exists because conferences cater meals. It is health information about a named student, and it should hold what catering needs to keep someone safe, not a medical history.

Delegates who are minors

Many delegates are secondary school students, and many of them are under 18. That is the normal case for this product, not an edge case.

The organization running the conference is responsible for having permission to enter a student’s details, from the school, the advisor or the parent, under whatever rules that school works to. The app cannot verify that permission exists and does not ask for it. That responsibility sits with the organization, and this page does not pretend otherwise.

Inside the product, a delegate’s name is shown only to staff of that conference. No public page shows a delegate’s name.

Scores, rankings and chair notes

Chairs record judgement as the conference runs: content and speaking scores from 1 to 5 on individual speeches, an optional one-line note on a speech, a four-part delegate rubric (research, speaking, diplomacy and decorum, 1 to 5), and free-text notes written about a delegate. Star ratings, head-to-head comparisons and award tiers recorded before 7 October 2026 are kept as they were; nothing in the app records new ones.

This is the dais’s working record. It sits behind the same access control as everything else: visible to staff of that conference and to nobody else. It never appears on a public page, and the product does not show it to the delegate it describes.

Chairs should write notes they would be willing to have read back to them in front of the delegate and their advisor. The software cannot enforce that. A free-text field holds whatever is typed into it.

How access is actually enforced

The tables holding delegates, conferences, organizations, organization members, conference members, delegate rankings and award duels are locked to server-side access only. Row-level security on each of them is set to the service role.

This means the browser cannot read those tables directly, even with a valid sign-in. Every read goes through a server function that first checks the caller staffs the conference being asked about. Delegate personal details are returned only to conference staff.

No public page shows conference data

Without signing in, anyone can open the home page, the download page and these legal pages. None of them shows anything about a conference, a committee or a delegate.

A chair may project their own console. It is the chair’s signed-in page on the chair’s laptop, with no public link and no token. It is built to show nations, not students’ names, email addresses or grades.

The public committee board link and the public awards page were retired on 7 October 2026, and the separate projector window on 9 October 2026.

Email

The only email the app sends goes to staff: when they are invited to an organization or a conference, and when that access changes or is removed. It is sent through the email integration built into the hosting platform. There is no third-party marketing or campaign tool in the product, and no mailing list is built out of delegate addresses.

The app never emails a delegate. A delegate email address is optional, and if staff do not enter one, nothing in the app needs it.

Payments

Card payment is not connected. The product cannot take a card, and there is nowhere in it that asks for one.

What it records is invoice requests and promo-code redemptions: that an organization asked to be invoiced, and which code it used. No card number, expiry date, security code or bank detail is collected or stored anywhere in the product.

Where the data lives

The app and its data run on Base44’s infrastructure. Base44 hosts the application, stores the database, and provides both the hosted sign-in and the email integration described above.

The chair console and the co-chair page each keep a copy of the committee (the speakers list, roll call, motions and votes, including delegate names and countries) and any changes, grades or notes not yet saved, in that browser’s local storage on that laptop. That is what lets a room keep running through a dropped connection. The copy stays on that laptop until its site data is cleared.

What the app does not do

There is no advertising in the product, no ad tracking, and no third-party analytics tool embedded in it.

Data is not sold, rented, or handed to anyone else to use for their own purposes.

There is no cookie banner, because there is almost nothing to consent to. The app sets what the hosting platform needs to keep a signed-in staff member signed in, and it remembers a chosen colour theme in the browser. There is no tracking cookie to decline.

There is no self-serve export button and no self-serve delete button for a delegate. That is not implemented. A delegate whose record should change or go asks the conference staff, who do it in the app.

Deletion has a real limit that is worth stating rather than hiding: a delegate with speeches recorded cannot be deleted until those speech records are removed first. Staff have to clear the debate record before the delegate record will go.

Asking for a correction or a removal

Start with the conference. Its staff entered the record and can edit or delete it directly, which is faster than anything routed through us.

If that is not possible, because the conference is over or its staff have moved on, write to {{CONTACT_EMAIL}} and say which conference and which delegate. Expect to be asked to show that you are that delegate, that delegate’s parent, or staff of that conference, because a request like this cannot be granted to whoever happens to ask.

There is no automated route for this today and no committed response time. These requests are handled by people, by hand.

Changes to this page

The stamp at the top of this page is its version marker. It currently reads “Draft — not yet in force”, because this page has not been reviewed or adopted yet.

When the page changes, that stamp changes with it. No automatic notification is built into the product today. If a change materially widens what the app collects or who can see it, we intend to email conference staff rather than leave them to notice the difference here.