Privacy Policy

MatchXMatch ("we", "us", or "the App") is a mobile dating app where users connect by playing short games together before revealing their photos. This policy explains what data we collect, why, and your rights over it.

For any privacy-related question or request, contact us at privacy@matchxmatch.app.

2.1 Information you provide

• Account: email address, password (stored hashed), username, gender, who you're interested in, date of birth, phone number.
• Profile: bio, city (set via a one-time GPS lookup at sign-up — see Section 5 for how this works; not continuously tracked), social media links, profile cartoon avatar configuration, profile photos you upload.
• Q&A answers: answers to profile questions you optionally fill in.
• Messages and game data: messages sent in matches, drawings, game answers, attached media (photos in chat).
• Reports and feedback: reports you file against other users, feedback you submit to us, accounts you block.

2.2 Information collected automatically

• Device push token: a unique identifier issued by Apple Push Notification Service (APNs) or Firebase Cloud Messaging (FCM) so we can send you notifications.
• Diagnostic logs: app crash logs and error events, which may include your user identifier at the time of capture. These are anonymized when your account is deleted.
• Match metadata: timestamps, match scores, in-app credits and credit transactions, karma score, match preferences.
• Advertising identifier (only when you choose personalized ads): when you opt in to personalized ads in the mobile app, Google AdMob reads your device's advertising identifier — Apple's IDFA on iOS, Google's Advertising ID (GAID) on Android — to deliver and measure ads. You can reset or limit this identifier in your device settings, or change your in-app choice at any time. See Section 7 for full details.

2.3 We do NOT collect

• Continuous or background location. We use a one-time GPS reading at sign-up to determine your city (see Section 5); we never track your location during app use or in the background.
• Contacts, calendar, microphone, or camera-roll access beyond photos you explicitly select for upload.

• To create and operate your account.
• To match you with other users based on your stated preferences (gender, age range).
• To deliver in-app gameplay, messages, and notifications.
• To enforce community safety (process reports, prevent abuse, suspend accounts that violate the Terms).
• To send transactional emails (account verification, password reset, account-deletion confirmation).
• To diagnose crashes and improve stability.
• To display advertising in the mobile app via Google AdMob. You can choose personalized or non-personalized ads, and change your choice anytime from Settings → Privacy Choices. See Section 7 for full details.

We do not sell your personal data to data brokers. We do use Google AdMob to display in-app advertising — see Section 7 for full details and your choices. If we ever add additional advertising or analytics partners, we will list them in Section 4 and update this policy before they begin processing your data.

We rely on the following services to operate the app. Each handles only the data necessary for its function:

• Supabase — database, authentication, and file storage for your profile, photos, messages, and matches. Data resides in the EU (Frankfurt region).
• Firebase Authentication (Google) — phone-number verification (SMS code delivery). Your phone number is sent to Firebase for this single purpose.
• Resend — delivery of transactional emails (verification, password reset, account-deletion confirmation).
• Apple Push Notification Service / Firebase Cloud Messaging — delivery of push notifications to your device.
• Cloudflare — DNS, email routing for our support inbox, and website hosting (this page).
• Railway — hosting of our backend API server.
• Apple Maps geocoding (iOS) / Google Maps geocoding (Android) — one-time reverse geocoding during sign-up: your device sends GPS coordinates to your operating system's mapping service to look up the city name. We store only the resulting city name, never the coordinates. See Section 5.
• Google AdMob (Google LLC) — display of in-app advertising on iOS and Android. When you consent to personalized ads, AdMob receives your device's advertising identifier (IDFA / GAID), IP address, ad interaction events, and approximate location derived from IP. Without your consent, only non-personalized ads are shown and the minimum data required to do so is shared. Google's ad practices: policies.google.com/technologies/ads. See Section 7.

AdMob is the only advertising partner integrated at this time. We may add additional advertising or analytics partners in the future; if we do, we will list them above and update this policy before they begin processing your data.

During sign-up, we ask for one-time access to your device's GPS in order to determine the city you live in. The flow:

• You tap the "📍" button in the profile setup screen.
• The app requests foreground location permission from your operating system. If you decline, you will not be able to complete sign-up. We deliberately do not offer a manual city entry: requiring GPS ensures that the city on your profile is accurate, which matters because city is a primary factor when we suggest matches near you. If you need help, contact privacy@matchxmatch.app.
• If you grant permission, the app reads your current coordinates once (using balanced accuracy — city-block level, not exact).
• The coordinates are sent to your operating system's mapping service — Apple Maps on iOS, Google Maps on Android — to convert them into a human-readable city name (this is called "reverse geocoding").
• We store only the resulting city name on your profile. The raw coordinates are not sent to our servers and are not retained on the device after the lookup.

We do not request GPS access again after sign-up. We do not track your location while you use the app, and we do not collect background location.

This website (matchxmatch.app) does not set any HTTP cookies. When you visit our landing, privacy, terms, or account-deletion pages, your browser does not receive a Set-Cookie header from our servers.

We do use the following client-side storage. The first three are strictly necessary for the function you requested and are notused for advertising, profiling, or cross-site tracking. The last one (advertising identifiers) only applies if you actively consent to personalized ads inside the mobile app:

