Mello

Privacy Policy

Last updated: October 24, 2026. Version 4.

This Policy explains how mello collects, uses, discloses, and retains information when you use our app, website, event-sharing pages, support channels, and related services. mello is operated by MELLOMEET LLC, a Utah limited liability company, 2505 S River Rd Unit 2 #224, Saint George, UT 84790.

Information we collect

Account and device data. Email address, authentication and session data, account identifiers, age eligibility, notification preferences, push tokens, device platform, security events, and support communications.

Profile data. Display name, username, full birthdate, gender and event eligibility settings, neighborhood, biography, prompts, interests, photos, verification status, followers, connections, and other information you choose to add.

Location and travel data. With permission, mello processes precise coordinates to suggest your location and find nearby activities. We store coordinates associated with your home area, search area, events, and trips. We also store destination labels and travel dates. We generally display a neighborhood, city, approximate area, or distance instead of your precise home coordinates.

Events and social activity. Events you create, save, join, attend, cancel, or host; venue details; attendee and waitlist status; check-ins; follows; blocks; connections; reviews; search radius; and event costs or attendance requirements.

Messages and media. Event, direct, and crew messages, replies, reactions, photos, voice clips, delivery state, and related metadata, and updates an organizer sends to the ticket holders of its events. Some content may be cached on your device for performance and offline display.

Safety and moderation data. Reports, categories, account and content references, moderation actions, blocks, appeals or support correspondence, and a protected snapshot of reported content where needed to review a concern or preserve evidence.

Payments. Stripe customer, payment-method, and payment-intent identifiers, transaction state, no-show charge information, and limited billing details. Payment-card details are submitted directly to Stripe; mello does not store full card numbers.

Tickets and organizers. When you buy a ticket, we collect the order, tier, quantity, price, service fee, tax, promo code, refund policy and house rules you accepted and when, ticket status, transfer and check-in records, and the event venue address used to calculate tax. Stripe separately collects device and payment information, including IP address, to process payments and prevent fraud, under its own privacy policy. The organizer and its door staff can see your display name, ticket number, tier, and check-in status, and the organizer can export a guest list of those admission fields. When door staff scan your ticket, they also see your profile photo, if you have one, the event's age rule, and whether the event requires photo ID. At an event that requires photo ID, door staff check your ID against you and may also compare it with the display name and profile photo on your ticket before admitting you. That comparison is made by a person; mello does not use face recognition and does not see, copy, or store your ID or anything on it. When the door's scanner is online, we record each ID check: the ticket, the staff member and device, the time, and whether you were admitted, with no reason and nothing from your ID. We delete these ID check records within 30 days after they are one year old, including after account deletion. If you were admitted, we keep the check-in record with your other ticket records, but once the ID check record is deleted it no longer shows that an ID check took place. Organizers can send updates to ticket holders and host a chat for ticket holders. If you apply as an organizer, we collect your organization's legal name and team, and Stripe collects the identity, tax, and bank information needed for payouts under its own terms. We keep order, tax, refund, dispute, and acceptance records after account deletion for as long as tax, accounting, and chargeback rules require.

Agreements you accept. When you accept our Terms, Privacy Policy, or Organizer Terms, we record the document and version, the time, your device platform and app version, and the IP address and user agent of the request. An organizer acceptance also records the organization and the name the signer typed. We keep these records after account deletion to show what you agreed to, and 7 years after your account closes we remove the IP address and user agent from them. When you confirm the rules for a paid event, we record the statement you confirmed, the event details it covered, your name and verification status, your device platform and app version, and the IP address and user agent of the request. We keep these confirmations, including after account deletion, for as long as the event's sales, refunds, chargebacks, or a claim about the event could require them, and 7 years after the event ends we remove the IP address and user agent from them.

