DuoQueue Privacy Policy

Effective date: November 2, 2026 Version: 1.12

This policy explains what DuoQueue collects, why, who we share it with, and what control you have over it. It's written in plain language on purpose. If anything here is unclear, contact us using the details below.


1. Who we are

DuoQueue is a swipe-based app for finding gaming duos, built for players 18 and older.

  • Legal entity: DuoQueue is operated by Cameron Shaw Stallings, as an individual (a sole proprietor), not a company or LLC.
  • Mailing address: 808 Crawford St, Houston, TX 77010, USA
  • Contact email for privacy questions and rights requests: support@duoqueue.io, the same monitored address used for support and safety reports throughout the app (see apps/mobile/src/lib/legal.ts).
  • Data Protection Officer / EU or UK representative: None appointed. DuoQueue is available in every country where Apple's App Store offers it, and it's run from the United States by one person. Wherever you live, send any privacy question or request to the email above.

Wherever this policy says "contact us," use the email above.


2. What we collect, and why

We only collect what the app actually uses. Here's every category, itemized.

Account information

  • Email address and password, if you sign up with email. Your password is never stored or seen by us in plain text. Authentication is handled by our infrastructure provider, Supabase Auth, which stores a salted hash. We use your email to let you sign in, confirm your address (a one-time 6-digit code), and send account-related messages.
  • What Apple shares, if you sign in with Apple. Apple signs you in, and we never see your Apple ID password. Apple gives us:
    • An email address. Either your real one, or, if you choose Hide My Email, a private relay address that Apple creates for DuoQueue and forwards to you. We use it for your account and for account-related messages, the same way we use the address of someone who signed up with email.
    • Your name, if you choose to share it. Apple sends it only the first time you sign in with Apple to DuoQueue, and you can edit or remove it on Apple's screen first. We use only your first name (or a nickname, if that is all Apple sends), and only as a suggested display name: it is filled in on the first step of setting up your profile, where you can change it before anyone sees it. Your profile is not shown to anyone until you finish setting it up. We do not store your last name.
    • An identifier for your Apple ID. A stable ID that Apple issues only to apps from our developer account, which is how we recognize you the next time you sign in with Apple. Other companies' apps cannot use it to recognize you.
    • Not your date of birth. Apple does not share it. From version 1.0.2 of the app, a new player gives it on the first screen, before any account exists. If you sign in with Apple without having given it first (and in earlier versions of the app), we ask for it right after you sign in, before your profile is created. See Section 9.
  • An Apple token kept only to revoke access. When you sign in with Apple, our server exchanges a one-time code from Apple for a token (Apple calls it a refresh token) that lets us revoke DuoQueue's access to your Apple ID. We keep it for that one purpose: when you delete your account, we use it to tell Apple to remove DuoQueue from the apps using Sign in with Apple in your Apple ID settings, and then it is deleted with the rest of your account. It is stored where only our servers can read it, it is never shown to anyone, and it is never used for anything else.

Profile information

  • Display name: shown on your profile and in chat.
  • Date of birth: collected once at signup. We use it for two things: confirming you're 18 or older (DuoQueue is not available to anyone younger; see Section 9) and calculating the age shown on your profile. Your exact birth date is never shown to other users, only your calculated age.
  • Gender: no longer collected. Earlier test versions of the app asked for it during setup. If you answered then, the answer is still stored until you delete your account. The app never shows it, but it is still part of the profile information our servers send to another user's app when your profile is shown to them (for example, in their deck, in Online Now, in the list of people who liked them, or when they open your profile), so it is not private from other signed-in users. It is never used to filter or rank who you're shown.
  • Region: collected at onboarding and shown on your profile to other users; also used to filter candidates when someone sets a region preference, to slightly favor same-region matches in ranking, and to work out Can duo.
  • Spoken language(s): collected at onboarding; used as a premium filter so users can require a shared language, and to favor candidates who share a language with you in ranking.
  • Photos: one optional picture, of anything you like. It is shown on your card and next to your name. Earlier test versions also asked for a header photo, which is still shown on your card if you haven't added a picture, and allowed gallery photos, which are kept but no longer shown in the app (they can still be part of the profile information sent to another signed-in user's app). All of them are deleted with your account, except as described in Section 5. Every uploaded photo is automatically re-processed to strip embedded location and camera metadata (EXIF/GPS data) before it's stored. Every photo also goes through our moderation pipeline before it becomes visible to anyone else. When our automated moderation provider (Sightengine) is configured, most photos are screened automatically and only borderline or undetermined cases go to a human moderator; if the automated provider isn't configured, every photo instead goes straight to human review. See Section 3.
  • Bio and prompt answers: free-text fields you write about yourself.
  • Games, shows/movies/anime, and platforms: what you play or watch, your self-reported skill level and rank per game, and which platforms (PC, PlayStation, Xbox, Switch, mobile) you play on. Your League of Legends rank, if you add one, is a tier and, for most tiers, a division (for example, "Gold II"), and it is shown to other users. We also compare the games, region and platforms you list with another player's, using each game's published cross-play rules, to show players you can play a game with nearer the top of your deck and, from version 1.0.4 of the app, to mark them "Can duo". For League of Legends in North America we compare your rank with theirs instead, using League's published rules for who can queue together, to mark players you can duo with in Ranked Solo/Duo. Other players see the same about you.
  • Playstyle tags and "vibe" answers: self-reported traits (e.g. chill vs. competitive, mic preference) and three sliders (session intensity, communication style, coaching preference) plus a tilt-handling answer, used to help match you with compatible players.
  • Schedule/timezone: your device timezone (detected automatically at signup) and an optional "usual play window" (hours of day you typically play), used to rank candidates who are actually awake and playing when you are.
  • Discord username (optional): never shown automatically. It's only revealed to a specific match if and when you tap "Share my Discord" in that conversation.

