1. Parties and scope
This agreement is concluded between the
conference organiser ("Controller")
and the operator of MUNpanel ("Processor"):
Sofie Sharaf
c/o IP-Management #12025
Ludwig-Erhard-Str. 18
20459 Hamburg
Germany
info@munpanel.eu
It is concluded when the organiser accepts the
Terms of Service on registration,
and it governs all processing of personal data that the Processor carries out on the
Controller's behalf. Where it conflicts with the Terms of Service, this agreement
prevails for data protection matters.
2. Subject matter, duration, nature and purpose
Subject matter: provision of MUNpanel, a platform for organising and running
Model United Nations conferences.
Nature and purpose: storing and making available conference data so that the
Controller can run its conference — committee and delegate administration,
access-code issuance, speaker lists, voting, messaging, document handling, attendance
records and, where the mobile app is used, push notifications.
Duration: for as long as the Controller holds an account or a conference in
MUNpanel. It ends when the account and all its conferences are deleted.
3. Categories of data and data subjects
Data subjects: conference participants — delegates, chairs, press members,
faculty advisors and crisis team members — and the Controller's own staff who
hold accounts.
Categories of personal data:
— identification data: names, role, committee and country assignment;
— authentication data: individual access codes, and for organiser accounts an
email address and a hashed password;
— content data: messages between participants, submitted documents, amendments
and directives, uploaded files and images;
— participation data: attendance and presence records, speaker list entries,
voting records;
— device data: push notification tokens, where a participant uses the mobile app
and enables notifications.
No special categories of data under Art. 9 GDPR are processed. The Controller
must not enter such data into MUNpanel.
4. Instructions
The Processor processes personal data only on the Controller's documented
instructions. Use of the platform by the Controller, and the settings it chooses,
constitute those instructions. Further instructions may be given in text form to
info@munpanel.eu.
The Processor informs the Controller without delay if, in its opinion, an instruction
infringes data protection law, and may suspend that instruction until it is
confirmed.
The Processor does not transfer data to a third country except as set out in section 7.
5. Confidentiality
Everyone authorised by the Processor to process personal data is bound to
confidentiality, either contractually or by a statutory duty, and that obligation
continues after the engagement ends.
6. Technical and organisational measures (Art. 32)
The Processor maintains at least the following:
Transport encryption. All traffic is served over HTTPS. Session cookies are
marked Secure in production, so they are never sent over an unencrypted
connection.
Encryption at rest. The database and stored files are encrypted at rest by the
hosting provider.
Credential protection. Organiser passwords are stored only as salted hashes
and never in plain text.
Participant access codes are
stored in readable form. This is a deliberate
design decision, not an omission: an organiser has to be able to look a code up again
and re-issue it — on a badge, in a delegate list, to someone who lost theirs
— which a one-way hash would make impossible. The codes are compensated for
instead: each is generated by a cryptographically secure random generator, is unique
across every conference in the system, grants access only to the one seat it belongs
to, and can be replaced by the organiser at any time. Endpoints that accept a code are
rate-limited to 10 attempts per minute and 60 per hour per IP address, so codes cannot
be found by trying.
Controllers should treat access codes like any other credential when distributing
them, and should have unused codes regenerated after a conference ends.
Session protection. Session cookies are HttpOnly, so client-side scripts cannot
read them, and SameSite=Lax, which blocks the standard cross-site request forgery
vector.
Access control. Each role reaches only its own area, enforced server-side on
every request. Conference data is scoped to the conference; an organiser sees only
conferences they own or were invited to.
Abuse protection. Authentication endpoints are rate-limited per IP address.
Request bodies are capped in size before being read into memory.
Data minimisation in notifications. Push notification payloads deliberately
carry no message content, and for private messages not even the sender's name, since a
lock screen is visible to anyone holding the device.
Availability. The database is hosted as a managed instance with automated
backups.
Separation. Production and test environments are separate deployments; the test
environment is additionally shielded by a password gate.
The Processor may change these measures as technology develops, provided the level of
protection is not reduced.
7. Sub-processors
The Controller grants general authorisation for the following sub-processors:
Google Ireland Ltd. (Google Cloud) — hosting of the application and the
database. Processing takes place in the European Union (Belgium and Germany). A data
processing agreement under Art. 28 GDPR is in place.
Expo (650 Industries, Inc.), United States — delivery of push
notifications, and only where a participant uses the mobile app and enables them. The
data transmitted is a device push token and a content-free notification payload. The
transfer is safeguarded by the EU Standard Contractual Clauses.
The Processor informs the Controller in text form before adding or replacing a
sub-processor. The Controller may object on reasonable data protection grounds within
30 days; if the objection cannot be resolved, either party may terminate.
8. Assistance with data subject rights
Requests from data subjects are directed to the Controller, who answers them. Where a
data subject approaches the Processor directly, the Processor forwards the request to
the Controller without delay and does not act on it itself.
The Processor supports the Controller with appropriate technical and organisational
measures in answering such requests, so far as this is possible and reasonable.
Access, correction and deletion of participant data are available to the Controller
directly in the platform.
9. Personal data breaches
The Processor notifies the Controller without undue delay after becoming aware of a
personal data breach affecting the Controller's data, and provides the information the
Controller needs for its own notification under Art. 33 GDPR. The Processor also
assists the Controller with data protection impact assessments and prior consultations
under Art. 35 and 36 GDPR, so far as this is relevant to the processing carried out
here.
10. Deletion and return
The Controller can delete its conferences and its account at any time in the platform.
Deleting a conference deletes its committees, participants, messages, uploads and
records.
On termination of this agreement, the Processor deletes all personal data processed on
the Controller's behalf, unless law requires it to be retained. Backups are deleted in
the course of the regular backup cycle.
11. Evidence and audits
The Processor makes available to the Controller, on request, the information necessary
to demonstrate compliance with Art. 28 GDPR. The Controller may satisfy itself of
compliance, on reasonable notice, during normal business hours and without disrupting
operations — by requesting information, by inspecting documentation, or, where
there is concrete cause, by an on-site inspection.
12. Liability and governing law
Liability follows Art. 82 GDPR. Between the parties, the liability provisions of the
Terms of Service apply in addition.
German law governs this agreement.