Bug reports. When you send a report through Report a bug, we collect what you write, a screenshot if you add one, your account, and the time. The app attaches your device platform, operating system version, device model, app version and build number, the identifier of the app update you are running, and the screen you were on, recorded without the identifier of any event, chat, or person shown on it. It does not attach your location, IP address, or a device identifier, and we remove location and other photo details from a screenshot before we store it. A screenshot can show other people's names, photos, or messages, so crop out anything the report does not need. Only mello administrators can read bug reports and view their screenshots.

Website and operational data. Requests, IP-derived security information, browser and device characteristics, error logs, function and delivery logs, and interactions needed to protect and operate the service. We do not currently use your information to build third-party advertising profiles or sell personal information.

Where information comes from

We receive information from you, your device permissions, your activity in mello, hosts and members you interact with, service providers acting for us, and safety or support reports. Event hosts may provide attendance information. Stripe provides payment and identity-verification status. Google location services may return place and geocoding results from searches or coordinates you submit.

How information is shared and displayed

Member profiles. Signed-in members may see profile fields such as display name, username, photos, approximate area, interests, prompts, gender or event-eligibility information where relevant, verification badge, and social connections.

Events. Hosts and attendees can see information needed to coordinate an event. Exact venue details are restricted based on event status and eligibility. Hosts can see attendee and check-in information.

Organizer events. On an event run by an organizer, the event's group chat is open to its ticket holders. The organizer's staff can read and post in it only when they hold a ticket on their own account. Updates an organizer sends to ticket holders are delivered to them as notifications.

Travel discovery. Travel destinations, date ranges, and approximate presence may be used to connect travelers and locals in a selected area.

Public event links. A shared event page may be visible without signing in and may show the event title, description, approximate area, cover image, host display name, attendee count, and a limited preview of attendee first names and avatars. Certain restricted events suppress attendee previews.

Chats. Members of an event, direct conversation, or crew can see content shared in that conversation. Moderators may access reported content when necessary to investigate safety concerns. Chat media is currently delivered through link-addressed files. Conversation members receive those links, and anyone who obtains a valid link may be able to access the file until it is removed.

Do not post information you do not want the relevant audience to see. Blocking limits future interaction but may not remove content already shared, retained safety evidence, or information another person saved outside mello.

Identity verification and biometric information

Identity verification is optional unless a particular feature or event requires it. If you choose it, Stripe Identity collects and processes a government identity document, a selfie, and biometric information derived from those materials to compare identity and liveness. Stripe checks whether the ID document appears genuine and whether the selfie matches the person pictured on it, and the result gives your account a verification signal. It does not confirm your name or your age to mello: mello does not receive the name, birthdate, or other details printed on your ID.

mello does not receive your raw government-ID image, selfie, or facial geometry. We do store your consent record, which includes the notice version, a hash of the notice text you were shown, the time, your device platform and app version, and the IP address and user agent of the request; your verification attempt and status; a Stripe verification-session identifier; failure information where applicable; and relevant timestamps. Stripe processes the underlying verification materials under its own privacy terms and our service arrangement.

You may withdraw biometric consent in Account settings. We promptly return the account to an unverified state and request redaction from Stripe. Provider redaction is asynchronous and may remain pending while Stripe completes it. We retain the minimum session and consent evidence needed to verify completion, handle retries, comply with law, and prevent an unconfirmed deletion from being described as complete.

When your check finishes, or if you withdraw consent or delete your account, mello instructs Stripe to permanently delete the ID image, selfie, and biometric information collected on our behalf, which Stripe completes within a few days. In every case they are destroyed no later than three years after your last interaction with mello, unless a shorter period is required by law. We do not sell, lease, trade, or profit from biometric identifiers or biometric information.

How we use information

  • provide accounts, discovery, maps, trips, events, chats, reminders, notifications, support, verification, and payment features;
  • personalize nearby results and enforce event eligibility, capacity, privacy, and safety controls;
  • authenticate users, prevent abuse, debug failures, secure infrastructure, and maintain service reliability;
  • investigate and fix the problems you report through Report a bug;
  • review reports, enforce our Terms, preserve evidence, protect members, and comply with valid legal obligations;
  • process transactions, ticket sales, sales tax, organizer payouts, saved payment methods, attendance outcomes, refunds, disputes, and no-show charges where expressly authorized; and
  • measure and improve mello using operational, aggregated, or de-identified information where practical.