Content

  • Messages. Chat messages you send to a match (or a party) are stored so the conversation is available across your devices. Before a message you send to a match is stored and delivered, our server checks it against a short list of swear words, slurs and abusive phrases, and replaces any it finds with asterisks. The original words are not stored, and we note on the message that it was changed. Messages in a party chat are not checked this way. Separately, you can list words or phrases in Hidden words (in Settings). A message from someone else that contains one of them is hidden in your chat until you tap to reveal it. This happens on your phone and does not change the message for anyone else. Your list is stored with your account so it works on each of your devices, no other player can see it, and it is deleted with your account. What happens to a party chat when players leave it is described in Section 5. Messages are intended to be private between the participants of that conversation, with one exception: if a message is reported, a human moderator on our team reviews the reported conversation to investigate. This is a policy commitment about how we access messages, not an absolute technical restriction: our moderation tooling is built so an admin account is able to open any conversation to investigate a report, and admins are instructed to only do so in direct response to an open report. The limits of that control are described plainly in Section 7.

Usage information

  • Presence / "Online Now" status: a signal that you're free to duo right now, on only when you turn it on. From version 1.0.2 of the app you turn it on by tapping Queue up; in earlier versions, with a switch in Online Now. Either way it ends after 60 minutes or when you stop. We also track a general "last active" timestamp used to rank the deck and to show partners when you're around.
  • Swipes and matches: who you liked, passed on, or matched with, needed to run the core matching feature and prevent the same profile from being shown to you twice.
  • Duo Pops and Duo Calls. When you tap Queue up, we record which players we sent a Duo Pop to, which of them opened or answered it, the short code in your LFG post, and, if someone becomes your duo with that code, who it was. Anyone who has the code can see your display name while it works. From version 1.0.4 of the app, any signed-in player who opens the code also sees the game it is for and can answer it to become your duo, and until 7 days after you queued up they can still see your name and the game, with a note that your post has ended or that someone already took it. If Duo Pops are on for you, we record that you were sent one and whether you opened or answered it. The player who queued up never sees who opened a Duo Pop or passed on it. Duo Pops only go to players whose region is NA East or NA West and who have them on. When you tap Queue up, your Duo Pop can go first to players you've matched with who play that game and have "A match queues up" on in Settings → Notifications, and then to other players in that game. A Duo Pop to a player you've matched with names you in the notification. A Duo Pop to anyone else doesn't name you until they open it. If nobody takes your Duo Pop in its 10 minutes and you're still queued, we send you one notification saying so, and we note on these records when we sent it. We delete these records after 30 days, and your part of them right away when you delete your account. Separately, the notification itself (that a Duo Pop was sent to you, or that the player who queued up was told theirs was grabbed, or that nobody took it) is recorded in our notification delivery log like every other notification, and that record is kept for 90 days (see "Notification delivery log" below). From version 1.0.3 of the app, Duo Pops are on by default for players whose region is NA East or NA West: the app turns them on once for your account and tells you in the app when it does, with a button to turn them off right there. Earlier versions of the app never turn them on by themselves. Either way, you can turn them off or back on at any time in Settings → Notifications. A Duo Pop is a notification, so it only reaches your phone if you allow notifications from DuoQueue in your iPhone's settings. That choice stays yours: if iOS has not asked you yet, tapping Got it on that notice asks you. We note when Duo Pops were first turned on or off for your account, whether by the default or by you, so the app turns them on by default at most once, and never after you have turned them on or off yourself in version 1.0.3 or later. That note is kept with your notification settings and deleted with your account.
  • Party LFG posts. From version 1.0.2 of the app, either player in a party of two can share an LFG post with a code to find a third. For each post we record its code, the game it names, who shared it, when it was made and until when it works, whether it was stopped, and who joined the party with it and when. Making a post also puts a note from you in your party chat. While a post is live, anyone with its code, even before they sign up, can see the name of the player who shared it and the game, and a signed-in player who is allowed to join sees the name and age of everyone in the party before joining. If you join a party with a code, we note that on your party membership, so the party chat shows you messages only from when you joined; we also note when each member's app first showed the party's post, so a post can only be made once everyone in the party can see it and stop it. We delete posts after 30 days. Deleting the account that shared a post deletes the post, and deleting the account that joined with it removes that account from it. The notes on your party membership are kept while you are in the party and deleted when you leave it, or when the party or your account is deleted.
  • Reports and blocks: who you've reported or blocked, and why, so we can act on it and keep that person from reappearing in your deck.
  • Match feedback tags: optional, non-public tags ("good comms," "showed up on time," "flaked," etc.) you can leave about a match after the fact, used to build a lightweight reputation signal.

