Privacy notice
Last reviewed: 1 May 2026.
What this build collects
The static build of Team2meet does not run a server. It does not collect personal data, does not use third-party analytics, and does not set tracking cookies.
- Browser storage: your name, your last-used time zone, and a list of meetings you have created or visited are stored locally in your own browser using
localStorage. - Share links: the meeting name, dates, time-window, organiser name and participant responses are encoded inside the share URL after the
#character. URL fragments are not transmitted to web servers. - Fonts: Google Fonts is used to load the DM Sans typeface. Google may log requests for that font; see the Google privacy policy. You can self-host the font to avoid this.
Your rights
Because no personal data is held on a server in this build, there is no remote record to access, correct, export or delete. You can clear all locally stored data by clearing your browser's site data for this domain.
If you deploy with a backend
If you (or your organisation) extend Team2meet with a backend such as PocketBase, Supabase or a PHP and MySQL service, you become the data controller and must publish your own privacy notice covering the data you collect and process.
Contact
For questions, contact FUSB Lab at Leeds Beckett University via the lab page.