Service providers and disclosures

We disclose information to providers only as needed for their services, security, legal compliance, and our instructions. Current categories include:

  • Supabase for authentication, databases, storage, realtime features, and server functions;
  • Stripe for identity verification, saved payment methods, payment processing, ticket payments, sales tax calculation, and organizer payouts;
  • Expo, Apple, and Google for app delivery, updates, device notifications, and platform services;
  • Google Maps Platform for place search, geocoding, and location labels;
  • Resend for service email; and
  • Google Fonts and hosting providers for website delivery and typography.

We may also disclose information with your direction; to event participants as described above; to professional advisers and transaction counterparties under appropriate duties; to protect rights, safety, and security; or when required by valid legal process. If ownership of mello changes, information may transfer subject to this Policy and applicable law.

Retention, withdrawal, and account deletion

We retain information for the shortest period reasonably necessary for the purposes described here, considering account activity, safety, fraud, payment disputes, backups, provider deletion status, and legal duties. Profile, event, social, and active message data generally remain while your account or the relevant feature is active. Device caches remain until cleared, expired, reinstalled, or removed through account controls.

Deleting your account initiates removal of your profile, owned media, account data, and Stripe Identity records. Some deletion work may complete asynchronously or require a retry if a provider cannot confirm deletion. Stripe payment records, transaction records, reported-content evidence, security logs, and legal records may be retained by us or a provider for chargebacks, fraud prevention, safety, accounting, legal claims, or mandatory retention, then deleted or de-identified when those purposes expire. Records of the agreements you accepted are kept as described under Agreements you accept.

Our daily cleanup deletes a bug report's screenshot once the report is 90 days old, and the report itself once it is one year old. Deleting your account deletes your bug reports and their screenshots. In each case, we keep a report longer only when we must meet a legal duty or preserve evidence of serious harm, such as apparent child sexual abuse material or a credible threat that we report to the authorities. A report kept this way, with any screenshot it still has and a record of which account sent it, stays only until that need ends. Our daily cleanup then deletes it once its normal deletion time has passed, or in the next cleanup if the account that sent it has already been deleted.

Backups and provider systems may take additional time to cycle. We may retain de-identified information that cannot reasonably be linked back to you.

Your choices and privacy rights

You can edit profile information, adjust notification settings, manage location permission, block members, withdraw biometric consent, and request account deletion in the app. Depending on where you live, you may also have rights to know, access, correct, delete, or obtain a copy of personal information; opt out of certain sale, sharing, targeted advertising, or profiling; limit certain sensitive-data uses; withdraw consent; and appeal a denied request.

mello does not currently sell personal information or share it for cross-context behavioral advertising. To exercise a right, email [email protected]. We may verify your identity and authority before acting. Authorized agents may submit requests where law allows. We will not discriminate against you for exercising a privacy right.

Security and international processing

We use administrative, technical, and organizational safeguards designed for the sensitivity of the information involved, including access controls and protected service boundaries. No system is completely secure, and we cannot guarantee that unauthorized access or loss will never occur. Providers may process information in the United States and other countries where they operate, subject to applicable transfer requirements.

Children

mello is for adults age 18 and older and is not directed to children. We do not knowingly allow anyone under 18 to create an account. If you believe a child provided information to mello, contact us so we can investigate and take appropriate action. See our Child Safety Standards.

Changes to this Policy

We may update this Policy as mello evolves. We will change the date above and provide additional notice or obtain consent where applicable law requires it. Material changes apply prospectively unless we clearly explain otherwise.

Contact us

Questions or privacy requests may be sent to [email protected] or by mail to MELLOMEET LLC, 2505 S River Rd Unit 2 #224, Saint George, UT 84790. Child-safety concerns may also be sent to [email protected].