Privacy notice

Saved in your browser

MUN Chair uses local storage to keep your meeting state and unfinished work between visits. This includes local speaker queues, motion and vote drafts, personal notes, sound and font preferences, and the notes window layout.

Your collaboration identity is also saved locally: your display name, role, room and session identifiers, a browser identifier, and a token used to restore access. A host’s browser can save the room PIN so the host can view it again. Someone with access to the same browser profile may be able to reopen this information.

Shared with your meeting room

When you create or join a collaboration room, Supabase stores the room’s meeting and committee names, chair information, delegate names and attendance, meeting status, and completed motion groups and voting results. Other members of that room can see shared records, member display names, roles, and online status.

The service also stores membership and session information, browser identifiers, activity timestamps, and credentials needed to control room access. Joining uses a Meeting ID, PIN, and display name; no separate email account is required.

Unfinished motion details remain local until they are formally submitted. A small room status indicator can identify the motion being handled, its operator, and its start time. Personal notes and sound, font, and window preferences are not included in room synchronization.

Services that make the app work

Vercel hosts the website, and Supabase provides the collaboration backend. Requests to these services involve connection information such as your IP address and browser or request metadata; the providers may retain operational and security logs.

The app also loads fonts from Google Fonts, which sends a request from your browser to Google. This privacy page uses fonts available on your device.

Provider information: Vercel, Supabase, and Google.

Visitor statistics

The production app uses Vercel Web Analytics to measure aggregate visitors, page views, referral sources, approximate location, and browser and device types. It does not use cookies. Page opens and refreshes are counted; actions inside a meeting are not tracked as separate events.

We remove query parameters and URL fragments from the page URL before it is sent. Delegate names, room PINs, meeting records, document contents, and votes are not sent to visitor analytics. Development and preview sites are excluded. See Vercel’s Web Analytics privacy information for how the service processes request metadata.

Retention, removal, and your choices

• Local copies: Use your browser’s settings to clear this site’s stored data. This removes local drafts, notes, preferences, saved PINs, and recovery credentials. Export any records you need first; clearing data may prevent automatic recovery of your existing member identity.
• Cloud records: Leaving a room, resetting the app, or clearing browser storage does not delete the room’s records from Supabase. The current app has no self-service cloud deletion option or published automatic deletion period. Contact us to request review or removal of your data.
• Shared copies: Other participants may save or export meeting records. Removing data from this service does not remove copies they already hold.