Last updated: 12 November 2026

Privacy policy

DaisBoard is chairing software for Model United Nations (MUN) conferences. Many of the people whose data it holds are school students, often under 18. This policy explains what DaisBoard stores, who is responsible for it, how long it is kept and what rights people have. It is written to be read by students, parents and conference organisers alike.

This is a starting point, not legal advice. Organisers should check it against the law that applies to them, and the platform operator should complete the bracketed details before going live.

Who is responsible

Each conference is the controller of the data it enters about its committees, chairs and delegates. The conference decides what to record, who can see it and when it is deleted. Questions about a conference’s data go to that conference first; each conference can publish a privacy contact in DaisBoard.

The platform operator ([operator’s name and contact address]) runs DaisBoard and processes that data on the conference’s behalf, as a processor. The operator does not use conference data for any purpose of its own, does not sell it, does not show advertising and does not use it to train any AI system. The operator is the controller only of the data needed to run the platform itself: the registration details of each conference (organiser’s name and email, conference name and website) and technical logs.

What DaisBoard stores

• Conference organisers: name, email address, conference name, website and the admin password (stored only as a one-way hash).
• Chairs and secretariat: name, optional title and email, username and a 6-digit PIN (encrypted when the operator has set an encryption key), which committees they chair and what they may do.
• Delegations: the country or organisation represented, and optionally the delegate’s name, school and a reference from the conference’s registration system. Names are optional: a conference can use DaisBoard with countries only.
• Committee proceedings: attendance per session, speeches and their length, points, motions, amendments, resolutions and votes.
• The Committee Tracker: a record of each delegation’s participation drawn from the proceedings above, plus anything chairs log by hand. Chairs can correct it; every correction is recorded with who made it and when.
• Evaluations and awards (confidential): chairs’ scores against the conference’s rubric, their notes, nominations, deliberation notes and confirmed awards.
• Technical data: sign-in sessions (random tokens, stored as hashes), counters of failed sign-ins per network address (to stop password guessing; deleted within a day), and the hosting provider’s request logs.

DaisBoard does not use cookies for tracking or advertising. It sets one cookie to keep a signed-in person signed in. Devices may keep the last state of a chairing desk in the browser’s storage, so the desk keeps working when the internet drops; signing out and clearing the browser removes it.

Why, and on what basis

The data is used only to run the conference’s committees: to chair debate, to keep an accurate record of proceedings and participation, and to help chairs decide awards. Under the GDPR, the conference will usually rely on its legitimate interests in running the conference, or on the agreement with participants (and, where required for minors, their parents or school). Conferences should tell participants about DaisBoard in their own registration information.

Who can see what

• The public and delegates see only the conference’s public page (committee names and what each committee is doing) and the projector, which shows countries or organisations, never students’ names, and never the tracker, evaluations or awards.
• Chairs see the committees they chair. Evaluations and award deliberations are confidential and visible only to chairs the conference has given that right.
• Secretariat members see what the conference allows them to: the overview of proceedings does not include evaluations or deliberations unless they are given that right separately.
• The conference admin sees everything in their conference. Conferences can never see each other’s data.
• The platform operator sees each conference’s registration details and usage counts, and has technical access to the database only to keep the service running, fix faults or meet a legal obligation.

Data is not shared with other products (including ResoBoard) unless a conference connects them, which is not possible yet; when it is, it will be described here first.

Where it is kept, and how it is protected

[Hosting: e.g. the application on Vercel and the database on Turso, in the EU (Frankfurt).] Connections are encrypted (HTTPS). Passwords are hashed; PINs and the owner’s two-step secret are encrypted at rest when the operator sets an encryption key. Every request is checked on the server for who is signed in and what they may do; each conference’s data is separated in every database query. The owner panel requires two-step verification.

How long it is kept

A conference can set a date on which delegates’ names and schools, evaluations, ratings and deliberation notes are deleted automatically, and can delete them at any time. We recommend a date no later than a few weeks after the conference, once awards and certificates are done. A conference’s admin can export all of its data, and the operator deletes everything a conference holds when the conference is deleted. Database backups held by the hosting provider expire within [30] days.

Your rights

Anyone whose data is in DaisBoard can ask the conference for a copy, a correction or deletion, or object to its use; the conference admin can export the data and erase one delegate’s personal data from DaisBoard. Students under 18 can make these requests themselves or through a parent or their school. If a conference doesn’t respond, contact the operator at [contact address]. You can also complain to your data protection authority (in Greece, the Hellenic Data Protection Authority).

Changes

If this policy changes in a way that matters, the date above changes and conference admins are told in DaisBoard.