Privacy Policy

MingleTrivia is an iOS trivia game for groups, in the same room or apart. This Privacy Policy explains what information MingleTrivia collects, why we collect it, who receives it, how long we keep it, and the choices available to you when you visit mingletrivia.com, join the waitlist, or use the MingleTrivia app (together, the “Service”).

MingleTrivia is operated by Kyle Borg in the United States. Questions or requests can be sent to privacy@mingletrivia.com. This policy is part of our Terms of Service.

1. Information we collect

Information you provide

  • Waitlist details. If you join the waitlist, we collect the name and email address you submit.
  • Game-session details. The app does not require a MingleTrivia account. A host or guest chooses a display name for a game. That name, an app-generated player identifier, room membership, and game state are visible to the people in that game and may be carried by the selected game transport.
  • Optional player photo. You may take a photo for recognition in the lobby and scoreboard. You can skip it and use initials instead. The app does not use face tracking, facial geometry, facial recognition, or other biometric identifiers.
  • Apple purchases. Apple processes MingleTrivia Host subscriptions through StoreKit. The app reads verified entitlement and transaction status on your device to provide hosting. This release does not send a payment card, receipt, or StoreKit transaction record to MingleTrivia’s API; Apple does not provide us with your card or bank details.
  • Terms acceptance record. Before someone hosts, starts a solo game, or buys a Host subscription, the app records the Terms version, agreement time, presentation source, and a random installation identifier in app-local storage. It does not create a MingleTrivia account and is not shown to guests.
  • Messages to us. If you contact support, privacy, security, accessibility, or licensing, we receive the information you include in that message.

Information collected through operation of the Service

  • Browser players. Browser play collects your display name and random player and device identifiers to join a game hosted in the iPhone or iPad app. Your name, room code, reconnect credential and pending timer or answer are saved in browser local storage so a refresh can restore your seat and score. Tap Leave game or Forget saved seat to remove them, or clear this site's browser data. Room events and scores are held temporarily in the cloud relay. Browser play does not collect selfies, access your camera, host games or process purchases. Other players see your display name and initials.
  • Temporary connection data. To create, join, or recover a cloud-relay room, the Service processes room identifiers, player identifiers, display names, game events, and connection status. Games in this version run through the cloud relay and require an internet connection.
  • Filtered reliability telemetry. The app records limited event names, timestamps, opaque room/player identifiers, transport state, app state, and bounded technical properties to diagnose reliability. It sends that first-party telemetry to the MingleTrivia API. Its telemetry filters block fields containing names, emails, answer content, question text, photos, images, face data, prompts, and documents. This release does not initialize Firebase Analytics, Firebase Auth, Firestore, or Crashlytics.
  • Pseudonymous product analytics. Optional app analytics and first-party diagnostics are off until you enable them in Settings > Your Privacy Choices. Optional website analytics are off until you enable them in Privacy Settings. Older implicit-on preferences do not carry forward as consent in the updated release. The website and the app use PostHog (United States cloud region) for pseudonymous product analytics, such as which pages or screens are viewed and which features are used. Analytics events never include your name, email address, or the content of anything you type. In the app, events are tied to a random per-install ID that is not linked to your name or email; we never use it for advertising. On the website, PostHog runs with memory-only persistence, so it sets no cookie and stores no persistent identifier in your browser; IP addresses are anonymized, and session recording is off. We honor Do Not Track and Global Privacy Control signals by skipping analytics entirely, and you can opt out at any time on Privacy Settings or in the app's settings.
  • Website and security data. Our web server records IP address, request metadata, and timestamps in its access logs to deliver the site, prevent abuse, and rate-limit the waitlist and beta sign-up forms. The rate-limit window is kept in memory for up to one hour. When you fill in one of those forms, Google reCAPTCHA collects hardware and software information, such as device and browser data, and sends it to Google to check that the submission comes from a person and not an automated program. We receive only the resulting pass/fail assessment.
  • Local preferences. The website stores your notice acknowledgment in browser local storage. The app stores limited game and telemetry queues locally so it can function and recover from interrupted connectivity.

2. How we use information

We use information to operate, secure, and improve MingleTrivia. In particular, we use it to:

  • create, run, synchronize, and recover game sessions;
  • display the player identity and optional photo you choose to the people in your game;
  • confirm Apple subscription entitlements and respond to purchase-support questions;
  • send the waitlist and product communications you request, including launch notice;
  • diagnose errors, measure connection reliability, prevent abuse, and maintain security;
  • respond to support, accessibility, privacy, and legal requests; and
  • meet legal obligations and enforce our Terms.

3. Sharing and disclosures

We do not sell personal information or share it for cross-context behavioral advertising. We disclose information only as needed to operate the Service, when you direct us to do so, or as required by law.

People in your game

Other participants receive the display name, game state, and other gameplay information needed to play. If you choose a player photo, it is shared with the devices in your game for the lobby and scoreboard.

