RanMatch Privacy Policy and Regional Privacy Notice

• Document version: 2026-10-16
• Last updated: October 16, 2026
• Application: From the date this version is presented to you in the app; any required acceptance or explicit consent is obtained separately before the relevant operation.

1. Scope and controller

This Privacy Policy explains how personal data is collected, used, disclosed, retained, and deleted when you use the RanMatch mobile application and related services (the “Service”).

The controller of your personal data is:

Halil İbrahim Tayfur

• Privacy and support email: support@ranmatch.com
• Website: https://ranmatch.com

The “Regional provisions” section describes additional rights that may apply based on where you live.

This Policy provides information about processing. Acknowledging that it was read or accepting the Terms is not explicit consent to all processing. A device permission for camera, microphone, or location does not by itself satisfy every legal consent requirement.

2. Personal data we collect

2.1 Account and authentication data

• full name or profile name;
• email address;
• date of birth and age-eligibility information;
• Firebase-generated user ID and account timestamps;
• session, authentication, and account-security information;
• age declaration, timestamps for Terms acceptance and Privacy Notice acknowledgement, document versions, and app-language information.

Your password is processed by Firebase Authentication. RanMatch does not see or store your plaintext password.

2.2 Profile and preference data

Depending on your choices, you may provide:

• profile photos and biography;
• gender and participation preferences;
• school/education, work, height, languages, and interests;
• lifestyle fields such as alcohol and smoking preferences;
• sport or activity type, skill level, weekly frequency, goals, and participation style;
• profile visibility and discovery preferences.

Parts of your profile may be visible to other RanMatch users. The “Who can see information?” section explains how visibility works.

2.3 Location data

If you grant permission, we may receive device location. This can include:

• location while using the app for proximity and distance features;
• a more precise but rounded last location, accuracy, and timestamp in the private account record;
• an approximate discovery location reduced to an area of roughly one kilometer;
• country, city, and district selected for an activity;
• exact meeting latitude/longitude that you share with activity members.

An exact meeting point is not added to the general discovery profile; it is shared with users authorized to access the relevant activity. You can disable location permission in device settings, but proximity, distance, or location-based features may then be unavailable.

If you use Travel mode, your selected country, city, and approximate city-center location are stored in your account and used for discovery, ranking, and distance displays. This is not your actual device location. Your selected city and Travel mode status may be shown to users who can view your profile. You can turn the mode off or change your selection. This processing provides the discovery service you choose and is managed separately from device location permission.

2.4 Matching and interaction data

• standard Likes, Super Likes, passes/decisions, and mutual matches;
• blocked accounts;
• messaging state and unread counts;
• short-lived typing status and message delivery/read times shown to the other participant or relevant group members; typing status does not share the content of your draft;
• matching and feature-usage quotas;
• discovery filters and preferences used to generate suggestions.

2.5 Messages and User Content

• direct and activity-group text messages;
• photos, GIFs, and audio recordings you send;
• sender/recipient IDs, timestamps, storage paths, content type, and audio duration;
• activity titles, descriptions, cover images, and other user-provided content.

Messages are not represented as end-to-end encrypted. Security controls are used in transit and within service-provider infrastructure, but you should send only information that needs to be shared.

2.6 Activity, participation, and reputation data

• activities you create or join;
• date, duration, capacity, category, city/district, participation mode, and gender preference;
• organizer/member records and join requests;
• declarations about whether an activity occurred and whether a user attended;
• user ratings, reliability statistics, and publication times;
• membership and change-audit records.

2.7 Safety, report, and support data

• blocking records;
• report reason, details, related user/match/activity, and status;
• for a message report, a private evidence copy of the selected message and up to five preceding messages, including text, sender/time information, and any photo, GIF, or audio attachments, shown to you before submission. This copy is for authorized reviewers and may be retained separately from later deletion of the ordinary message. Access to ready evidence closes after thirty days, and records are assessed by daily cleanup;
• moderation decision, reason, authorized reviewer, and timestamps;
• correspondence and attachments you provide in a support request;
• limited technical security information used to prevent fraud and unauthorized access, such as IP address, user agent, request records, and App Check/App Attest validation signals.

2.8 Profile-verification data

If you choose profile verification, we process:

• a selfie captured with the front-facing camera;
• the face-forward or turn-side instruction shown to you;
• verification method, model version, match result, and submission/decision dates;
• pending, verified, or rejected status;
• authorized reviewer and, if applicable, rejection reason.

The current version uses Apple Vision to check whether the image contains one face and to assess face position, size, capture quality, and head direction. It then compares the selfie with faces in your saved profile photos on the device by creating EdgeFace-based numerical face representations. Those temporary representations are used only in device memory during the comparison; they are not sent to or stored on RanMatch servers. Your face is not searched for in other users' photos or in an external face database.