Device information

  • Push notification token and app version. If you grant notification permission, we store a device-specific push token (via Expo's push service) so we can deliver notifications like new matches and messages. Starting with version 1.0.2 of the app, we store next to that token which version and build of DuoQueue your phone is running, which app update it has installed, and your phone's operating system and its version (for example, iOS 18.6). We use this only to see which app versions are still in use, so we can fix problems and tell people when an update is needed. It includes no other device identifier, no device name and no location, and it is deleted with the token when you sign out on that phone or delete your account. If your phone cannot reach DuoQueue when you sign out, the token and these details stay linked to your account until another account signs in on that phone, we learn the app was removed from it, or you delete your account.
  • Notification delivery log. For each notification we send you, we keep a short record: which kind it was (for example, a new match, a message or a Duo Pop), when it was sent, how many of your devices we sent it to, whether Expo's push service accepted it, and the error code if it did not. It holds no message content: no title, no text, no names. We use it only to check that notifications are delivered and to stop sending the ones that do not help. We delete these records after 90 days, and all of yours when you delete your account.

Purchases

  • Subscription and purchase status (DuoQueue+ and Power-Ups). Purchases are handled entirely by Apple's App Store, and processed for us by RevenueCat. We never see or store your card number, billing address, or any other payment credential. We only receive purchase/subscription status (active, expired, product purchased, renewal date) from RevenueCat.

Optional linked gaming accounts

  • Steam. If you choose to link your Steam account, we verify it's really yours via Steam's own sign-in (OpenID), then store your Steam ID, persona name, and avatar. We separately pull your owned-games playtime for titles in our catalog (e.g. "42.3h on Counter-Strike 2") so your stats are verified rather than self-reported. Steam's profile lookup can return additional public-profile fields (real name, country/state, account-creation time, and more, depending on the linked account's own Steam privacy settings). Our server only persists the Steam ID, persona name, and avatar into your profile; the rest of that response is discarded and never stored.
  • We only ever read the specific fields disclosed above. We do not read your friends list, purchase history, private messages, or anything else on Steam.

Bot-protection signals

  • At signup, we may run Cloudflare Turnstile, an anti-bot challenge, to block automated account creation. Cloudflare processes device/browser signals for this purpose; we don't receive or store the details itself, only a pass/fail token.

Invites

DuoQueue gives every account a personal invite code so you can bring someone you already play with. Using one records a relationship between two accounts, so it is its own category rather than a footnote under profile data.

  • Who invited whom. When you sign up with someone's invite code, we store your account ID, their account ID, the code that was used, and the date. We use it for two things: to show you their profile when you arrive, so the person who invited you is the first face you see rather than a stranger, and to understand how many people join this way. You have one inviter, and it is whoever's code you used first. Redeeming a second code does not change it.
  • Whether the two of you actually connected. If you tap the button to duo up with the person who invited you, we record the date you did. That is a separate fact from the invite itself, and it is the only thing we record about what happened next; the conversation you have afterwards is an ordinary chat and is covered under Content above.
  • Your own invite code. We store one code per account, when it was created, and whether it has been turned off. The code is a random string. It is not derived from your name, your email address, or anything else about you, and it cannot be reversed into any of them.
  • We do not learn who you sent an invite to unless they join. The invite travels in a message you send, through whatever app you send it in. We are not in that conversation, we never see the recipient, and nothing is stored about anybody who receives a code and does not sign up. There is no address book access, no contact upload, and no way for us to know an invite was sent at all until somebody uses it.
  • Deleting your account removes it. The invite records are attached to the accounts in them, so deleting yours deletes your code and any record of who invited you. See Section 5.

