Privacy notice

Last reviewed: 3 May 2026. Data controller: Hasnova Technologies Limited, United Kingdom.

Summary

Team2meet does not run any server-side data processing in this static build. There are no accounts, no analytics, no advertising, no tracking, and no third-party data brokers. The information you enter is stored only in your own browser and inside the share URL you generate.

Cookies and similar storage

Team2meet does not set any HTTP cookies. We use a small amount of localStorage in your browser, which falls under regulation 6 of the Privacy and Electronic Communications Regulations (PECR), enforced by the Information Commissioner's Office. We ask for your consent before writing anything beyond what is strictly necessary.

Storage key Purpose Lifetime Category
t2m_consent_v1 Records your accept or reject choice for the banner. Until cleared Strictly necessary
t2m_user_name Remembers your name so you do not retype it. Until cleared Preference (consent required)
t2m_event_history Stores a list of meetings you created or visited so they appear on the home page. Until cleared Preference (consent required)
t2m_timezone Remembers your last-used display time zone. Until cleared Preference (consent required)
t2m_draft_dates, t2m_draft_name Auto-saves your in-progress meeting so a refresh does not lose work. Cleared on link generation Preference (consent required)
t2m_theme_mode, t2m_theme_accent Records your light/dark/system mode and accent colour selected from the theme picker. Until cleared Strictly necessary (set only by your direct interaction with the theme picker)

You can withdraw consent at any time by clearing site data in your browser, or by visiting this page in a private or incognito window.

What is stored where

  • 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. These are written only after you accept the consent banner.
  • 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 never transmitted to web servers (per the W3C URL Living Standard, https://url.spec.whatwg.org/). Anyone you send the link to can read its contents, so treat the link as you would treat the meeting itself.
  • 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.
  • Hosting: the static files are served from Hostinger. Their server logs may record IP addresses and user-agent strings as part of normal web hosting; see the Hostinger privacy policy.

Lawful basis

Where local storage is used for preferences, the lawful basis is your consent (UK GDPR Article 6(1)(a)). Strictly necessary storage (your consent choice itself) does not require consent under PECR regulation 6(4)(b).

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 believe Hasnova Technologies Limited is processing your data improperly, you have the right to lodge a complaint with the Information Commissioner's Office at ico.org.uk.

Server-side meeting storage

Where the optional backend has been enabled by the operator, meeting records (meeting name, organiser name, candidate dates and times, anchor time zone, and each participant's name and ticked availability) are stored in a MariaDB database hosted by Hostinger International Ltd on the same shared hosting account that serves this website. Hostinger acts as a processor on behalf of Hasnova Technologies Limited, which remains the sole data controller.

The lawful basis is legitimate interest (UK GDPR Article 6(1)(f)): organising a shared meeting is impossible without recording the participants' availability, and the data collected is the minimum required to compute a heatmap of overlap. No marketing, profiling, analytics or cross-site tracking is performed on this data.

Records are retained for as long as the meeting link is in active use plus an automatic clean-up window of 90 days from the last update. Anyone can request earlier deletion by contacting the organiser or Hasnova Technologies Limited directly.

Where the backend is not configured, the site falls back to URL-fragment storage as described above and no data is sent to the server at all.

Third-party share buttons

The Microsoft Teams, Outlook (web), WhatsApp and Google Calendar buttons each open the respective third party's website in a new tab pre-filled with the meeting link and a short message. Clicking a share button transmits the meeting URL to that third party in the form of a query string in their address bar, which their service may log according to its own privacy policy. None of these services is contacted unless and until the user clicks the corresponding button.

Contact

For questions or to exercise your rights, contact Hasnova Technologies Limited via the contact details published on the company's main website. This privacy notice may be updated; the date at the top of the page indicates the latest review.