• Browser localStorage (web): on the account-deletion page we remember your last language choice (TR, EN, or IT) in a key called mxm-lang, so the page opens in the language you previously selected. You can clear it any time from your browser's site-data settings.
• On-device secure storage (mobile app): the iOS and Android apps store your sign-in tokens in the platform's secure store (Apple Keychain / Android Keystore) so you stay signed in between sessions. Tokens are removed when you sign out or delete your account.
• Necessary infrastructure cookies: our hosting provider (Cloudflare) may temporarily issue technical cookies for bot protection or connection routing on attacked or rate-limited endpoints. These are not under our control, contain no personal identifier, and exist only for the duration of the request.
• Advertising identifiers (mobile app only): when you use the iOS or Android app and consent to personalized ads on the in-app consent screen, the Google AdMob SDK reads your device's advertising identifier (IDFA on iOS, Google Advertising ID on Android) to deliver and measure ads. This identifier is not stored on our servers; it is provided to Google AdMob only while ads are being delivered. You can reset or revoke this identifier in your device settings, and change your in-app choice at any time from Settings → Privacy Choices.

The website itself remains tracker-free and does not display advertising. Advertising appears only in the mobile app. See Section 7 for what data is involved and how to control it.

7.1 Why we show ads

MatchXMatch is free to use. Ads help cover the cost of running the matchmaking servers, photo storage, push notifications, and customer support.

7.2 Who shows the ads

We work with Google AdMob (operated by Google LLC) to deliver advertising in the mobile app. AdMob is the only ad partner integrated at this time. If we add additional ad networks in the future, we will list them in Section 4 and update this policy before they begin serving ads.

7.3 Personalized vs non-personalized ads

• Personalized ads use your device's advertising identifier (IDFA on iOS, GAID on Android) to show ads that may be more relevant to your interests. AdMob may combine this identifier with other data Google holds about you for ad personalization and measurement.
• Non-personalized ads show only based on contextual signals — your country and the app you are using. No advertising identifier is shared and no behavioral profile is built.

7.4 How you choose

On first launch of the mobile app, we show a consent screen powered by Google's User Messaging Platform (UMP) where you can pick between personalized and non-personalized ads.

You can change your choice anytime from Settings → Privacy Choices in the app — this re-opens the same consent screen.

7.5 Device-level opt-out

You can also limit ad tracking at the operating-system level:

• iOS: Settings → Privacy & Security → Apple Advertising → toggle off "Personalized Ads". Also: Settings → Privacy & Security → Tracking → toggle off "Allow Apps to Request to Track".
• Android: Settings → Google → Ads → "Delete advertising ID" or "Opt out of personalized advertising".

7.6 Children

The app is restricted to users 18 years of age or older. We configure AdMob with Tag for Child-Directed Treatment (TFCD) = false because the app is not directed to children. Ads served to our users are intended for adult audiences.

7.7 Where ads appear

• Interstitial ads shown during the transition between matches.
• Rewarded ads are optional — you can choose to watch one in exchange for in-app credits.

We do not show ads in the middle of a game, during a chat, or during the photo-reveal moment.

7.8 EU, UK, Switzerland, and Turkey

If you are located in the European Economic Area, the United Kingdom, Switzerland, or Turkey, your active choice on the consent screen is required before personalized ads are shown. If you decline personalized ads, you will still see non-personalized ads unless you also opt out at the device level (see 7.5).

Your in-app choice is stored on your device only. Reinstalling the app resets your choice, and you will see the consent screen again on next launch.

7.9 Where to learn more

• Google's data and ad practices: policies.google.com/technologies/ads
• Google AdMob privacy information: support.google.com/admob/answer/6128543

Profile photos you upload are stored privately in our storage bucket and shared only with users who match with you and only after both of you choose to reveal them. Media you attach to chat messages is visible only to your match partner.

When you delete a message or your account, the corresponding media files are removed from our storage.

• Account and profile data are retained as long as your account is active.
• Inactive matches may be archived and purged according to our retention policy (typically after extended inactivity).
• Push notification tokens are removed when you uninstall the app or disable notifications.
• Diagnostic logs are retained for a limited time for stability analysis and are anonymized when your account is deleted.

Depending on where you live, you may have the following rights:

• Access — request a copy of the data we hold about you.
• Correction — edit your profile in the app or request a correction.
• Deletion — delete your account at any time (see Section 11).
• Restriction / objection — ask us to limit how we process your data.
• Portability — receive a machine-readable copy of your data.
• Complaint — lodge a complaint with your local data-protection authority.

To exercise any of these, email privacy@matchxmatch.app. We will respond within 30 days.

You can permanently delete your account and associated data using any of the methods on our account-deletion page:

• From inside the app (Settings → Delete My Account).
• Through the self-service web form (no app required).
• By email to matchmatchx@gmail.com.

Deletion removes your profile, photos, matches, messages, credits, and authentication record. Anonymized crash logs may be retained for stability analysis.

MatchXMatch is for users 18 years of age or older. We do not knowingly collect data from anyone under 18. If you become aware that a minor has registered, contact us and we will remove the account.

We use industry-standard measures including TLS encryption in transit, encrypted storage at rest (Supabase), hashed passwords, and row-level security policies in our database to limit access to your data. No system is perfectly secure, but we work to minimize risk.

Our primary data hosting is in the European Union (Frankfurt). Some sub-processors (e.g., Firebase, Apple/Google push and mapping services, Google AdMob) may operate globally. Where required, transfers are protected by appropriate safeguards such as Standard Contractual Clauses.

We may update this policy from time to time. The "Last updated" date at the top reflects the most recent change. Material changes — including new advertising or analytics partners — will be announced in the app and listed in Section 4 before they take effect.

Questions or requests: privacy@matchxmatch.app.