Website (duoqueue.io) and the old waitlist

This is the one category on this list that is about our website rather than the app.

  • What the website collects today: nothing from you directly. DuoQueue launched on the App Store on September 30, 2026, and we took the waitlist form off the site that day. duoqueue.io has no form any more, so it does not ask for your email address or anything else.
  • No cookies, no analytics, and no advertising scripts on duoqueue.io. Our pages set no cookies, carry no analytics or advertising tag, and load nothing from a third-party server: every page is self-contained HTML, and the only files it requests are its own fonts and icon and, on the trailer page (duoqueue.io/watch/), a short video about the app and its poster image, all served from duoqueue.io itself. The video plays in your browser's own built-in player. There is no JavaScript on the site at all.
  • Our web host sees your visit. duoqueue.io is published as a static site on GitHub Pages, so GitHub operates the server that answers your request and sees your IP address and user agent the way any web host would. GitHub is listed in Section 3.
  • Shared links. From version 1.0.4 of the app, the link in an LFG post or an invite is duoqueue.io/i/ followed by its code. If DuoQueue is on your iPhone, tapping the link usually opens the app, which uses the code the same way as one you type in. Otherwise duoqueue.io sends your browser on to DuoQueue's page on the App Store, and so does any other duoqueue.io address that doesn't exist. These links collect nothing new: GitHub sees the visit like any other page visit, including the code in the address, and we receive nothing from GitHub about it. So that your iPhone knows which links belong to DuoQueue, Apple reads a small public file on duoqueue.io that lists them, and your iPhone gets that list from Apple.
  • If you joined the waitlist before launch. We stored your email address, the date, and which of our links you arrived from (so we knew which channel worked). The only emails a waitlist address can get from us are a confirmation that you joined and one message announcing the launch. That second message is marketing, and we call it that rather than describing it as transactional. We do not add waitlist addresses to any other mailing list, we do not sell or rent them, and we do not use them to advertise to you anywhere else. We keep your address until you ask us to delete it, or until we delete the list (see Section 5). You can ask at any time by replying to a waitlist email or contacting us at the address in Section 1.
  • The old form, if a copy is still open somewhere. A copy of the form left open in a browser tab from before launch can still send an address to our server. If one does, our server does not add the address to the list or keep it: it sends the browser to our home page. To stop bots, it still keeps a salted, one-way hash of the IP address that sent it, never the IP address itself, for 48 hours. The form goes to our backend at supabase.co, which sits behind Cloudflare, and Cloudflare's bot protection may set a short-lived cookie called __cf_bm on that supabase.co domain, never on duoqueue.io. It lasts 30 minutes, it is not readable by our pages, and it is not used for advertising or cross-site tracking.
  • The 18-or-older box on that form was a self-declaration. You told us your age; we did not check it, and we do not describe it as verification or age assurance. It was there because DuoQueue is an adults-only product and we did not want an underage person on a mailing list for it.

What we do NOT collect

We do not collect precise GPS location, contacts-list access, or browsing history outside the app. We do not run any advertising or analytics SDK: there is no Meta/Google ad pixel, no Mixpanel/Amplitude/Segment-style tracker, or any comparable dependency anywhere in the app's code today.


3. Who we share data with

We use a small number of specialized service providers ("processors") to run the app and the website: Supabase, Sightengine, Expo, Resend, RevenueCat, Apple, Cloudflare, GitHub, and Steam. We use each of them as a service provider/processor under that provider's own standard terms of service, and none of them can use your data for their own purposes beyond providing their service to us.

