Privacy Policy

This describes what Let's Mingle, operated by LetsMingle, does with information about you. It is short because the product collects very little, and specific because a policy that could describe any product describes nothing.

The short version

• Google accounts are optional for visitors and required for creators.We use secure cookies for sign-in and guest browser identity. We do not receive your Google password.
• Your audio and video are never recorded. They pass through and are gone.
• We keep a log of who was present in a space and when, with the display name you typed.
• We use Google Analytics to understand visits and usage across the site. It uses cookies and collects browser, device, and approximate location information.

What we collect

Your display name

For guests, whatever you type on the way in, up to 64 characters. It is not verified, and you can use a different one every time. It is shown to everyone in the space, and it is stored with the presence records described below.

What the room knows while you are in it

For as long as a space is live it holds, for each person: an id derived from your account or guest browser identity for this space, the display name, whether you are available, in focus or away, whether your camera and microphone are on or off, and which conversation you are in. It also holds conversation names, host announcements, and the last twenty messages a host has sent to the room.

Room state is stored so the space survives between visits. Memberships, admin roles, bans, settings and deletion status persist even when nobody is present.

Presence records

So we can tell whether the product is doing anything useful, we record six kinds of event: joining a space, leaving it, starting a conversation, joining one, leaving one, and a failure to reach the media service. Each row holds the time, the space id, the visit id, the display name, the event kind, and the conversation id.

No IP address, no user agent, no location, no device information is attached to these — the request is never read for them. Nothing about what was said, and no audio or video, is recorded.

These records are kept indefinitely. They are used to understand how much time people spend with somebody else present, which is the one number that says whether the idea works. They are read through an operator dashboard that requires a separately authorized Google account; they are not visible to other participants, sold, or shared with anyone.

The demo room and load-testing spaces are excluded from these presence records. Google Analytics runs on all pages, including demo and load-test pages.

Operational activity monitoring

The site operator has a restricted dashboard of spaces, host email addresses, and usage metrics. A read-only activity view shows connected participants’ names, group membership, availability, camera and microphone on/off states, and reported media errors. Viewing does not add the operator to the room or produce a participant notification. It does not provide access to audio, video, profile images, messages, or announcements.

We keep a private record of operator monitoring access. The space directory and monitoring access records are retained indefinitely, like the presence records above. Space hosts do not gain access to the site-wide dashboard.

Accounts, history and moderation

When you sign in, we store your Google account ID, verified email, name and profile photo URL. Your Google name and photo are visible in joined spaces; participant emails are visible only to space admins. Google sign-in identifies your account, not a verified legal identity.

We store signed-in users' joined spaces and last visit times for cross-device history. We do not import browser history, and the demo is excluded. Removing a saved space removes that history entry, not the space or its moderation records.

Each space retains members, admin invitations, bans and its most recent 1,000 admin actions. Account bans persist across devices; guest bans use a browser identity cookie. Deleting a space leaves a permanent deletion marker and does not erase account or presence records.

The sign-in cookie lasts eight hours; the guest identity cookie lasts up to one year. Account and moderation records are retained until removed through the relevant controls or a support request.

Kept in your browser

The app stores a few things locally so it can remember you between visits. These live in your browser and clearing site data removes them:

• your session for each space you have entered, including your display name;
• a note that you deliberately stepped out of a space, so a reload does not walk you back in;
• a private tally of how often you have ended up in conversation with each other person, up to 200 people per space. It is used only to order the room so the people you actually talk to appear first. It is never sent to us and nobody else can see it.

Audio and video

Nothing records them. There is no recording feature, no transcription, no analysis of what you say or how you look, and no frame or sample is written to storage anywhere in the service.

Media is relayed rather than sent directly between browsers, which means it passes through Cloudflare’s real-time infrastructure on its way to the other people in your conversation. Setting up a connection also involves exchanging network information about your device — including its local and public IP addresses — with our server and Cloudflare; this is how video calling works everywhere, and we pass it through without storing it.

Only people in the same conversation as you can receive your microphone. That is enforced by the server on every request, not by the page you are looking at.

Who else is involved

Cloudflare hosts the service, stores its data, and relays the audio and video. As our infrastructure provider they also log ordinary request metadata, including IP addresses, in the way any web host does.

Google Analytics measures page visits and site interactions using cookies and browser and device information. Google processes IP addresses to derive approximate location; Google Analytics does not log or store those IP addresses. See Google’s data practices. Fonts are served from our own domain, so your browser makes no request to a font provider.

Google provides sign-in and profile information. The Google sign-in component contacts Google; profile photos may also load from Google.

Security, honestly stated

Anyone with a space link can request entry. Admins can require Google sign-in and ban accounts or guest browser identities. Guest bans can be bypassed by clearing site data. Keep private space links within your intended group.

Your session is a signed token with a twelve-hour life, carrying your visit id, the space, your display name and, when signed in, your account profile. Current permissions are checked on the server. It is signed rather than encrypted, so anyone who obtains the token can read the display name inside it.

Children

The service is not intended for children under 13, and we do not knowingly collect their information. If you believe a child has used it, write to us and we will remove what we can.

Your choices

You can leave a space at any time, use a different display name, keep your camera off, and clear your browser’s site data to remove everything stored locally.

There is no self-service way to delete or export your presence records today. To request either, email hello@letsmingle.io with the space and the display name you used, or the Google email you signed in with. We will verify the request and handle it manually.

Where the service is operated

LetsMingle is based in the United States, and the service runs on infrastructure distributed worldwide. If you use it from outside the United States, your information is processed there and in whichever region serves you.

Changes

If this policy changes, the date at the top changes with it. Material changes to what we collect will be announced rather than quietly edited in.

Contact

hello@letsmingle.io. See also the terms and the help page.