A stronger privacy notice built for a global, real-time communication product.

Scope and service operator

This Privacy Policy applies to the Meetzo website, product interfaces, support interactions, and moderation workflows that reference this notice. It is written to explain our current product practices in plain language and to support common transparency expectations that arise under modern privacy laws in multiple regions.

For this version of the service, Meetzo is operated through the contact channels listed in this notice. If a specific legal entity, registered office, or regional representative is designated for public launch or future expansion, this page will be updated before that change takes effect.

How Meetzo is designed

Meetzo is built around lightweight, anonymous real-time communication. That design choice affects privacy: we generally try to minimize persistent user data, avoid unnecessary profile collection, and keep ordinary live interactions ephemeral unless a safety, legal, or operational reason requires us to retain limited records.

• We do not require a public profile to start basic text or video chat.
• We do not intentionally record or archive ordinary live video or audio sessions.
• We do not intentionally store full text chat transcripts by default during ordinary use.
• We may retain limited logs, report details, connection metadata, and support correspondence where needed for operations, safety, fraud prevention, legal compliance, or troubleshooting.

Categories of information we collect

• Connection and device data such as IP-derived region, browser type, device type, app version, timestamps, network quality, and diagnostic event logs.
• Session metadata such as whether you joined text or video chat, how long a session lasted, how often you skipped, and whether a report or enforcement action was triggered.
• Report and moderation information such as the reason selected, any note submitted, a short chat excerpt where available, internal review notes, repeat-abuse signals, and enforcement history tied to a session or identifier.
• Support and rights-request information such as your email address, the request details, follow-up communications, and documents or facts needed to verify and respond to your request.
• Browser-side storage information such as limited cookies, local storage, or session storage that help operate the site, support security, or remember lightweight preferences.

What we do not collect or use by default

• We do not require your real name, photo, or public social profile to use the core anonymous product flow.
• We do not currently sell personal information.
• We do not currently share personal information for cross-context behavioral advertising in the core Meetzo experience.
• We do not intentionally create a long-term reputation score or public-facing identity layer for ordinary users.

Why we process information

• To route real-time messages, signaling data, and matching events so the service can function.
• To keep the product reliable, debug errors, monitor uptime, and improve performance.
• To detect spam, fraud, ban evasion, automation, and abusive behavior.
• To review reports, enforce our Terms and Community Guidelines, and protect users, minors, and the platform.
• To answer support emails, respond to privacy requests, and comply with legal obligations.
• To maintain records that show how we handle security, moderation, and privacy responsibilities.

Lawful bases and regional privacy expectations

Where laws such as the GDPR or UK GDPR apply, Meetzo expects to rely on a limited set of lawful bases depending on the context. These may include performance of a contract or requested service for core matching and communications features, compliance with legal obligations, legitimate interests for platform safety and fraud prevention, and consent where a specific activity requires it.

Where California or similar US state privacy laws apply, this notice is also intended to support transparency around what categories of personal information we process, why we process them, and how eligible users can exercise rights such as access, deletion, correction, or opt-out where relevant.

How matching and live communication work

Text chat messages are routed through our real-time service so they can be delivered to the other participant in the current session. Video chat uses signaling infrastructure to establish a direct peer connection between users wherever possible.

Because these features operate in real time, some technical metadata and connection events are generated even when the content itself is not stored as a permanent transcript or recording.

Cookies, local storage, and similar technologies

Meetzo uses limited browser-side technologies to operate the website, maintain lightweight session continuity, reduce abuse, remember basic preferences, and understand product health. Our Cookie Policy provides more detail.

At present, Meetzo primarily relies on essential or limited diagnostic storage. If we later introduce non-essential analytics, personalization, or advertising technologies in regulated environments, we will add any consent controls required before enabling them.

How we share information