If the match succeeds, a one-time selfie is uploaded briefly to private Firebase storage to bind the verification decision securely to the account and is designed to be deleted after automatic processing completes. The selfie is not displayed on your profile or made available to other users. If the match fails, the selfie is not uploaded, the profile is not verified, and you may retry. Changing profile photos later resets verification. Pending submissions from earlier app versions may be subject to authorized human review.

If the automatic selfie-deletion step fails, the file may remain in storage; a verification badge alone does not prove deletion completed. Contact support for deletion or verification-data requests. Creating face representations on the device is still personal-data processing; keeping them off the server does not remove applicable processing conditions.

2.9 Purchase, digital-entitlement, and subscription data

Payments are processed by Apple; RanMatch does not receive full payment-card details. RanMatch may process limited information such as:

• purchased Super Like or boost pack, subscription product, and membership tier;
• transaction and subscription IDs, environment, purchase date, and any expiration date;
• transaction evidence signed by Apple;
• an App Store account token derived one-way from the RanMatch user ID;
• Super Like, profile-boost, and activity-boost entitlements granted to and used by the account;
• active, canceled, refunded, revoked, or expired purchase/subscription status.

2.10 Device permissions and local information

• Camera: profile verification and taking photos.
• Microphone: recording audio messages.
• Photo picker: accessing only the photo or GIF you choose to upload.
• Location: proximity, distance, and meeting features.
• Local device preferences: app settings such as selected language and last known membership status.

The current RanMatch version does not use an advertising network, a cross-app tracking SDK, contact-book access, or HealthKit health data. If this changes, this Policy and the relevant consent and store disclosures will be updated before the new processing begins.

2.11 Notification information

We use Firebase Cloud Messaging and Apple's notification infrastructure for message, match, and activity notifications. Delivery tokens, account identifiers, preferred language, and registration/update information are processed for this purpose. You may turn off permission in device settings. Doing so does not delete your account or every historical notification record; account deletion also covers account-linked active delivery tokens.

Camera permission is requested when you start taking a photo or profile verification; microphone permission is requested when you start recording an audio message.

3. Sources of personal data

We may receive personal data:

• directly from you through account, profile, message, activity, report, and support fields;
• from your device and permissions you grant;
• from other users, for example when they add you to an activity, rate you, or report you;
• from Apple in limited purchase/subscription-validation and App Store records;
• from infrastructure providers such as Google Firebase and Apple through service and security records.

4. Why we process data and our legal bases

Depending on applicable law, we rely on one or more of the following bases:

Where we rely on legitimate interests, we balance the safety of the Service and its users, fraud prevention, and system integrity against your rights. Where processing is based on consent, you may withdraw consent for the future. Withdrawal does not affect processing already performed lawfully.

For users in Türkiye, the processing conditions under Law No. 6698 are explained separately under “Türkiye — KVKK notice.”

Camera, microphone, photo-picker, and location permissions control technical access to the relevant device resource. We do not treat these permissions as KVKK explicit consent for every processing activity. Granting a permission does not itself authorize processing an unused optional feature’s data for other purposes.

5. Who can see information?

Other RanMatch users

Depending on visibility settings and the context of interaction, other users may see:

• profile name, age, profile photos, biography, sport/activity information, interests, languages, and selected profile fields;
• approximate location or calculated distance;
• verification badge and activity-reliability/rating summary;
• direct messages and media after a mutual match;
• information that a Super Like you send is associated with your profile may be shown to the relevant recipient;
• activity membership information, group messages, and the exact meeting point if they are authorized members of the same activity.

Your private account record, email address, verification selfie, and sensitive administration records are not added to the public profile.

Service providers

We may disclose data, only as needed to provide the Service, to categories including:

• Google Firebase: authentication, databases, file storage, server functions, and app-integrity checks;
• Apple: App Store distribution, StoreKit payments, consumable products and subscriptions, App Attest, device permissions, and Apple Maps/MapKit;
• GeoNames: downloading public city/region data for the selected country; the provider may see the country-file request and connection IP/technical information. Your account ID, profile information, precise location and typed search text are not included in this download request. The geographic list is cached on your device and searched locally. Where coverage is missing, an online search you initiate uses Apple Maps/MapKit.
• legal, security, advisory, or technical-support providers where necessary and subject to appropriate confidentiality obligations.

Legal requests and organizational changes

We may disclose data to competent authorities where required by law, to protect rights and safety, investigate fraud, or respond to a valid legal request. If the Service is involved in a merger, financing, reorganization, or transfer, personal data may be transferred to a relevant party with appropriate confidentiality and notice measures.

6. Do we sell data or share it for advertising?

RanMatch does not sell personal data for money. The current version does not use a third-party targeted-advertising network and does not “share” personal data for cross-context behavioral advertising across apps or websites owned by different companies. If this practice changes, required notices and choice mechanisms will be provided before it takes effect.

7. International data transfers

RanMatch is provided from Türkiye, but providers such as Google Firebase and Apple may process data in Türkiye, the European Economic Area, the United States, and other countries where they maintain facilities. Data-protection rules in those countries may differ from those in your location.

International transfers require a valid transfer condition under Article 9 of Turkish Law No. 6698 and other applicable law. A provider being located abroad, reading this Policy, or accepting general terms does not itself authorize a transfer. EU Standard Contractual Clauses do not automatically satisfy Turkish transfer requirements. RanMatch’s primary Firestore database is configured in the European multi-region (eur3), and its primary file bucket in the European multi-region (EU). Processing locations for other provider services, technical support, and subprocessors may differ by service. These location details do not mean that all processing occurs exclusively in Europe or that required agreements or notifications have been completed.

Contact support@ranmatch.com to request information about providers, processing regions, or applicable safeguards.

8. Retention and deletion

Turning off matching visibility affects visibility among new matching candidates; it does not delete existing chat or activity relationships or photo records. Signing out is not account deletion. If an account-deletion request recorded on the server is interrupted by an error, the daily maintenance task retries cleanup of remaining application data. The request remains queued until completion; a daily schedule does not guarantee destruction of all copies within exactly twenty-four hours. If the connection fails before the server records the request, you may need to submit it again. An error response is not completed deletion; you may contact support. This does not limit statutory deletion rights.

We aim to retain data only for as long as needed for the purpose of collection, safety, dispute resolution, and legal obligations. The following criteria reflect the current system behavior:

Timed cleanup is periodic and paginated. Reaching an eligibility threshold does not guarantee simultaneous physical destruction of every copy. Provider logs and recovery copies follow separately disclosed cycles.

You can delete your account through application settings. The process is designed to remove the authentication account, private/public profile records, account-linked files, and relevant social/activity data from active systems. Limited records strictly necessary for another person’s safety, a valid legal obligation, fraud prevention, or the establishment or defense of a claim may be retained in anonymized or access-restricted form. Service-provider backups may be cleared according to their ordinary deletion cycles.

When an account is deleted, unused consumable RanMatch entitlements associated with that account are removed from active systems. Deleting a RanMatch account does not cancel a subscription managed by Apple.

9. Automated processing and recommendations

RanMatch may filter or order candidate profiles based on preferences, approximate location, activity interests, prior Likes/passes, blocks, and profile visibility. A received Super Like may affect the priority with which the relevant profile is presented, but it does not guarantee first position, display, or a match. Paid profile or activity boosts may affect visibility or ranking priority in the relevant discovery lists; they do not guarantee first position, a number of impressions, participation, or a match. These operations provide connection suggestions and do not make decisions that produce legal or similarly significant effects.

The on-device profile-verification process automatically determines whether the selfie matches at least one saved profile photo above the configured threshold. A match verifies the profile; a non-match does not issue a badge and keeps retry available. Pending submissions from earlier versions and moderation processes may include authorized human review. To contest an outcome, contact support@ranmatch.com.

You can withdraw verification consent using “Remove verification” in the “Profile Verification” section of the profile editor. The operation removes the verification badge and result data and cleans up remaining verification selfies; it does not delete your account or profile photos. Necessary limited consent and operation evidence may be retained. If cleanup cannot finish, the app shows the pending state; you can retry or contact support. New verification is blocked until cleanup finishes.

10. Security

We use technical and organizational controls such as access restrictions, authentication, App Check/App Attest, server-side authorization, encryption in transit, provider-side storage encryption, and separation between private and public data.

No system is completely secure. If you believe your account or data is at risk, contact support@ranmatch.com.

If a personal-data breach requires notice under applicable law, we will notify affected individuals and competent authorities within the legally required period.

11. Your choices and rights

Depending on your location and applicable law, you may have the right to:

• access personal data and obtain a copy;
• correct inaccurate or incomplete data;
• request deletion;
• restrict or object to processing;
• receive data you provided in a portable format;
• withdraw consent;
• request human review of certain automated processing or moderation outcomes;
• opt out of sale, targeted advertising, or certain forms of sharing;
• complain to a data-protection authority;
• exercise privacy rights without discrimination.

You can edit many profile fields in the app, change permissions in device settings, block users, and delete your account in application settings. For other requests, contact support@ranmatch.com.

We may need to verify your identity for security. We request only information required by the applicable request procedure and the request itself; we do not ask for your account password, verification code, or payment-card details. If an authorized agent submits a request, we may ask for evidence of authority. Response periods depend on applicable law. Requests under Turkish law follow the thirty-day rule below; extensions available in another country do not automatically apply to Turkish requests.

