Privacy Policy

1. Information We Collect

We may collect the following categories of information:

• Personal information such as your name, email address, and details provided through our waitlist or referral forms.
• Friend referral details that you or your nominated friends voluntarily share for introductions.
• Login information (as applicable), such as account credentials and authentication data.
• Demographic information and dating preferences you provide through the website or share with our AI tools.
• Optional profile information such as education, occupation, location, and interests.
• Payment information, if applicable, when you make a purchase or subscribe to a paid feature.
• Technical information, including browser type, device identifiers, and website usage data collected through cookies or analytics tools.
• Marketing attribution information about how you found us, such as the campaign tags on the link you arrived through and the website that sent you (see section 7).

We do not intentionally collect sensitive personal data unless explicitly provided for the purpose of matchmaking.

If you are a concierge client, this information is not collected from you through the website. Our team gathers it in an interview and builds your profile for you, on your behalf and with your consent, and the account that holds it is created and operated by our team rather than by you.

2. How We Use Your Information

We use your information to:

• Manage waitlist sign-ups, account creation, and referrals
• Facilitate introductions and improve matching accuracy
• Operate and refine AI-based insights and recommendations
• Communicate updates, events, and service information
• Process payments, where applicable
• Monitor website and app performance and enhance user experience
• Measure how our advertising performs, and which channels, ads, and links bring new members and whether they go on to complete a profile and be matched
• Comply with legal and regulatory obligations

We do not sell or rent your personal data to third parties.

3. AI-Generated Content and Matching

DCMA uses artificial intelligence (“AI”) to assist in generating profiles, insights, and match recommendations. While we strive for accuracy and fairness, AI-generated content may occasionally be imprecise or reflect bias.

You understand and accept that:

• We do not guarantee the accuracy, completeness, or appropriateness of AI outputs.
• You are responsible for decisions or actions based on AI recommendations.
• AI results may sometimes produce unexpected or incomplete content.

We continually review and refine our systems to improve fairness, reliability, and transparency in AI-based matching.

4. How We Share Information

We may share your information in the following limited circumstances:

• With potential matches, to facilitate introductions or compatibility assessments, in line with the information you choose to provide.
• With a concierge client — someone who pays us to be matched by hand and who is not a member of the app — where we are considering introducing you to them. That client may be shown your full profile, including your photos and your written answers. Where we make the introduction, we tell you that it is a concierge introduction.
• With trusted service providers who help us operate our website, analytics, communications, or payment systems under strict confidentiality obligations.
• With legal or regulatory authorities, if required to comply with applicable laws or to protect our rights, property, or users.

The specific service providers and partners we rely on today are:

• Vercel: hosting, edge delivery, and first-party traffic analytics (Vercel Analytics and Vercel Speed Insights).
• Supabase: authentication, database, and file storage for your account and profile data.
• PostHog (EU region, Frankfurt): pseudonymous product-analytics events. Configured so that no names, emails, phone numbers, or message content are transmitted.
• Google (Google Tag Manager and Google Analytics): traffic and marketing measurement. Google Tag Manager loads only on our public pages (home, about, FAQ, Play Cupid, sign-up, privacy, and terms) and not while you're signed in, apart from the sign-up page, where your sign-up is completed. It is never loaded on pages whose address contains a private link — such as a vouch invitation or a password-reset link. In the EU, UK, and EEA it is not loaded until you accept the cookie banner; anywhere, it is not loaded if you've chosen Reject or if your browser sends a Global Privacy Control signal (see section 7).
• Meta (Meta Platforms Ireland Ltd for users in the UK, EU, and EEA; Meta Platforms, Inc. elsewhere): the Meta pixel, loaded through Google Tag Manager, measures how our Facebook and Instagram ads perform — for example, that a sign-up happened after someone clicked an ad. When you create an account the pixel tells Meta that a sign-up happened, without your name, email address, or phone number. Like any website tag, the pixel can see the address of the page you're on (including any campaign tags in it), your IP address, and browser details, and it may set Meta's own cookies (such as _fbp and _fbc). Meta handles this information under its own terms and privacy policy. It follows the same rules as Google's tags, because it loads through Google Tag Manager: only on our public pages and not while you're signed in (apart from the sign-up page), never on pages whose address contains a private link, in the EU, UK, and EEA not until you accept the cookie banner, and nowhere if you've chosen Reject or your browser sends a Global Privacy Control signal.
• Our marketing agency (currently Performance Pilots): helps us measure which of our campaigns bring new members. They see only combined figures: the number of sign-ups and completed profiles by campaign, ad and country each month, and weekly sign-up totals, with any figure under 5 hidden. They never see your name, email address, phone number, photos, profile answers, or anything you typed yourself, and they never see a record for any individual member.
• Twilio: SMS delivery for phone verification and match notifications.
• Resend: transactional email delivery (sign-up confirmations, match updates, password resets).

All shared information is handled in accordance with relevant privacy regulations, and each processor is bound by a data-processing agreement that restricts use to the services we've engaged them for. Meta, as noted above, processes what its pixel collects under its own terms rather than only on our instructions.

5. Data Retention

We retain personal information only for as long as necessary to fulfill the purposes described above or as required by law. You may request deletion of your information at any time by contacting us. Marketing attribution information stored in your browser stops being used after 30 days and is removed from your browser when you create an account; the copy saved with your account is deleted along with your profile.

