Tracking and Analytics Policy
Monogam App | Last updated: September 21, 2026
This policy explains the tracking and technical technologies used by the Monogam mobile app to improve the user experience, measure app performance and carry out identity verification.
Monotech Bilişim Teknoloji Anonim Şirketi (Tax No: 6211334496) is responsible, as data controller, for the processing of all personal data covered by this policy. Mobile apps do not use browser cookies; instead, device identifiers and in-app session data are used.
1. Technologies We Use
Monogam uses the following categories of technology:
| Technology | Provider | Purpose | Opt-Out |
|---|---|---|---|
| Firebase Instance ID | Google LLC | Device identifier used to uniquely identify the app | Cannot be disabled — required for the core service |
| Firebase Analytics | Google LLC | App usage statistics, screen views, user flows | Cannot be disabled — required for the core service |
| Firebase Crashlytics | Google LLC | App error reports and performance monitoring | Cannot be disabled — required for the core service |
| Firebase Performance | Google LLC | Measurement of network requests and app launch time | Cannot be disabled — required for the core service |
| Firebase Authentication | Google LLC | SMS OTP verification; phone number is processed for identity verification | Cannot be disabled — required for the core service |
| NetGSM SMS Service | Genel Mobil Telekomünikasyon Hizmetleri A.Ş. | SMS OTP verification; only the phone number and verification code are transmitted, no data is stored | Cannot be disabled — required for identity verification |
2. Data Collected and Purposes
2.1 Mandatory Technical Data
Data required for the app to function properly:
- Session data: App login/logout times
- Device information: Operating system version, device model
- Error logs: For detecting and fixing app crashes
- Network information: API response times and connection status
- Identity verification data: Phone number for SMS OTP verification (NetGSM and/or Firebase Authentication)
Without this data, app errors cannot be detected or fixed, and identity verification cannot be carried out. 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 only 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: Stored in truncated form by Google; the full IP is not transmitted to Monogam
- Device identifiers: Not linked to your real identity
- Usage data: Processed anonymously or pseudonymously
The phone number processed within Firebase Authentication is used solely for identity verification; it is not processed for analytics or marketing purposes. After verification is completed, this data is deleted from Firebase systems within 30 days.
NetGSM receives only the phone number and verification code during the SMS verification process. As NetGSM is established in Türkiye, it does not fall within the scope of transfers abroad; it is subject to the provisions of the KVKK.
Firebase data may be processed by Google LLC in the United States of America. Google applies the EU Standard Contractual Clauses to these transfers. This transfer is also stated in our Privacy Policy, PDPL Privacy Notice (KVKK) and Explicit Consent Form, and is based on the user’s explicit consent.
4. Retention Periods
Firebase data is retained for the following periods:
- User-level analytics data: 12 months (default Firebase setting)
- Aggregate reports: Indefinitely (contain no individual user data)
- Error reports (Crashlytics): 90 days
- Performance data: 30 days
- Identity verification logs (Authentication): 30 days after verification is completed
- NetGSM SMS logs: Processed by NetGSM at the moment of verification; not stored by Monogam
5. Opt-Out Options
Firebase Authentication and NetGSM SMS verification cannot be disabled, as they are required for identity verification.
6. Third-Party Connections
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 never shared with third parties for advertising purposes without prior notice.
7. Children’s Privacy
Monogam is intended only for users aged 18 and over. We do not knowingly collect analytics data from users under 18. If we become aware of such a case, we will delete the relevant data immediately.
8. Policy Updates
This policy may be updated in line with app updates or changes to 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 September 21, 2026.