LOBBI

Privacy Policy

Effective date: 4 October 2026

1. Who we are

This policy explains how Lobbi (“Lobbi”, “we”, “us”) handles personal data across our website at mylobbi.link and our app at in.mylobbi.link.

For privacy questions or requests, email [email protected].

2. What Lobbi is

Lobbi provides branded virtual waiting rooms for video calls. Hosts (typically professionals or teams) use the Lobbi app at in.mylobbi.link to design lobbies, set a call link, and admit guests. Guests open a public lobby link, check in, and wait until the host lets them into the underlying meeting (Zoom, Google Meet, Microsoft Teams, or another URL the host provides).

Lobbi is the doorway to your call — it does not replace your meeting provider.

3. Roles and responsibilities

Host account data. For information about people who sign up and use the Lobbi app, Lobbi is the data controller.

Guest check-in data. When a guest uses a lobby, the host decides who receives the link and why. The host is the data controller for guest personal data collected during check-in. Lobbi acts as a data processor, processing guest data on the host’s instructions to operate the waiting room (check-in, notifications, admit flow, and basic analytics for the host).

If you are a guest with questions about how your data is used, contact the host who invited you. You may also contact us at [email protected] and we will assist where we can.

4. Data we collect — hosts

When you create an account and use Lobbi, we may collect:

5. Data we collect — guests

When a guest opens a lobby link and checks in, we may collect:

Guest lobbies are publicly reachable by anyone with the link. Do not enter sensitive information unless you trust the host who sent you the link.

6. How we use data

We use personal data to:

We do not sell personal data. We email hosts about their account and lobbies; we do not send marketing email to guests who only checked in to a lobby.

Where applicable, we rely on:

8. Sharing and sub-processors

We use trusted providers to run Lobbi. They process data only on our instructions:

We may disclose data if required by law, to protect rights and safety, or in connection with a merger or acquisition (with notice where appropriate).

9. Slack integration

Connecting Slack is optional and off unless a host turns it on. When a host connects it, Lobbi posts check-in notifications into one Slack channel chosen during installation, and teammates can admit, delay, or remove a guest from that message.

What Lobbi receives from Slack

Lobbi requests a single Slack permission, incoming-webhook. We cannot read messages, files, channel lists, or member profiles in your workspace, and we cannot post anywhere except the channel chosen at install. We do not use any Slack data to train machine learning models.

What Lobbi sends to Slack

Each notification contains the guest’s name (or “A guest” if they gave none), the lobby name, and — once a teammate admits the guest — the meeting link. Guest email addresses, phone numbers, and answers to custom check-in questions are not sent to Slack.

How long we keep it, and how to delete it

The webhook URL and the workspace, channel, and user IDs are kept for as long as the integration stays connected. When a host disconnects Slack in Lobbi, or removes Lobbi from the Slack workspace, we delete the stored credentials and mark the connection revoked.

Notifications already delivered live in your own Slack workspace and follow your Slack retention settings rather than ours, so deleting those messages is done in Slack. To remove everything on our side, disconnect from Integrations in Lobbi, or email [email protected] and we will do it for you.

10. Google Meet integration

Connecting Google Meet is optional and off unless a host turns it on from Integrations in Lobbi. When connected, Lobbi can create a Google Meet link for a lobby, so admitted guests are sent straight into that meeting.

What Lobbi can access

Lobbi requests a single Google permission, https://www.googleapis.com/auth/meetings.space.created. It lets Lobbi create new Google Meet meeting spaces and manage only the meeting spaces Lobbi itself created. Lobbi cannot read your Gmail, Google Calendar, contacts, Google Drive, or any meeting, recording, or transcript that Lobbi did not create.

What Lobbi stores

How Lobbi uses and shares Google data

Google user data is used only to create and show Google Meet links for your lobbies. The meeting link is shown to guests you admit to that lobby, and teammates in your Lobbi workspace can use the connection to create meeting links for the workspace’s lobbies. Teammates and guests never see your Google tokens.

We do not sell Google user data, use it for advertising, or use it to develop, improve, or train generalised artificial intelligence or machine learning models. No person at Lobbi reads Google user data unless you ask us to (for example for support), it is needed for security reasons, or the law requires it.

Lobbi’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How long we keep it, and how to delete it

Tokens are kept only while Google Meet stays connected. When a host disconnects Google Meet in Lobbi, we revoke the tokens with Google and delete them from our systems. You can also remove Lobbi’s access at any time from your Google Account permissions page; the stored tokens stop working immediately, and we delete them on request. Meeting links stay with the lobby they were created for until the lobby is deleted or you ask us to remove them at [email protected].

11. How we protect your data

We use the following technical and organisational measures to protect personal data, including sensitive data such as Google OAuth tokens and other integration credentials:

No method of transmission or storage is completely secure, but we work to protect your data and review these measures as Lobbi evolves. To report a security concern, email [email protected].

12. International transfers

Our infrastructure providers may process data in countries outside your own. Our Supabase database, authentication, and file storage are hosted in the United States (us-west-1). Cloudflare serves our site and API from its global network, so requests are handled at the location nearest to the visitor. Resend, PostHog, Google, and Slack each process data on their own infrastructure as described in their privacy policies. Where required, we use appropriate safeguards such as standard contractual clauses.

13. Retention

We keep account and lobby data while your account is active and as needed to provide the service. Session and check-in records are retained for host analytics and operational purposes. We delete or anonymise data when it is no longer needed, unless we must keep it for legal reasons.

There is no self-service account deletion in the app yet. To request deletion of your account or data, email [email protected].

14. Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or port your personal data, and to object to or withdraw consent for certain processing.

Hosts can update profile and workspace details in Settings. For other requests, contact [email protected]. We respond within the timeframes required by applicable law. You may also complain to your local data protection authority.

15. Children

Lobbi is not directed at children under 16. We do not knowingly collect personal data from children. If you believe a child has provided data, contact us and we will delete it.

16. Beta and pricing

Lobbi is currently offered as a free beta. We may introduce paid plans later; we will email account holders before any change that affects billing. Beta features and data practices may evolve as the product develops.

17. Changes

We may update this policy. We will post the new effective date on this page and, for material changes, notify account holders by email where appropriate. Continued use after changes means you accept the updated policy.

18. Contact

Email: [email protected]
Website: mylobbi.link