6. Your Rights

You have the right to:

• Access, correct, or delete your personal information
• Withdraw consent to data processing
• Request a copy of the data we hold about you

To exercise these rights, please contact us at setmeup@dontcallmeaunty.co.

7. Cookies and Analytics

We use cookies and similar technologies to analyze traffic, personalize content, and improve performance. You may disable cookies in your browser settings; however, certain site features may not function properly.

Essential cookies (always on): these are used by Supabase to keep you signed in, by our edge layer to remember your region (dcma_geo), and to remember your answer to the cookie banner and which version of it you answered (dcma_consent, dcma_consent_v). Without them, logging in and staying logged in will not work.

Optional analytics and advertising: if you're visiting from the EU, UK, or EEA, you'll see a banner asking whether to enable PostHog product analytics, Google's analytics and marketing measurement, the Meta pixel, and marketing attribution (below). All of these stay off until you accept — Google Tag Manager, which loads Google's and Meta's tags, is not loaded at all until then. Outside the EU/UK/EEA, pseudonymous analytics, the Meta pixel, and marketing attribution are enabled by default under a legitimate-interest basis. Wherever you are, choosing Reject turns them all off in your browser: PostHog stops, Google Tag Manager (and so the Meta pixel) is not loaded, and any marketing attribution record already saved in your browser is deleted. A small number of account events (for example, that your account was created) are still recorded from our own servers in PostHog against your account ID, without your name, email, or phone number.

Changing your answer: use the Cookie settings link in the footer (at the bottom of this page and our other public pages), or the Cookie Settings button on your account's Settings page, at any time, wherever you are, to accept or reject. If you switch from Accept to Reject, the page reloads so that tags already running stop, and we delete the cookies Google's and Meta's tags had set on our site (cookies they hold on their own domains can only be cleared through their settings or your browser). You can also clear this site's stored data or block cookies in your browser settings, or contact us.

Global Privacy Control: if your browser sends a Global Privacy Control signal, we treat it as an opt-out of sharing your information for advertising. We don't load Google Tag Manager or the Meta pixel. (We don't send server-side events to Meta for anyone.) Our own first-party measurement described below (the marketing attribution record kept on our site) is not sharing and still applies, unless you choose Reject.

Where tags run: the Meta pixel and Google Tag Manager load only on our public pages (home, about, FAQ, Play Cupid, sign-up, privacy, and terms). They never load on the pages you see while signed in, such as onboarding, your profile, or your matches; the one exception is the sign-up page itself, where the sign-up is completed after your account has been created. They also don't load on a sign-up page opened from a friend's invite link, so your friend's referral code isn't passed to them, and if you move from a public page to a signed-in page the page reloads without them.

Marketing attribution: to learn which channels and ads bring people to DCMA, when you arrive we may save a small record of how you got here in your browser's local storage (dcma_attr and dcma_utm): the campaign tags on the link you followed (such as utm_ tags and Meta campaign, ad set, and ad IDs); whether the link carried an ad-click identifier from Meta, Google, or TikTok (we note only which kind, not the identifier itself); the domain of the website that sent you (not its full address); the path of the first page you landed on (not its query string); and whether you were browsing inside the Instagram, Facebook, TikTok, LinkedIn, or Snapchat app. If you arrived through a friend's invite link, we save their referral code the same way (dcma_ref) so they get credit. This record is used for up to 30 days and is removed from your browser when you create an account. When you sign up, it is saved with your account together with how you signed up (email or Google), the country your IP address indicated at the time, and your answer to the cookie banner. Only our team can access your individual record (our marketing agency sees it only as part of combined figures; see section 4), and we use it only for our own measurement of which channels bring members and whether they go on to complete a profile and be matched. We don't sell this record or send it to advertising platforms. If you're in the EU, UK, or EEA and don't accept the banner, or, wherever you are, you choose Reject, nothing is stored in your browser, and at sign-up we record only how you signed up, your country, that you didn't consent, and a friend's referral code if you arrived through their invite link (kept only for your current browser session, so the sign-up you started can credit them). If you choose to tell us how you first heard about DCMA (an optional question after you finish your profile), we store your answer with your account and use it only for the same measurement; it is never shared with advertising or analytics partners.

What analytics and advertising partners receive. We don't include your name, email address, phone number, or message content in the events we send to PostHog, Google, or Meta. Our product-analytics pipeline has technical controls that strip these before events leave the browser or our servers, and PostHog events are keyed to your internal profile ID. Google's and Meta's tags do receive the address of the pages you visit, your IP address, and browser details, which is why they are switched off entirely on pages whose address contains a private link.

8. Data Security

We apply reasonable administrative, technical, and organizational measures to protect your data against loss, misuse, or unauthorized access. However, no system is completely secure, and we cannot guarantee absolute protection.

9. International Data Transfers

As DCMA operates globally, your information may be transferred and processed outside your country of residence. We take steps to ensure that such transfers comply with applicable data-protection laws and include appropriate safeguards.

10. Updates to This Policy

We may update this Privacy Policy from time to time. The updated version will be indicated by a revised “Last Updated” date. Your continued use of our services after any changes signifies your acceptance of the updated policy.

11. Contact Us

If you have questions or concerns about this Privacy Policy, please contact us at: