courtme.ai: Privacy Policy
Effective Date: 2026-07-13
Last Updated: 2026-09-27
Entity: CourtMe, Inc. (Delaware C-Corporation; principal place of business: Austin, TX)
Contact: privacy@courtme.ai
1. Plain-language summary (TL;DR)
- We collect personal information, including sensitive data like sexual orientation (inferred from your preferences and matches), precise location, and gender identity, to run AI-powered, event-scoped matching across networking, friendship, and romance intents. A citywide dating mode is described in this Policy but is not yet available (see Section 2.5).
- We send your data to AI providers to run matchmaking while you are using courtme, and we do not use your data to train AI models. See Sections 3.2 and 8.
- Your messages and your conversations with our AI matchmaker are stored on our servers (they are not end-to-end encrypted), and trained staff may review them for safety, support, moderation, and to improve matching. Each such review is purpose-limited and audit-logged. See Sections 3.6 and 9.
- We share data with advertising partners (Meta, Google) for marketing. Under California law (CCPA/CPRA), this is considered a "sale" / "share" of personal information. You can opt out via the "Do Not Sell or Share My Personal Information" link in our footer.
- You have rights to access, correct, delete, and port your data. See Section 7.
- We do not knowingly collect data from anyone under 18.
- We retain data only as long as needed. See Section 9.
This summary does not replace the full Policy below.
2. Information we collect
2.1 Information you provide
- Name, email, phone number
- Date of birth (our age gate rejects anyone under 18; it is not checked against an ID at IRL events)
- Gender and gender identity
- City and approximate location
- Photos
- Profile information, including biographical text, match preferences, "tell your AI matchmaker" prompts, personality questionnaire answers, pain-point questionnaire answers, and your intent for an event (networking, friendship, romance)
- Payment information (processed by Stripe; we do not store full card numbers)
- Date feedback, reports, and unmatch reasons
- Communications you send to courtme (support emails, in-app reports)
- Messages and content you exchange with other users (one-to-one match chats, event chats, and group chats)
- Your conversations with our AI matchmaker ("Courtney"), including onboarding and intake interviews conducted by voice and/or text
- Audio recordings and transcripts of your voice interactions with our AI matchmaker (voice intake)
2.2 Information collected automatically
- Device and technical data: device type, OS, app version, IP address, language preferences, time zone
- Usage data: pages and screens viewed, actions taken (matches approved, dates booked, messages opened), session duration, referral source
- Location data: city- and ZIP-level location at minimum; precise GPS location if you grant permission (for venue suggestions and date coordination)
- Cookies and similar technologies: see Section 6
2.3 Information from third parties
- Photo moderation: AWS Rekognition returns content-classification results and face-detection quality results for the photos you upload. We do not use Rekognition, or any other vendor, to match your face against an identity document (see Section 2.5)
- Advertising partners: Meta, Google, and similar may share back conversion/audience data
- Referrals: when another user refers you, we may receive your contact info from them. When an event host refers another host, we record which host's referral code or event brought the new host in, so we can credit the referrer
- Event hosts - billing and referral fraud checks: if you run paid events as a host, Stripe returns your payment status and receipts. To stop referral credits being claimed by the same person twice, we also keep a one-way hash (SHA-256) of the device identifier you paid from and of the card fingerprint Stripe assigns to your card. We never store the raw device identifier or card fingerprint, and the hashes are used only to compare referrals against each other
- Event link scans: when anyone opens a courtme event link (www.courtme.ai/e/…), we log the event code, the browser or app identifier (user agent), and the referring page, so hosts can see how many people scanned their QR code. No name or account is attached to that log
Automated photo checks. Every photo you upload is run through automated checks, including face detection, to confirm the photo is usable and meets our content guidelines. The face-detection output is discarded immediately. We never retain it, never store it against your account, and never use it to identify you or anyone else. We do not currently run identity face-matching, and we do not generate or store biometric identifiers anywhere in courtme. When dating mode launches, the identity verification it requires will be governed by our Biometric Data Notice (see Section 2.5). IRL events do not use it.
2.4 Sensitive Personal Information (SPI)
We collect or infer the following categories defined as Sensitive Personal Information under California CPRA (and equivalent under other state laws):
- Precise geolocation (when you grant permission)
- Sexual orientation (often inferred from match patterns or preferences you provide)
- Gender identity (when you provide it)
- Racial or ethnic origin (if you choose to provide it)
- Biometric identifiers (facial geometry) - not collected today. Identity verification is not available in the current product (Section 2.5). When dating mode launches, the selfie-to-ID face match it requires will be governed by our Biometric Data Notice, and we will never use biometric data for advertising or AI training. IRL events do not use it.
- Account credentials (in combination with passwords)
We use SPI only for the purposes you would reasonably expect from a matchmaking product (matching and safety, and, for the interests you write in intake, choosing sponsor booth cards and booth recommendations as described in Section 12A) and not for inferring characteristics about you for any other purpose. You may limit our use of SPI by contacting privacy@courtme.ai.
2.5 Features described in this Policy that are not yet available
courtme today is event-scoped: you join a specific event and are matched with other attendees of that event. The features below are described elsewhere in this Policy, or exist in the app in a disabled state, and are not available to you today. We do not collect the data they would involve, and we will update this Policy and its effective date before any of them launches.
- Citywide dating mode - matching outside an event, date coordination, and post-date feedback.
- Identity verification (required in dating mode when it launches; not used at IRL events) - government ID via Stripe Identity, and the selfie-to-ID face match that will generate biometric data under our Biometric Data Notice. We do not ask for, receive, or store a government ID or a verification selfie.
- Emergency contact and safety check-in SMS - including any phone number belonging to a third party. We do not ask for or store an emergency contact.
- Token purchases and in-app purchases - courtme has no working in-app purchase. Payments that do happen today are event and subscription charges made by hosts through Stripe. Our Token Terms describe a mode that is not yet available.
3. How we use your information
3.1 To provide the service
- Create your account and build your profile
- Run our AI matchmaking system to suggest matches
- Choose which sponsor booth cards to show you at an event, send you a sponsored booth recommendation in your Courtney chat, and run the booth chats you choose to open (Section 12A)
- Respond to reports, run moderation, and act on safety incidents
- Prevent fraud, abuse, and ban evasion
- Process payments - event and subscription charges made by hosts, through Stripe
- Coordinate dates and run safety check-ins - dating mode, not yet available (Section 2.5)
3.2 To improve the service, and how AI processes your data
We do not use your data to train AI models - ours or anyone else's. courtme does not train, fine-tune, or otherwise build AI models on your information.
What we do instead is send your information to AI providers at the moment you use a feature, so they can return a result for you. That is inference, not training:
- Your profile content, questionnaire answers, and "tell your AI matchmaker" prompts are sent to Anthropic to write your profile summary and to score and rank the other attendees at your event.
- Short text drawn from your profile is sent to Voyage AI, which returns a numeric representation (an "embedding") used to shortlist who to rank at larger events.
- Your voice intake is streamed to LiveKit and Deepgram so it can be transcribed, and so the matchmaker can speak back to you, in real time.
Each of these providers is a subprocessor bound by the data processing agreement described in Section 4.1. We keep the inputs and outputs of these calls on our own systems and retain them under Section 9.
To measure and improve how well matching works, we use de-identified or aggregated statistics - for example match rates, meet rates, and how often a suggested match was approved - which are not linked to you.
If we ever decide to train models on user data, we will update this Policy and its effective date, tell you, and offer an opt-out before doing so. We would never use biometric data (facial geometry) or voice-identification data for model training in any case.
3.3 To communicate with you
- Transactional emails and push notifications (event reminders, matches, messages)
- Lifecycle marketing (you may opt out of marketing at any time)
- Support and policy responses
- Product updates
3.4 To market courtme
- Run advertising campaigns (Meta, Google, TikTok)
- Build "lookalike" audiences based on existing users
- Measure ad effectiveness and attribution
3.5 To meet legal and safety obligations
- Respond to law enforcement requests (with legal process)
- Investigate safety incidents and abuse reports
- Defend legal claims
- Comply with applicable laws
3.6 To review communications for safety, support, and product quality
Your in-app messages are stored on our servers and are not end-to-end encrypted. Authorized courtme personnel may review the content of:
- messages you exchange with other users (match, event, and group chats), and
- your conversations with our AI matchmaker ("Courtney"), including intake interviews,
for safety and abuse investigation, fraud and ban-evasion prevention, moderation, responding to your support requests and disputes, product-quality review, and improving our matching and AI systems. (We do not train AI models on your content at all - see Section 3.2 - but the safety, support, and legal review described here is separate from that and continues regardless.)
This internal access is role-limited, purpose-scoped, and audit-logged: only trained Trust & Safety and product/research staff may reach this content, each access is tied to a specific purpose (for example safety, moderation, support, research, product quality, or legal) and a stated reason, and every access is recorded in an internal audit log. Retaining messages on our servers rather than end-to-end encrypting them is what makes this safety and support review possible, and is standard practice for dating and messaging services; the access controls and audit logging above are the safeguards on it.
4. Sharing of information: including SALES/SHARES under California law
4.1 Service providers (subprocessors)
We share personal information with the vendors below, each bound by a data processing agreement (DPA) to use the data only to provide services to us. We maintain and update this list as our subprocessors change.
| Subprocessor |
Purpose |
Data involved |
| Supabase |
Database, authentication, file storage |
Account, profile, messages, photos |
| Anthropic |
AI matchmaking, bio generation, content-moderation classifiers |
Profile, prompts, messages/intake (pseudonymized where feasible) |
| Voyage AI |
Text embeddings used to shortlist which attendees to rank |
Short text drawn from your profile |
| AWS - Amazon Rekognition |
Photo content moderation and face-detection quality checks |
Photos |
| Stripe |
Payments and host billing |
Payment info (we do not store full card numbers) |
| Twilio |
SMS: phone verification codes. Safety check-in and emergency-contact SMS belong to dating mode and are not yet available (Section 2.5) |
Your phone number |
| LiveKit |
Real-time voice transport for AI intake |
Voice audio stream |
| Deepgram |
Speech-to-text transcription of voice intake, and text-to-speech for the AI matchmaker's voice |
Voice audio, transcripts, the matchmaker's reply text |
| PostHog |
Product analytics |
Usage/event data, identifiers |
| Sentry |
Error and crash monitoring |
Diagnostics, IP address, identifiers |
| Inngest |
Background job orchestration |
Data needed to run scheduled/async jobs |
| Resend |
Transactional and lifecycle email |
Email address, message content |
| Vercel |
Web hosting |
IP address, request logs |
| Expo / EAS |
Mobile builds and push-notification delivery |
Device/push tokens |
| Google |
Places API (venue data); Analytics/Ads (see 4.2) |
Venue queries; usage/conversion data |
| Apple / Google (app stores) |
App distribution, push delivery, and age-signal where available. courtme has no in-app purchase (Section 2.5) |
Push tokens, age category |
We do not use OpenAI as a subprocessor at this time; if that changes, we will update this list.
4.2 Advertising and analytics partners: TREATED AS "SALE"/"SHARE" UNDER CCPA/CPRA
We share information with the following partners for advertising and analytics. Under the California Consumer Privacy Act / CPRA, the activities below are legally categorized as "sale" or "sharing" of your personal information, even though no money changes hands directly for the data:
- Meta (Facebook/Instagram), via Meta Pixel and Conversions API. We share signup events, page views, and audience data for ad targeting, optimization, and lookalike modeling.
- Google: Google Analytics and Google Ads. We share usage and conversion data.
- TikTok (if active): TikTok Pixel for ad attribution.
- Other ad-tech partners as we onboard them.
You have the right to opt out of this sale/sharing. Use the "Do Not Sell or Share My Personal Information" link in our footer, or email privacy@courtme.ai. We will honor Global Privacy Control (GPC) signals as opt-outs.
We do not sell or share Sensitive Personal Information for purposes other than those you'd reasonably expect.
4.3 Other users
- Your profile, photos, and AI-generated bio are visible to your matches
- Date coordination details are shared with the user you're going on a date with (dating mode; not yet available - Section 2.5)
- Reports you submit may be reviewed by our moderation team and, in serious cases, shared with law enforcement
- Event sponsors and exhibitors (booth staff): only if you open a chat with a sponsor's booth by tapping "Say hi", that sponsor's booth staff receive your first name, your age, an internal account ID (a random code that does not by itself reveal who you are), and the messages in that chat (Section 12A). Sponsors pay for the booth placement, not for your data, and receive nothing about you unless you open a chat.
4.4 Business transfers
If courtme is acquired, merged, or sells assets, your data may transfer to the acquirer. We will notify you before the transfer if your rights would meaningfully change.
4.5 Legal disclosure
We disclose data when legally compelled (subpoena, court order, government request) and when necessary to investigate suspected fraud, threats, or violations of our terms.
5. Automated decision-making (AI matchmaking)
Our matchmaking system uses automated processes, including AI / large language models, to score and suggest matches. Specifically:
- We generate compatibility scores using AI prompts that consider your profile, preferences, and prior decisions
- We do not make decisions about you with legal or similarly significant effect using AI alone (e.g., we do not deny services, employment, or credit based on AI)
- You may request a human review of any AI-driven decision affecting you (e.g., if a match was removed for moderation reasons) by emailing privacy@courtme.ai
If you are an EU/UK resident, you have additional rights under GDPR Article 22 regarding automated decision-making. See Section 7.4.
6. Cookies and similar technologies
We use cookies, SDKs, and similar technologies for:
- Essential: session, authentication, fraud prevention (always on)
- Performance: analytics (Google Analytics, PostHog)
- Advertising: Meta Pixel, Google Ads tag, TikTok Pixel
You can manage non-essential cookies via our cookie banner on first visit and through your account settings. You can also use browser controls or Global Privacy Control (GPC) signals.
7. Your privacy rights
Depending on where you live, you may have the following rights:
7.1 All users
- Access: request a copy of personal information we hold about you
- Correct: fix inaccurate data
- Delete: request erasure (subject to legal/safety exceptions)
- Port: receive your data in a machine-readable format
- Object/Limit: to certain uses including marketing and sale/share
7.2 California residents (CCPA/CPRA)
- Right to know categories and specific pieces of personal information collected
- Right to opt out of "sale" and "sharing" (advertising, see Section 4.2)
- Right to limit use of Sensitive Personal Information
- Right to delete
- Right to correct
- Right to data portability
- Right to non-discrimination for exercising these rights
To submit a request, use the "Do Not Sell or Share My Personal Information" link or email privacy@courtme.ai. We respond within 45 days (extendable by 45 with notice).
7.3 Texas, Colorado, Connecticut, Virginia, Utah, and other state law residents
You have substantially similar rights under your state's law. Submit requests to privacy@courtme.ai.
7.4 EU/UK residents (GDPR)
- All rights above plus the right to object to processing, the right to restrict processing, and the right to lodge a complaint with your data protection authority
- Right to human review of automated decisions (Article 22)
- Our lawful bases for processing: contract performance (running the service), legitimate interests (safety, fraud prevention, improvement), consent (marketing, SPI uses requiring consent), and legal obligations
8. AI processing, and opting out of "sale"/"share"
AI training: there is nothing to opt out of - we do not use your data to train AI models (see Section 3.2). AI providers process your data only at the moment you use a feature, to return a result to you. If we ever decide to train models on user data, we will update this Policy and its effective date, tell you, and offer an opt-out first. We would never use biometric data (facial geometry) or voice-identification data for model training in any case. To object to AI processing generally, email privacy@courtme.ai.
Sale/Share opt-out: Use the "Do Not Sell or Share My Personal Information" link in our footer, or send GPC signals via your browser. We honor GPC.
9. Data retention
We keep personal information only as long as needed for the purposes in this Policy, then delete or de-identify it. When you delete your account, we remove your data on the timeline below, subject to the exceptions that follow.
9.1 Standard timelines
- Active accounts: while your account is active.
- Inactive accounts (no login for 24 months): we may delete or anonymize the account.
- On account deletion - your solo data (profile, photos, AI-matchmaker "Courtney" intake and transcripts, your own settings): soft-deleted immediately and purged from production systems within 30 days, and from backups on our normal backup cycle.
- Two-person chats (match, event, and group messages): because these conversations also belong to the other participant(s), when you delete your account we redact your identity from shared threads (removing your name and profile), but the conversation content may be retained for the other participant and for safety, subject to the exceptions below. Messages are retained server-side and are not end-to-end encrypted (see Section 3.6).
- Booth chats (Section 12A): deleted with your account, on the solo-data timeline above.
- Voice-intake audio: raw audio is deleted shortly after transcription; the transcript follows the Courtney-intake timeline above.
- IP address and authentication logs: retained up to 90 days for security and fraud prevention, then purged (unless subject to a preservation request or legal hold).
9.2 Exceptions - data we retain after deletion
- Financial records (tax/audit): on deletion we strip identity from token-transaction and purchase-receipt records and retain the de-identified records (amounts, dates, tax fields) for accounting, tax, and audit purposes for the period required by law (generally around 7 years). De-identification is designed to be irreversible, and these records are no longer linked to you.
- Safety records: reports, safety-related blocks, safety incidents, ban records, and their associated chats are retained after deletion for safety, abuse-prevention, and legal-defense purposes - at least 1 year for ordinary matters and up to 7 years (or the applicable limitations period, whichever is longer) for serious incidents (e.g., assault, threats, sex-offender enforcement). Child-safety (CSAM) material is handled and preserved as required by 18 U.S.C. §2258A.
- Legal hold: anything subject to an active report, investigation, litigation, subpoena, or law-enforcement or legal-preservation request is retained until the matter and any preservation obligation ends.
- Mutual connections and their chats: when you and another attendee match, that connection and its chat thread persist after the event ends. They remain until either person unmatches or blocks the other, moderation removes them, or either account is deleted (see Section 12A). Confirming "We met" is a quality metric only and does not affect how long anything is kept.
- Aggregated and de-identified statistics used to measure and improve the service may be retained indefinitely. They are not linked to you, and they are not used to train AI models (see Section 3.2).
Internal staff access to retained messages and intake is audit-logged and purpose-scoped (see Section 3.6).
10. Security
We use industry-standard measures including encryption at rest and in transit, access controls, and audit logging. No system is perfectly secure. If we discover a breach of your personal information, we will notify you and applicable regulators as required by law.
11. Children
courtme is 18+ only. We do not knowingly collect data from anyone under 18 years of age. If the date of birth you give us (or any other signal) indicates you are under 18, we block account creation and purge the associated sign-up data - including email address and phone number - from our systems, retaining only the minimal, non-identifying information needed to prevent immediate re-registration. If we otherwise learn we have collected data from a minor, we will delete it. If you believe a minor is using courtme, contact safety@courtme.ai.
12. International users
courtme is operated from the United States. If you access courtme from outside the US, your data will be transferred to and processed in the US.
For EU/UK users, we use Standard Contractual Clauses (SCCs) or equivalent safeguards for transfers outside the EEA/UK.
12A. IRL Mode & Events
When you join courtme at a partner event ("IRL Mode") - e.g., by scanning an event QR code or entering a join code - the following applies in addition to the rest of this Policy:
- What we collect at events: the event you joined and the host/QR code that referred you, the profile information you create (including selected intent - networking, friendship, romance), your in-app activity at the event, and the standard account, device, and usage data in Section 2.2.
- Event location: we determine your event association from the QR code or join code you scan or enter - not from continuous or precise location tracking. If you separately grant precise-location permission (for example, for venue suggestions), that is optional and is Sensitive Personal Information subject to your right to limit its use (Section 2.4).
- Events expire; connections do not. The event closes - browsing other attendees and making new matches ends when the event's window closes. Every mutual match you make, and its chat thread, stays with you after the event ends, and remains until either person unmatches or blocks the other, moderation removes it, or either account is deleted. Confirming in-app that you met in person ("We met") is a quality metric reported to the host in aggregate only; it does not decide whether a match is kept. Your account, profile, and messages are also retained, subject to Section 9, Data Retention.
- Meet requests are visible to the person you ask. When you send a "want to meet" request, the other attendee sees your event profile and that you asked, right away - the request is not hidden until it is mutual. They can accept, dismiss, block, or report it; you only see that your request was sent. A block removes your request from their view and stops you seeing each other at the event.
- What the host sees: event hosts receive aggregate statistics only - scans, signups, intake completed, meet requests sent, matches, groups, how many pairs confirmed "We met", and, if the host answers it, a headcount estimate and join rate - in the host dashboard and in an automated report emailed to the host after the event. Hosts do not receive your name, contact details, profile, or messages.
- Event & promotional notifications: we may send in-app push notifications about future events from the host whose event you joined, and about courtme. You can opt out in your notification settings (service/safety messages may still be sent).
- In-app advertising: we may show advertising or sponsored placements in the app, handled under the advertising and "sale/sharing" disclosures in Sections 6–8; your opt-out rights there continue to apply. Sponsor booth cards are covered by the next item.
- Sponsor booth cards and booth chats: at some events, sponsors or exhibitors have a booth, and the app may show you up to two booth cards labeled "Sponsored". We choose which cards you see inside courtme, by matching each booth's keywords (for example, "running") against the interests from your intake that are shown on your event profile; a booth with no keywords is shown to everyone. We do not use your romance or dating preferences to choose booth cards. The interests we match are free text from your intake, so if you mentioned something sensitive there (for example, your religion or your health), it could match a booth keyword. Sponsors are never told who saw their card or whose interests matched. For some of these booths, Courtney, our AI matchmaker, may also send you one message in your Courtney chat recommending that booth, labeled "Sponsored". It uses the same keyword matching as booth cards (only a booth with a keyword that matched your interests can be recommended), is written from a fixed template (not generated by AI), names the booth's own keyword that matched rather than your own words, is sent at most once per event, and is never sent as a push notification or email. Sponsors are not told that it was sent or to whom. The message has the same "Say hi" button as a card. Nothing about you goes to a sponsor unless you tap "Say hi", which opens a chat with that booth: from then on the sponsor's booth staff see your first name, your age and the messages in that chat, and can reply. They do not see your photos, profile, intake, contact details or anything else about you (other than the internal account ID described in Section 4.3), and they cannot see other attendees through the booth. Booth staff use their own courtme accounts, and their messages appear under the booth's name. You can hide a booth at any time, which ends the chat, and once the booth's staff have replied you can report them from the chat. Because you choose to open the chat, this is a disclosure you direct, not a "sale" or "share" of your personal information. To be left out of booth matching altogether, including these recommendations, email privacy@courtme.ai.
13. Changes to this Policy
We may update this Policy. Material changes will be communicated by email and in-app notice. Continued use after the effective date constitutes acceptance.
14. Contact
For EU residents, our EU representative is: not yet appointed; EU users may contact privacy@courtme.ai.