12. Children’s privacy

RanMatch is only for users aged 18 and over. We do not intend to knowingly collect account data from anyone under 18. If we learn that a minor created an account, we will take reasonable steps to delete the account and associated data or take another protective action. Contact support@ranmatch.com to report a concern.

13. Regional provisions

13.1 Türkiye — KVKK notice

For purposes of Turkish Personal Data Protection Law No. 6698, the controller is Halil İbrahim Tayfur. Data is collected wholly or partly by automated means through app forms and content uploads, device permissions, automatic technical records, other-user interactions, and Apple/Firebase services.

For Türkiye, purposes and processing conditions are mapped below. Each condition applies only to necessary data and where its requirements are actually met; the list does not mean that every condition is used together for the same processing.

Height or a sports preference is not automatically health data. Providing health or other special-category information in free text or messages does not authorize its use for every purpose. Biometric face comparison is subject to Article 6 and adequate safeguards. Special-category data without an applicable processing condition is not reused for other purposes.

For the purposes described in this Policy, data may be transferred to authorized RanMatch personnel, other users, providers such as Google/Firebase and Apple, advisers, and legally authorized public bodies. International transfers are subject to the requirements in section 7; this notice alone does not authorize transfers or constitute explicit consent.

Under Article 11, you may ask whether your data is processed; request information; learn the purpose and whether data is used accordingly; learn recipients in Türkiye or abroad; request correction and notice to recipients; request deletion/destruction where conditions apply and notice to recipients; object to a result produced exclusively by automated analysis that is against you; and claim compensation for unlawful processing.

You may submit a request from the email address registered to your RanMatch account to support@ranmatch.com. This email route does not remove other submission methods or mandatory elements under the applicable Turkish request-procedure communiqué. If you cannot access your account or registered email, contact support to establish an appropriate secure route. We verify requests without giving access to another person’s data; a complete identity-document copy is not requested routinely.

We resolve the request as soon as its nature permits and within thirty days at the latest. We provide a final written or electronic response describing the accepted scope, actions taken, and reasons for any refusal. Requests for additional information or a telephone conversation do not replace the final response. Requests to notify recipients of correction or deletion/destruction are also assessed under the applicable statutory conditions.

13.2 European Economic Area, United Kingdom, and Switzerland

Depending on your residence and how the Service is offered to you, data protection rules of the European Economic Area, United Kingdom, or Switzerland may apply. Limited storefront availability does not exclude laws that apply on another basis.

If the GDPR or equivalent law applies for another reason, the legal bases described in “Why we process data” and rights of access, correction, erasure, restriction, objection, portability, withdrawal of consent, and complaint to a competent supervisory authority may apply. Contact support@ranmatch.com for information.

13.3 United States and California

Where applicable U.S. state privacy law applies, you may have rights to access/know, correct, delete, obtain a portable copy, opt out of targeted advertising or sale/sharing, limit certain uses of sensitive data, and receive equal service when exercising a right.

Categories we may process in the preceding 12 months include identifiers and contact information, online identifiers, approximate/precise location, profile characteristics, User Content, purchase/subscription information, internet/app activity, inferences, and safety records. These categories are disclosed as described above to users, infrastructure providers, and competent authorities for the stated purposes.

RanMatch does not sell personal information and, in its current version, does not share it for cross-context behavioral advertising or process it for targeted advertising as those terms are defined by relevant state laws. RanMatch does not knowingly serve people under 16; every account is 18+.

Submit a request or appeal through support@ranmatch.com. You may use an authorized agent where applicable law permits.

13.4 Brazil

Where Brazil’s General Data Protection Law (LGPD) applies, processing may rely on performance of a contract, legal obligations, the exercise of rights, legitimate interests, and consent where required. You may request confirmation, access, correction, anonymization/blocking/deletion, portability, information about sharing, consent-related rights, and review through support@ranmatch.com. You may also contact Brazil’s National Data Protection Authority (ANPD).

13.5 Canada, Australia, and other regions

Local law may grant additional rights such as access, correction, deletion, withdrawal of consent, and complaint to a privacy regulator. RanMatch will handle verifiable requests under applicable local law. If a country requires a local representative, registration, data localization, or a separate notice, it must be completed before that storefront is enabled.

14. Changes to this Policy

We may update this Policy when the product, data practices, or law changes. We will revise the “Last updated” date. For material changes, we will provide advance notice by in-app message, email, or another appropriate method and request renewed consent/acceptance where required.

15. Contact and complaints

For privacy questions, requests, or complaints:

• Controller: Halil İbrahim Tayfur
• Privacy and support email: support@ranmatch.com
• Website: https://ranmatch.com

You may also have the right to complain to the competent data-protection or consumer authority where you live.