ProviderRoleWhat they receiveLocation
SupabaseHosting, database, authentication, file storage, and realtime chat delivery (the backbone the whole app runs on)Effectively all account and profile data described in Section 2United States
SightengineAutomated photo moderation, when configured (see below)When our automated moderation provider is active, every photo you upload is sent to Sightengine to be automatically screened for nudity, graphic content, and whether the person in the photo appears to be a minor, before it's shown to anyone elseUnited States
Expo (push notifications and app updates)Delivers push notifications, and delivers updates to the appYour device push token and the notification content (e.g. "You matched with X"). To get that push token, the app sends Expo your phone's Apple push token, DuoQueue's app ID and a random ID that Expo's notification code creates on your phone. It does this when you first allow notifications, and each time the app starts after that. Also, each time the app starts, it asks Expo's update service (u.expo.dev) whether there is a newer update for your version of DuoQueue, and downloads it from Expo if there is. That request carries the platform (iOS), the app's version and runtime version, its update channel, the IDs of the updates installed on your phone, a random ID that Expo's update code creates on your phone the first time it runs, and, if the app crashed the last time it opened, a short description of the error. Like any request over the internet, it also carries your IP address. It carries no account details, and we do not link that random ID to your accountUnited States
ResendSends our email: transactional messages (signup confirmation, account emails) and the waitlist messages described in Section 2, one of which is a marketing announcementYour email address and the content of the email being sentUnited States
GitHub (GitHub Pages)Hosts duoqueue.io, our public website: the home page, a short video about the app, these legal documents, the page a shared DuoQueue link opens in a browser, the file that tells iPhones which links open the app, and a small file the DuoQueue app reads to check whether its version is still supportedThe IP address, user agent, and requested URL of every visit to duoqueue.io, as any web host receives. For a shared link opened in a browser, that URL includes the link's code. From version 1.0.2, the DuoQueue app also reads one small file from duoqueue.io when it opens (and at most about once an hour after that) to check whether its version is still supported, so GitHub receives the same details for that request. We do not receive or keep server logs from GitHub, and there is no analytics on the siteUnited States / global edge network
RevenueCatManages subscriptions and in-app purchasesYour app-level user ID and purchase/subscription events from Apple (never your payment details)United States
Apple (App Store)Processes your payment when you buy a subscription or a Power-UpYour payment details, handled entirely by Apple; we never receive themUnited States
Apple (Sign in with Apple)Only if you choose to sign in with Apple: signs you in, and later lets us revoke that accessApple authenticates you itself. Our server sends Apple the one-time code from your sign-in to obtain the revocation token described in Section 2, and, when you delete your account, that token (or a fresh code from the same Apple ID) so Apple can revoke DuoQueue's accessUnited States
CloudflareTwo separate roles: the Turnstile bot-protection challenge at signup in the app, and the network in front of our Supabase backend, which a submission of the old waitlist form passes throughDevice/browser signals used to distinguish humans from bots. Its bot protection may set a 30-minute __cf_bm cookie on the supabase.co domain when the old waitlist form is submitted, never on duoqueue.io, and never for advertisingGlobal network (may include US)
SteamOnly if you choose to link an accountWe send your account link request to Steam and receive back the public profile fields listed in Section 2United States (approximate, platform-dependent)

Sightengine and Resend are config-gated, not hard-wired. Our photo-moderation pipeline defaults to routing every photo straight to human review and only calls Sightengine when a provider setting and API credentials are set in our live environment; if that configuration is ever unset, no photo is sent to Sightengine at all. As of this writing, our live production environment has that provider setting and both Sightengine credentials configured, so automated screening is active. Transactional email (account confirmation codes and similar) is sent through Resend, which is configured as our custom SMTP provider. Any waitlist email described in Section 2 is sent through Resend as well.

Where your data is processed. DuoQueue is available in every country where Apple's App Store offers it. Wherever you live, your data is processed and stored in the United States by the providers listed above. If you live outside the United States, that means your data is transferred to the United States, where privacy laws may differ from the laws where you live.

We do not sell your personal information. We do not share your data with data brokers or advertising networks, and we don't run any advertising or analytics SDK that would make this a "sale" or "share" under CCPA/CPRA. See Section 6 for the CCPA-specific disclosures.


DuoQueue is available in the EU, UK and EEA through Apple's App Store (see Section 1). If you're in a region covered by the GDPR or UK GDPR, here's the legal basis for each category of processing:

  • Performance of a contract: running the account you signed up for. Email, password, Sign in with Apple, profile data, matching, messaging, purchases, and account deletion all rely on this basis, since we can't provide the app without them.
  • Legitimate interests: content moderation (photo screening, report handling), fraud/bot prevention (Turnstile), keeping the deck functional (swipe/match history), and security logging. We've weighed these against your privacy interests and believe they're necessary and proportionate to keep the app safe.
  • Consent: anything genuinely optional, including linking a Steam account, sharing your Discord username with a specific match, and push notifications (which require your device-level permission). You can withdraw consent at any time by unlinking the account, not sharing, or disabling notifications (see Section 6).

