mbio Connect privacy

Effective September 3, 2026

The browser extension

On the ticketing sites listed in its permissions, the mbio Connect extension reads the current page URL and the public event details that the page publishes for search engines: title, date, venue, city, and event category. It keeps the current event per tab in Chrome session storage so the popup can show the correct queue, and sends a derived event fingerprint to the mbio Connect API over HTTPS for the anonymous queue lookup. It does not read prices, seat maps, purchases, messages, passwords, or unrelated page content; monitor sites outside the listed ticketing sites; or build or sell a browsing history.

Account linking and one-tap joins

Account linking is optional. If you choose it, the extension stores a pairing credential, a short-lived contact-verification token, and your mbio profile details (verified contact information, first name, age band, and gender) in Chrome local storage. This lets the extension refresh your sign-in and offer one-tap joins. When you tap join, the extension sends those profile details, your selected match mode, and the current event details and page URL to the mbio Connect API over HTTPS. The extension never joins a queue without your action.

The service

When you join a match queue we store your verified contact information, first name, age band, gender, match preferences, and the event you selected to make your match. Other fans never see your name until you both accept a match. We do not sell user data, use it for advertising, use it for purposes unrelated to mbio Connect, or use it to determine creditworthiness or for lending. We do not collect government ID documents, and queue sizes are shown only as rounded ranges.

Contact

Questions or deletion requests: email hello@wgodw.com and we'll take care of it.