Service providers

  • Amazon Web Services: hosting and operation of the API and cloud-relay infrastructure, including Simple Email Service for waitlist confirmation-email delivery.
  • Google: reCAPTCHA spam and abuse protection on the waitlist and beta sign-up forms. Use of reCAPTCHA is subject to the Google Privacy Policy and Terms of Service.
  • Listmonk: self-hosted (on our own infrastructure) waitlist contact management and launch/product communications for people who submit the form; delivered through Amazon Web Services Simple Email Service.
  • Apple: App Store distribution and StoreKit subscription processing.
  • PostHog: pseudonymous product analytics for the website and the app, described in Section 1 above and in our Cookie Policy.

PostHog is not an advertising network and is not used for cross-site tracking. Beyond it, we do not use an in-app advertising network, cross-site tracking SDK, or a Firebase analytics/crash-reporting service in this release.

Providers may process information only to provide their services to us, subject to their terms and applicable law. We may also disclose information in a merger, acquisition, financing, or transfer of assets, or when we reasonably believe disclosure is necessary to comply with law, protect people or property, investigate misuse, or defend legal claims.

4. Storage and retention

  • Optional player photos: stored on-device and scheduled for deletion after 24 hours. When you add a photo, it is sent through the cloud relay to the players in your game as part of the room data. The relay holds it in memory only, never writes it to disk, and discards it with the room (no more than 24 hours).
  • Cloud-relay rooms: held in memory only while active and deleted when the configured room lifetime expires (a room can be configured for no more than 24 hours).
  • Server telemetry: kept in a bounded, in-memory operational store, capped at 5,000 recent events. The app retains a limited local queue/history (up to 200 pending and 500 historical events) in its app storage until it is cleared or the app data is removed.
  • Terms acceptance record: stored in app-local storage until the app’s data is removed. It is not a server-side account or acceptance ledger.
  • Waitlist data: retained while we operate the waitlist and related communications, unless you unsubscribe or request deletion, subject to records we must retain by law.
  • Support and purchase records: retained for the period reasonably needed to address the request, provide the service, prevent fraud, and meet tax or legal duties.

5. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, receive a portable copy of, restrict, or object to certain processing of your personal information. Every marketing email includes an unsubscribe link, or you can email support@mingletrivia.com. The waitlist and beta confirmation emails are transactional and do not include an unsubscribe link; to stop further messages after signing up, email support@mingletrivia.com. Transactional messages about a purchase or an active request may still be necessary.

Use our privacy-rights page for a clear request guide, or visit privacy settings to reset the website’s stored notice choice. You can also email privacy@mingletrivia.com with the right you want to exercise and the email address used for the waitlist or support request. We may need information necessary to verify the request before acting on it. We will not discriminate against you for exercising applicable privacy rights.

6. Cookies and similar storage

mingletrivia.com uses PostHog for the pseudonymous product analytics described in Section 1 and Section 3, but that analytics does not set a cookie: it runs with memory-only persistence, so no analytics identifier is written to your browser and nothing persists past this tab. The site sets no advertising cookie. Browser players also use local storage for the seat, name, random identifiers, reconnect credential and pending game actions described in Section 1. These remain until you leave, forget the seat or clear site data. Other pages use local storage for two necessary preferences: whether you have acknowledged the website-storage notice, and whether you have opted out of analytics. On pages with a sign-up form, Google reCAPTCHA loads after you start filling in the form and may set a strictly necessary security cookie (_GRECAPTCHA) to protect the form from spam. The app does not use browser cookies.

Read the specific Cookie Policy, or use Privacy Settings to reset the notice choice or opt out of analytics. If we introduce advertising technologies or cross-site tracking, we will update this policy and provide the appropriate choices before enabling them.

Do Not Track and Global Privacy Control

This website honors the Do Not Track browser setting and the Global Privacy Control signal: when either is on, or when you opt out on Privacy Settings, we skip loading PostHog entirely for that visit, so no analytics event is sent and no analytics identifier is created. This is separate from the one local website-storage acknowledgment described above and from iOS privacy permissions.

7. Children’s privacy

MingleTrivia is not directed to children under 13, and we do not knowingly collect personal information from children under 13 without the consent required by applicable law. Parents or guardians who believe a child has provided personal information may contact privacy@mingletrivia.com to request review or deletion.

8. Security

We use reasonable technical and organizational measures appropriate to the Service, including transport security for web/API traffic, access controls, provider security commitments, limited data collection, and filtering of sensitive fields from telemetry. No system or transmission is perfectly secure; please use the app only in safe environments and notify us of suspected vulnerabilities at security@mingletrivia.com.

9. International transfers

MingleTrivia is operated from the United States. If you use the Service from another country, information may be transferred to and processed in the United States and other places where our providers operate. Those places may have different data-protection laws than your home jurisdiction.

10. California privacy notice

This section describes, for California residents, the categories of personal information we collect, why, and who receives it. The categories below use the names in the California Consumer Privacy Act (CCPA). We collect them for the purposes described in Section 2.