5. How long we keep data

  • Active accounts. We keep your data for as long as your account exists and you're using the app.
  • Deleted accounts. DuoQueue has in-app account deletion (Settings → Sign out or delete account → Delete account). When you delete your account:
    • Your profile, photos, messages, matches, swipe history, preferences, linked accounts, and push tokens are permanently deleted, including the underlying stored files (not just hidden). Because a conversation is tied to the match between you and your match partner, deleting your account also deletes your match partner's copy of any conversation you shared with them, not just yours.
    • This is irreversible. There is no "undo" or account-recovery grace period once deletion completes.
    • If you signed in with Apple, deleting your account also tells Apple to revoke DuoQueue's access to your Apple ID, so DuoQueue is removed from the apps using Sign in with Apple in your Apple ID settings. We do this with the token kept from your sign-in. Your iPhone may also ask you to confirm with your Apple ID, which gives us a fresh code to use instead if that token is missing or no longer works; we use it only if it belongs to the same Apple ID you signed in with. If you dismiss that confirmation, or Apple cannot be reached, your account is still deleted. If DuoQueue is still listed in your Apple ID settings under Sign in with Apple afterwards, you can remove it there yourself. That token is deleted with your account either way.
    • Before your profile is finished. If you signed in but have not finished setting up your profile (for example, you signed in with Apple and stopped at the date of birth screen), you can delete the account with "Delete this sign-in", on that screen or, on any step of profile setup, under "Sign out or delete". It goes through the same deletion described here.
    • Exception: if someone else's report about you is on file when you delete your account, the report record itself, and an internal reference id, are retained after your profile and identifying data are otherwise deleted, so we can maintain a history of safety actions (e.g. confirming a pattern of reported behavior) without your profile continuing to exist. This is a reference id, not an anonymization process: it is not linked to your profile once your profile is gone, but it isn't scrubbed of the report's own content (e.g. the reason and details given) either. The same is true for a report you filed: if you delete your account, that report record is kept, with an internal reference id in place of your profile.
    • Safety holds. Three things are kept, or stop a deletion, for safety reasons:
      • A photo or voice intro that never passed our safety check (one that was rejected, or one still waiting for review) is not deleted with your account. We keep the stored file and a record of it so a moderator can still review it and, where the law requires, report it, for as long as that review or legal obligation lasts.
      • An account that has been banned cannot be deleted in the app; contact support@duoqueue.io. A record of the ban is kept after any deletion so the same address cannot sign up again; it holds a one-way hash of the account's email address, not the address itself.
      • If there is an open report that the account holder may be under 18, the account is frozen and banned instead of deleted: its display name, bio and Discord username are removed and it is hidden from everyone, but its matches, messages, photos and voice intro are kept for that review.
  • Invites. Your invite code and any record of who invited you are attached to your account and are deleted with it. The same is true in the other direction: if somebody you invited deletes their account, the record of you having invited them goes with theirs. This means an invite record only ever exists while both accounts do, and neither of you can be left in a record the other has deleted.
  • Parties. From version 1.0.3 of the app, you can leave a party. Leaving removes you from the party and deletes the likes and passes you made in its deck. It also stops any LFG post the party has open, and if you started the party, it no longer records that you did. After you leave, you can no longer see the party or its chat. The messages you sent stay in the chat. The players still in it can read them, and so can a player who joins the party later by invite. A player who joins with an LFG code sees only messages sent after they joined. The players still in it will see that you left, and if two of them are left, they may get a notification saying so. A party needs at least two players. When fewer than two are left, the party, its chat and its posts are deleted for everyone. In every version of the app, the same happens when the last two players in a party unmatch, or when one of them blocks the other. This happens at once when someone leaves or unmatches. After a block, the party ends at once for its players, and its chat is deleted after the 7 days explained below. When it is because a player deleted their account, our daily cleanup deletes the party within a day. If leaving brings a party down to two players who also have another party of just the two of them, we keep the one with the most messages and delete the rest the same way.
    • A reported party chat is kept. There are two exceptions to these deletions. If a report between two of the party's players is still open, we keep the party chat for that report instead of deleting it. The party's players here are the ones still in it and anyone who wrote in its chat. The players involved in the leave, block or unmatch that ended it also count when it ends, and after a block, for the 7 days that follow. Once a player deletes their account, they no longer count here. A report about them, or one they made, then keeps the chat only if it was already being kept. If a party ends because one player blocked another, we also keep its chat for 7 days after the block, so a report made in that time can still be reviewed. A report between two of the party's players made in those 7 days keeps the chat the same way as a report made before the block. If no report keeps it, our daily cleanup deletes the chat within a day after those 7 days. The kept chat has no members, and its posts stop working. No player can open it, including the players who were in it. Our moderation team can still read it to review the report. Messages from a player who deletes their account are still deleted with that account. Once every such report is closed (acted on or dismissed), or deleted, our daily cleanup deletes the chat within a day. After a block, that is never before the 7 days are up. A report made after a party chat is deleted cannot bring it back. When a party ends because a player left or unmatched, its chat is deleted at once unless a report already keeps it. If you want a party chat reviewed, report the player before you leave or unmatch.
  • Waitlist signups (duoqueue.io). The waitlist form has been off our website since launch (see Section 2). The salted hash of the IP address that sent a form is deleted automatically 48 hours after it was created. Your email address and the link you arrived from are kept until you ask us to delete them, or until we delete the list, whichever comes first. Waitlist rows are stored separately from app accounts and are not connected to one: joining the waitlist does not create an account, and deleting your DuoQueue account does not remove your address from the waitlist. If you want both gone, tell us and we will do both.
  • Backups. As of this writing, our hosting provider's automated point-in-time recovery and scheduled backup snapshots are not enabled for our production database, so there is no additional backup-retention window beyond the deletion described above. If backups are enabled in the future, deleted data could persist in a backup for that backup's retention period before being purged in the normal course of our hosting provider's backup rotation.
  • Legal holds. We may retain specific records longer than normal if we're legally required to (e.g. an active law enforcement request), for as long as that requirement lasts.

