Privacy Policy for Qesmati
This policy explains the data Qesmati processes, why it is used, and the choices available to you.
This policy explains the data Qesmati needs for accounts, profiles, and contact requests, how that data is used and protected, and the choices available to you. Public profiles do not require published contact details, and access, correction, and deletion are governed by the controls below.
Qesmati's Privacy Policy and data protection approach distinguish account information from the details in a marriage profile. When a wali or another person manages a profile, its information must be provided with the profile subject's consent for a serious introduction. Data is used to confirm accounts, operate search and review, process contact requests and notifications, and prevent misuse, with access limited by role and need. Do not place a phone number, address, document, or financial detail in a public description; use the designated fields and process, and request correction or deletion through account controls or support when needed.
The platform records limited technical data needed to protect sessions, diagnose failures, and resist misuse, such as request time, browser type, and appropriate security identifiers. These logs are not used to create a public member description and remain subject to the retention periods and controls stated in this policy. When contacting support, share the ticket or request reference instead of copying conversations or another person's details, and review device and account settings whenever a shared device is used.
1. Information We Collect
- • Account and profile data: name, email, phone number, age, nationality, place of residence, marital status, education and occupation.
- • Data you choose to enter yourself, such as level of religious observance, health status, and how you describe yourself and the partner you are seeking. These are optional and you may remove them at any time.
- • Login records and interactions within the site to improve service.
2. How Do We Use This Information?
- • To connect you with suitable people based on your preferences.
- • To improve the user experience and site appearance.
- • To send alerts or important notifications related to your account.
3. Who Can See Your Data?
Other members see profile information you choose to publish. Private contact details are shown only according to platform settings and accepted contact requests. Moderators and technical service providers may process data as needed to operate the service and review reports.
4. Your Rights
- • You can modify your data at any time.
- • You can disable your account in settings and request permanent deletion through the Contact page.
- • If a relative created a profile describing you and you were not aware of it, contact us and we will remove it - no account needed.
5. Protecting Your Data
We use encrypted connections, store passwords as hashes, and restrict data access according to operational need. The platform may use infrastructure and service providers according to the service's actual configuration.
6. Mobile App Notifications and Firebase
When you enable app notifications, Firebase Cloud Messaging and Firebase Installations process a Firebase Installation ID (FID) and technical information such as the app version and Firebase user agent. Qesmati sends its server the app's FCM registration token, an app-installation device identifier, optional device name, app version, and selected locale.
We use this data only to deliver service notifications related to your account, such as messages, contact requests, and security or account updates, and to localize delivery. We do not put message text or private contact details in an FCM notification payload.
Google, through Firebase services, acts as our service provider and technical processor for this data to deliver notifications.
Registration tokens and notification data are transmitted over encrypted connections. We do not expose an FCM token to other members, and lock-screen content is limited to a generic alert and non-sensitive routing identifiers.
Notification permission is optional and can be denied or revoked in system settings. You can also control account-notification categories in Qesmati's notification preferences.
When Firebase rotates a registration token, we replace the old token for the same installation. The app requests token removal when you sign out, we delete it when the account is deleted, and the server removes tokens that FCM reports as invalid or unregistered.
We do not use Firebase Cloud Messaging or the Firebase Installation ID for advertising, ad tracking, or analytics. Firebase Crashlytics is not enabled in this release of the app.
Cookie Policy
We use cookies to improve your experience on our website.
Essential Cookies: We use essential cookies to operate the website, such as session and authentication cookies. These cookies are essential and cannot be disabled.
Privacy Requests and Data Retention
We handle privacy requests according to the laws applicable to the platform's operation and the person making the request.
You may request access to, correction of, or deletion of your data through the Contact page. We may verify identity before acting on a request.
We retain data as needed to provide the service, protect users, and meet legal obligations, then delete or anonymize it according to the record type.
If you have any inquiries regarding the privacy policy, please contact us via the official email.
Last Updated: August 31, 2026