CategoryExamplesSourceBusiness purposeDisclosed to (service providers)Retention
IdentifiersName, email address, in-game display name, random per-install analytics ID, IP addressYou (waitlist and beta forms, the app); your device and browserRecord signups and send confirmations and updates; run games; pseudonymous analytics; security and abuse preventionListmonk (self-hosted) and Amazon SES; PostHog; Google reCAPTCHA; AWS hostingWaitlist and beta data while the waitlist, beta, or launch offer is active, or until you unsubscribe or request deletion. Analytics ID until you request deletion or reset it in the app. Display name held in relay memory for no more than 24 hours.
Commercial informationPurchase and subscription (entitlement) statusApple, through StoreKit; we never see card dataUnlock Host features; provide the service; prevent fraudAppleAs long as reasonably needed to provide the service, prevent fraud, and meet tax or legal duties
Internet or other electronic network activityPseudonymous page and screen views and feature use; first-party reliability telemetry (opaque ids); request metadata in server access logs; beta device typeYour device and browser; the app; our servers; beta formUnderstand product usage; keep the service reliable; security and abuse preventionPostHog; AWS hosting; Google reCAPTCHAServer telemetry in a bounded in-memory store (5,000 recent events). Analytics until you request deletion. Access logs are kept only as long as needed for operations and security.
Audio, electronic, visual, or similar informationOptional player photo (selfie)You, in the appShow you to the other players in your roomAWS hosting (cloud relay, in memory only); shared with players in your roomOn your device for up to 24 hours. Held in relay memory only, never written to disk, and discarded with the room (no more than 24 hours).
Other information you give usReferral source, support messages, privacy requestsYou (beta form, email)Run the beta; respond to requests; supportListmonk (self-hosted) and Amazon SES; AWS hostingAs long as reasonably needed to address the request or run the beta; until you request deletion for beta form data

A selfie is a photo, not biometric data. We do not perform face recognition or process face data. We do not collect sensitive personal information to infer characteristics about you.

In the past 12 months we have disclosed the categories above to service providers for business purposes. We have not sold or shared personal information, and we do not knowingly sell or share the personal information of consumers under 16.

We treat a Global Privacy Control signal as a request to opt out of sale or sharing. We do not use or disclose sensitive personal information for purposes beyond those permitted by California law, so we do not provide a "Limit the Use of My Sensitive Personal Information" link.

Your California rights

  • Know and access: the categories and specific pieces of personal information we have collected about you, and the sources, purposes, and recipients.
  • Delete: ask us to delete personal information we collected from you, subject to legal exceptions.
  • Correct: ask us to correct inaccurate personal information.
  • Opt out of sale or sharing: we do not sell or share personal information, so there is nothing to opt out of, and we honor Global Privacy Control signals.
  • Limit use of sensitive personal information: we do not use sensitive personal information beyond permitted purposes.
  • Non-discrimination: we will not deny you the service, charge different prices, or provide a different level of service because you exercise these rights.

How to make a request

Submit a request through our privacy-rights page or by emailing privacy@mingletrivia.com.

In the app: open Settings > Your Privacy Choices to turn analytics and diagnostics on or off, and to use "Delete my data on this device".

Verification. For waitlist, beta, and support data, we match the request to the email address you used. For data that exists only in the app, include your analytics ID, which you can copy from Settings > Your Privacy Choices > Copy my analytics ID. An authorized agent needs your signed permission, and we may still verify your identity with you.

Timing. We respond within 45 days. We may extend that once by another 45 days, and we will tell you when we do.

11. People outside the United States

If the GDPR, UK GDPR, or similar law applies to you, our legal bases may include performance of a contract (operating the Service and providing purchases), consent (where required, such as optional marketing), legitimate interests (security, reliability, and service improvement), and compliance with legal obligations. You may have rights of access, correction, deletion, portability, restriction, objection, and withdrawal of consent. You may also lodge a complaint with your local data-protection authority.

13. Changes to this policy

We may update this policy as the Service or applicable requirements change. We will post the revised policy here and update the date above. If a change materially affects how we use personal information, we will provide additional notice when required.

14. Contact

Player safety and moderation

Player names are screened for objectionable words. In rooms using the updated app, the host reviews player photos before sharing them with other players. Hosts can reject a photo or remove a player; a removed device cannot rejoin that room. Players can block another player's name and photo within their room and submit a private safety report. Browser guests never receive player-photo image data.

Submitting a safety report shares the reported name/photo, room and player identifiers, selected reason, and any explanation with MingleTrivia moderators. Reports are stored privately for up to 30 days; sensitive evidence is removed once a report is resolved. Safety notifications contain a report reference rather than the photo. We review safety reports within 24 hours. These safety actions and the room relay operate independently of optional analytics and diagnostic choices. Contact support@mingletrivia.com or use Report a Concern.

Use the private routes on our Report a Concern page for privacy, safety/conduct, accessibility, and content-rights reports. Security reports may be sent to security@mingletrivia.com.