6. Your rights

You have the following rights over your data. Most are available directly in the app; the rest are a quick email away.

RightWhat it meansHow to exercise it
AccessSee what we hold about youView it directly in the app (profile, matches, messages, settings), or email us for a full export
CorrectionFix inaccurate dataEdit your profile directly in the app for anything editable; email us for anything you can't change yourself (e.g. date of birth)
DeletionDelete your account and dataSettings → Sign out or delete account → Delete account ("Delete this sign-in" if your profile isn't finished yet), or email us if you'd rather we do it
PortabilityGet a copy of your data in a portable formatEmail us. There's no self-service export button in the app yet, so this is handled manually, within a reasonable turnaround (GDPR: 30 days; CCPA: 45 days)
ObjectionObject to processing based on legitimate interestsEmail us with what you're objecting to
Withdraw consentRevoke any consent-based processing at any timeUnlink a gaming account, stop sharing Discord in a chat, or turn off notification permissions (all directly in the app)

California residents (CCPA/CPRA)

In the last 12 months, we've collected the categories of personal information described in Section 2 (identifiers, including an email address given to us on our website; profile/characteristics data; commercial/purchase information; internet/app activity, including a short-lived salted hash of the IP address that submitted our website's old waitlist form; a record of which account invited you to DuoQueue, where you joined using someone's invite code; and information about your other online activity from linked gaming accounts). We've disclosed those same categories to the service providers listed in Section 3, for the business purposes described there.

Sending the one-time launch announcement you asked for by joining our waitlist is direct marketing, not a sale or a share, and it is not cross-context behavioral advertising. We do not disclose waitlist addresses to anyone except the email provider that delivers the message.

  • We do not sell or share (as CPRA defines "share," which includes cross-context behavioral advertising) your personal information, and we don't operate any advertising-technology pipeline that would make this happen. There is nothing to opt out of.
  • You have the right to know, delete, and correct your personal information, and the right to non-discrimination for exercising any of these rights. We will never charge you more or provide a worse experience because you made a privacy request.
  • To exercise any CCPA/CPRA right, use the contact email in Section 1.

EU/UK/EEA residents (GDPR)

DuoQueue is run from the United States and has no establishment in the EU or UK, so it has no lead supervisory authority there. You can contact us first using the email in Section 1, and you have the right to complain to the data protection authority where you live.


7. Security

We take reasonable steps to protect your data, but no system is perfectly secure, and we can't guarantee absolute security.

  • Encryption in transit. All traffic between the app and our servers is encrypted (HTTPS/TLS), including chat messages, photos, and account data.
  • Encryption at rest. Our hosting provider, Supabase, encrypts stored data at rest.
  • Access controls. We use row-level database access controls so that, by default, a user's private data (messages, profile, preferences) is only readable by that user or the specific people it's meant to be shared with (e.g. your match partner in a conversation). Administrative access to broader data (e.g. for moderation) is restricted to designated accounts and gated by an admin flag that isn't self-grantable. That access is not currently logged.
  • Content moderation. Photos go through our moderation pipeline (automated when configured, human review otherwise; see Section 2/Section 3) before becoming visible to others, and reported content can be reviewed by our moderation team.
  • What we don't promise. We do not claim our systems are unhackable or that a breach could never happen. If one does, we will notify affected users and relevant authorities as required by applicable law.

If you believe you've found a security vulnerability, please report it to the contact email in Section 1 rather than exploiting or publicly disclosing it first.


8. Automated decision-making (photo moderation)

When you upload a photo, and our automated moderation provider (Sightengine) is configured (see Section 3), it analyzes the photo to check for nudity, graphic content, and whether the person appears to be a minor, and can automatically reject a photo without a human reviewing it first. If your photo is rejected and you believe that was a mistake, you can contact us to request human review. Photos that the automated system can't confidently judge (or every photo, if the automated provider isn't configured) are held for manual review by our team rather than being auto-approved or auto-rejected.