• With infrastructure, hosting, monitoring, communications, or support providers that help us operate Meetzo under appropriate contractual or technical restrictions.
• With moderators, contractors, or trusted reviewers on a need-to-know basis when a safety report, abuse pattern, or legal issue requires investigation.
• With law enforcement, regulators, courts, emergency responders, or other parties when required by law or when reasonably necessary to prevent serious harm, fraud, child exploitation, or security incidents.
• In connection with a merger, financing, acquisition, restructuring, or asset transfer where personal information is relevant and permitted by law.
• With other users only to the limited extent necessary to deliver the real-time communication service you chose to use.

International transfers

Meetzo may be accessed from multiple countries and may rely on providers located in more than one jurisdiction. Where information is transferred internationally, we aim to use reasonable safeguards that fit the sensitivity of the data and the legal regime involved.

If regional law requires additional transfer protections or notices, we will provide them through this policy or related supplemental notices.

Retention and deletion approach

We keep information only as long as reasonably necessary for the purposes described in this notice. That means retention varies based on whether the data relates to basic operations, abuse prevention, security, legal compliance, support, or an unresolved report.

We aim to delete, aggregate, or de-identify information when it is no longer reasonably needed. We may retain a smaller set of records for longer where necessary to investigate repeat abuse, comply with law, defend legal claims, or document platform safety decisions.

Your privacy rights

Depending on where you live, you may have rights to request access to personal information, correction of inaccurate data, deletion, restriction or objection to certain processing, data portability, or information about categories of data collected, used, sold, or shared.

California residents may also have rights related to knowing, deleting, correcting, limiting certain sensitive personal information uses, opting out of sale or sharing where applicable, and non-discrimination for exercising privacy rights. Meetzo does not currently sell or share personal information for targeted advertising in the core product.

Users in the EEA, UK, or similar jurisdictions may also have the right to complain to a supervisory authority if they believe their data has been handled unlawfully.

How to submit a request

• Email privacy@meetzo.app with the subject line that best matches your request, such as access request, deletion request, correction request, or privacy question.
• Describe the request clearly and include enough detail for us to identify the records or session involved.
• If you are submitting a request as an authorized agent, guardian, or representative, identify that status and include any information needed to verify your authority where applicable.
• Do not send more sensitive information than necessary. If we need more information to verify a request, we will ask only for what is reasonably required.

Verification and response timing

We use a verification process that is proportionate to the sensitivity of the request and the information involved. If we cannot reasonably verify a request, we may ask follow-up questions or explain why we cannot complete it.

We aim to respond without undue delay and within the period required by applicable law. Depending on the region and request type, this may be around one month for many EEA or UK rights requests or up to 45 days for certain California rights requests, subject to extensions where law allows and notice is given.

Children and age restrictions

Meetzo is intended for adults and our platform rules require users to be at least 18 years old. We do not design the service for children.

The service is also not intended for children under 13. If we learn that personal information has been collected from a child in a way that requires action under applicable law, we will take steps to delete the data where appropriate and restrict the related access or session.

Automated decision-making and profiling

Meetzo may use simple automated signals for matching, queue management, abuse detection, rate limiting, spam prevention, and report triage. These signals are intended to help operate and protect the platform, not to create a public score or make broad eligibility decisions about your identity.

Where manual review is needed for enforcement, safety, or support, we may supplement automated signals with human evaluation.

Security and incident response

We use reasonable administrative, technical, and organizational safeguards designed to reduce the risk of unauthorized access, misuse, disclosure, or loss. No service can guarantee perfect security, but we work to keep controls proportional to the product and its risks.

If we become aware of a security incident that requires notification under applicable law, we will handle that process in line with the relevant legal requirements and the facts of the incident.

Changes and contact

We may update this Privacy Policy as the service evolves, our practices change, or law requires additional disclosures. When we make material changes, we will update the policy date and publish the revised version on this page.

For privacy questions or requests, contact privacy@meetzo.app. For general support, contact support@meetzo.app. For urgent abuse or safety concerns, contact abuse@meetzo.app.