Private by design, honest about the limits.

What happens during a call

Video and audio travel directly between the two participants through WebRTC whenever the network allows. GleMeet does not continuously record calls. A participant can still use their own device to capture a call, so do not share private information.

Identity and operational records

GleMeet uses a private browser cookie to recognize guest sessions. Signed-in visitors may instead use their platform account identifier. Other participants do not see these identifiers. GleMeet stores matchmaking state, session identifiers, connection signaling, blocks, reports, bans, and moderation audit records needed to operate and protect the service. Clearing your browser data can reset a guest session, so guest restrictions are less durable than account-based restrictions.

Reports and screenshot evidence

When you submit a report, GleMeet attempts to capture one still frame from the reported participant’s remote video. That frame, the report reason, optional note, session identifiers, and timestamps may be stored temporarily for safety review. Report evidence is available only through the authenticated owner interface and is not published at a guessable public URL.

Text chat

Current-match text messages travel through the same peer-to-peer WebRTC connection. GleMeet does not store them in the app database, and they disappear from the interface when the match ends.

Moderator access

Authorized moderators can review reports, protected screenshot evidence, active session records, and moderation history. The current peer-to-peer beta does not let moderators silently join a live call. If that capability is introduced later, this notice and the in-product disclosure must be updated first.

Website analytics

GleMeet uses Google Analytics to understand page visits and actions such as starting, connecting, skipping, ending, reporting, and sharing. Our product events do not include video, audio, text messages, evidence, or guest/session identifiers. Analytics may use browser cookies and can be blocked by your browser. Ad personalization and Google signals are disabled in our tag configuration.

Optional AI conversations

If an AI Companion is enabled, it is clearly labeled as fictional AI and is separate from human video chat. Only messages you type into that AI interface are sent to the configured AI provider to generate a response. Your camera, microphone, human text chat, and report evidence are not sent to the AI. Messages disappear from the interface when you close the AI conversation. The provider’s data policies also apply; do not type sensitive personal information.

Who operates GleMeet

GleMeet is an independent online service operated from Uttar Pradesh, India. For any privacy, safety or legal matter, contact support@glemeet.com.

How long we keep data

Your choices and rights

You can ask to access, correct or delete data linked to your guest session, or withdraw consent, by emailing support@glemeet.com. Include your guest or session ID if you have one. We may keep data where the law requires it, or where it is needed to enforce safety measures such as bans. We aim to reply within 7 days.

Scheduled sessions

Some sessions may be organised on a GleMeet community server on Discord. Anything you share on Discord is handled by Discord under its own policies. GleMeet does not import Discord data into the service. Matches during scheduled sessions are made between participants who chose to join that session.

Contact & grievances

Contact for general, privacy and safety matters: support@glemeet.com

Grievance Officer: Prashant Kanaujia, support@glemeet.com

How to complain: include what happened, the date and time, your guest or session ID if you have it, and any report ID.

Response times:

Appeals: if you are not satisfied with a decision, you may appeal to the Grievance Appellate Committee (gac.gov.in) within 30 days.

Emergencies: if anyone is in immediate danger, contact local emergency services (112 in India).