9. Age restriction

DuoQueue is for adults only: you must be 18 or older to create an account.

We ask for your date of birth at signup, and we enforce the 18+ rule on the date you give us: a date of birth under 18 is rejected by the app and again by our database, which will not store a profile with one, so an under-18 date cannot complete a profile. From version 1.0.2 of the app, we ask for it on the first screen, before you build your card and before any account exists. Until you save your card it is kept only on your phone and is not sent to us; it expires after 7 days, and it is cleared when you save your card, choose Start over or sign out. It is sent to us once, when your account is created. If you sign in with Apple, which does not share a date of birth, without having given it first (and in earlier versions of the app), we ask for it right after you sign in instead, and no profile is created until you give one that is 18 or older. Until then the account can see no one's profile and no one can see it, and you can delete it from that screen. What we do not do is verify that the date is true. We do not check identity documents and we do not use a third-party age-assurance service. It is a self-declaration that we then enforce, and we describe it that way here rather than calling it verification, which would imply a check we do not perform. The 18-or-older box on our website's old waitlist form (Section 2) was a self-declaration in the same sense, with no profile behind it to enforce against.

If we learn that someone under 18 has created an account (for example, through a report using the "underage" report reason, or otherwise), we will terminate that account and delete the associated data as described in Section 5. If you believe a minor is using DuoQueue, please report that profile in the app (profile → Report) or contact us directly using the email in Section 1.

We do not knowingly collect personal information from anyone under 18. If you're a parent or guardian and believe your child has provided us with personal information, contact us and we will investigate and delete it.


10. Changes to this policy

We may update this policy as the app changes. If we make a material change, we'll update the effective date at the top of this document. For significant changes, we'll also make a reasonable effort to notify users in-app before the change takes effect. We encourage you to review this policy periodically.

What changed in version 1.12 (November 2, 2026):

  • Can duo in any game. From version 1.0.4 of the app, Can duo lights up for a game you and another player both list, when you're in the same region and your platforms can play together. To work that out, we compare the games, region and platforms you both list. For League of Legends in North America we still compare ranks. See "Games, shows/movies/anime, and platforms" and "Region" in Section 2.
  • Shared links and Duo Call codes. From version 1.0.4 of the app, the link in an LFG post or an invite can open DuoQueue directly. Any signed-in player can answer a live Duo Call code, and anyone signed in who has your post's code can see your name and its game until 7 days after you queued up. The links collect nothing new. See "Duo Pops and Duo Calls" and "Website (duoqueue.io) and the old waitlist" in Section 2, and the GitHub row in Section 3.

What changed in version 1.11 (October 29, 2026):

  • Duo Pops for players you've matched with. When you tap Queue up, your Duo Pop can now go first to players you've matched with who play that game and have "A match queues up" on, and the notification they get names you. See "Duo Pops and Duo Calls" in Section 2.
  • When nobody takes your Duo Pop. If nobody takes it in its 10 minutes and you're still queued, we send you one notification saying so. See "Duo Pops and Duo Calls" in Section 2.

What changed in version 1.10 (October 27, 2026):

  • Where DuoQueue is available. DuoQueue is available in every country where Apple's App Store offers it, not only in the United States. Your data is still processed and stored in the United States. See Section 1, "Where your data is processed" in Section 3, Section 4 and Section 6.

What changed in version 1.9 (October 27, 2026):

  • Deck order. We now compare the games, region and platforms you and another player list, using each game's published cross-play rules, and show players you can play a game with nearer the top of your deck. See "Games, shows/movies/anime, and platforms" and "Region" in Section 2.

What changed in version 1.8 (October 27, 2026):

  • Duo Pops are on by default. Since version 1.0.3 of the app, Duo Pops are on by default for players whose region is NA East or NA West. The app tells you when it turns them on, with a button to turn them off, and you can turn them off or back on at any time in Settings → Notifications. See "Duo Pops and Duo Calls" in Section 2.
  • App updates. Section 3 now lists Expo's update service, which the app checks when it starts, and what that check sends. It also says what the app sends Expo to get its push token.
  • Website. The website section now says what duoqueue.io collects since the app launched (nothing from you directly), and what happens to email addresses from the old waitlist.
  • Purchases. The list of purchases now names only what the app sells, DuoQueue+ and Power-Ups, and only Apple as the store. Section 3 no longer lists Google, because DuoQueue is only on iPhone.

Contact us

Email support@duoqueue.io with any question about this policy. For our full legal entity name and business address, see Section 1.