Tracking & Analytics Policy
Monogam App · Last updated: 10 August 2026
This policy explains the tracking and technical technologies used by the Monogam mobile application to improve the user experience, measure application performance, and carry out identity authentication processes. Taha Dülgar is responsible, in the capacity of data controller, for the processing of all personal data within the scope of this policy. Once the incorporation process is completed, this section will be updated with the relevant legal entity information. Mobile applications do not use browser cookies; instead, device identifiers and in-app session data are used.
1. Technologies We Use
Monogam uses the following technology categories:
| Technology | Provider | Purpose | Opt-Out |
|---|---|---|---|
| Firebase Instance ID | Google LLC | Device identifier used to uniquely identify the application | Cannot be disabled — required for the basic service |
| Firebase Analytics | Google LLC | Application usage statistics, screen views, user flows | Cannot be disabled — required for the basic service |
| Firebase Crashlytics | Google LLC | Application error reports and performance monitoring | Cannot be disabled — required for the basic service |
| Firebase Performance | Google LLC | Measurement of network requests and application launch time | Cannot be disabled — required for the basic service |
| Firebase Authentication | Google LLC | SMS OTP and email verification processes; phone number and email address are processed for authentication | Cannot be disabled — required for the basic service |
2. Data Collected and Purposes
2.1 Mandatory Technical Data
Data required for the proper functioning of the application:
- Session data: Application login/logout times
- Device information: Operating system version, device model
- Error logs: For detection and correction of application crashes
- Network information: API response times and connection status
- Authentication data: Phone number and email address for SMS OTP and email verification (Firebase Authentication)
Without this data, application errors cannot be detected or corrected, and identity authentication cannot be performed. Legal basis: Performance of a contract (KVKK Art. 5/2-c) and Legitimate interest (KVKK Art. 5/2-f).
2.2 Analytics Data
Data collected to improve the user experience:
- Which screens are used and for how long
- Frequency of use of matching and messaging features
- In-app button click and flow data
- User segments (age group, location region — not individual)
This data is not used to identify individual users; it is processed solely as aggregate statistics. Legal basis: Explicit consent (KVKK Art. 5/1).
3. Processing of Personal Data
Firebase Analytics processes personal data with the following approach:
- IP address: Truncated and stored by Google; the full IP is not transmitted to Monogam
- Device identifiers: Not associated with your real identity
- Usage data: Processed anonymously or pseudonymously
The phone number and email address processed under Firebase Authentication are used solely for identity authentication purposes; they are not processed for analytics or marketing purposes. After verification is completed, this data is deleted from Firebase systems within 30 days.
Firebase data may be processed by Google LLC in the United States. Google applies the EU Standard Contractual Clauses for these transfers. This transfer is also stated in our Privacy Policy, KVKK Disclosure Notice, and Explicit Consent Notice and is based on the user’s explicit consent.
4. Retention Periods
Firebase data is retained for the following periods:
- User-level analytics data: 14 months (default Firebase setting)
- Aggregate reports: Indefinite (contains no individual user data)
- Error reports (Crashlytics): 90 days
- Performance data: 30 days
- Authentication logs (Authentication): 30 days after verification is completed
5. Opt-Out Options
You may disable the collection of analytics data through the following means:
- In-app: Profile > Settings > Privacy > Turn Off Analytics Data
- iOS: Settings > Privacy > Tracking > Remove permission for Monogam
- Android: Settings > Privacy > Ads > Reset Advertising ID
Disabling analytics data does not affect the application’s core functions. Firebase Authentication, however, cannot be disabled as it is required for SMS and email verification.
6. Third-Party Links
Monogam does not currently use third-party advertising networks or social media tracking pixels. If this changes, this policy will be updated and users will be informed. User data is under no circumstances shared with third parties for advertising purposes without prior notice.
7. Children’s Privacy
Monogam is intended solely for users aged 18 and over. We do not knowingly collect analytics data from users under the age of 18. If we become aware of such a situation, we will immediately delete the relevant data.
8. Policy Updates
This policy may be updated in line with application updates or changes in the technologies used. Material changes will be communicated via in-app notification or email.
9. Contact
For questions about this policy:
- Email: [email protected]
This policy entered into force on 10 August 2026.