This Cookies & Similar Technologies Policy (the “Cookies Policy”) explains how Tawasol Software and Website Design (“Oolfa”, “we”, “us” or “our”) uses cookies and similar tracking technologies on:

  • Our websites (including oolfa.com and any localized versions), and
  • Our mobile applications on Android and iOS

(together, the “Service”).

Oolfa is a global Muslim marriage platform designed for adult Muslims worldwide. Because our users are located in many countries, this Cookies Policy is written to reflect key requirements under laws such as the EU/UK ePrivacy rules, the GDPR/UK GDPR, and the California Consumer Privacy Act as amended by the CPRA. iubenda+3ICO+3ICO+3

For more information about how we handle personal data generally (including your rights and choices), please also read our Privacy Policy.

If there is any conflict between this Cookies Policy and the Privacy Policy regarding cookies and similar technologies, this Cookies Policy will apply to that topic.

1. What are cookies and similar technologies?

1.1 Cookies

Cookies are small text files that are stored on your browser or device when you visit a website. They are widely used to make websites work, or to work more efficiently, as well as to provide information to the site owner. ICO+1

Cookies can be:

  • Session cookies – deleted automatically when you close your browser.
  • Persistent cookies – remain on your device until they expire or you delete them.

1.2 SDKs, device identifiers and other similar technologies

On our mobile apps, we use technologies that work in a similar way to cookies, such as:

  • Software development kits (SDKs) integrated into the app (for example, analytics or crash reporting SDKs).
  • Device identifiers (for example, advertising identifiers or app instance IDs).
  • Local storage and in-app preferences stored on your device.

Under many privacy and ePrivacy laws, these technologies are treated similarly to cookies because they store or access information on your device. privacymatters.dlapiper.com+1

In this Cookies Policy, we refer to “cookies” to include both traditional browser cookies and similar technologies used in our apps, unless we need to distinguish between them.

2. Why we use cookies and similar technologies

We use cookies and similar technologies for several purposes, grouped broadly into four categories.

2.1 Strictly necessary cookies and technologies

These are essential for the Service to function and cannot be switched off in our systems. Without them, we cannot:

  • Provide secure login and basic features
  • Keep you logged in while you navigate
  • Remember core security and privacy settings
  • Process your cookie choices and consent

Because these are strictly necessary to provide the Service or to comply with our legal obligations (for example, security requirements), they generally do not require your consent under EU/UK ePrivacy rules. ICO+2Data Protection Law Hub+2

2.2 Functionality (preference) cookies

These cookies remember choices you make, such as:

  • Language and region
  • Display preferences
  • Certain in-app settings that determine how the app looks or behaves for you

They help us provide a more tailored, user-friendly experience. In some jurisdictions, your consent may be required if these are not strictly necessary.

2.3 Performance and analytics cookies / SDKs

We use analytics tools (for example, tools provided by large technology providers) to help us understand how our websites and apps are used, so that we can:

  • Measure and improve performance
  • Fix bugs and crashes
  • Understand which features are used most
  • Plan new features and improvements

These tools typically collect information such as the pages or screens you view, how long you spend on them, the device and operating system you use, and general location information (for example, city/region).

Under EU/UK ePrivacy rules, these analytics tools usually require your consent unless they are configured in a very limited, privacy-preserving way. Data protection authorities have clarified that analytics cookies often need GDPR-standard consent (freely given, specific, informed and unambiguous, given by a clear affirmative action). iubenda+5ICO+5cookieyes.com+5

2.4 Marketing and advertising cookies / identifiers

At the time this Cookies Policy was last updated:

If we decide in the future to use technologies for this purpose, we will:

  • Update this Cookies Policy and our Privacy Policy
  • Obtain any consent required by applicable law before placing or reading those cookies or identifiers
  • Provide you with clear choices, including any “Do Not Sell or Share My Personal Information” or similar opt-out rights required under CPRA or other laws

3. Cookies and similar technologies we may use

Because specific cookies and SDKs can change over time (for example, when we add or remove services), we provide an overview of the types of technologies we typically use. If required by law or if technically feasible, we may provide a more detailed, up-to-date list via our cookie banner or help pages.

3.1 On our websites

Our websites may use:

  • Strictly necessary cookies
    • For example, cookies that:
      • Keep your session active after login
      • Store your cookie consent choices
      • Protect against fraudulent use of logins and sessions
  • Functionality cookies
    • For example, cookies that remember:
      • The language version of the site you prefer
      • Your region or selected country
      • Certain interface preferences
  • Performance/analytics cookies
    • For example, cookies that:
      • Count page visits and traffic sources so we can measure and improve site performance
      • Help us understand which pages are most and least popular
      • Track basic technical errors and load times

These analytics cookies often come from third-party providers. These providers may process data about your visits to our site alongside information from other sites that use their services, but they are bound by their own privacy policies and our contracts with them. Supervisory authorities around the world (for example, in the EU and France) have taken enforcement action where analytics and advertising cookies were set without proper consent or where refusal was harder than acceptance. The Wall Street Journal+6CNIL+6Baker McKenzie Resource Hub+6

3.2 In our mobile apps

Our Android and iOS apps may use:

  • App-internal preferences and storage
    • To remember settings such as language, notification preferences, and how certain features behave.
  • Analytics SDKs
    • To understand app usage, performance, and crashes (for example, which screens are most used or where crashes occur).
  • Device identifiers and push notification tokens
    • To deliver push notifications (for example, new messages or matches) to your device.
    • To measure aggregated engagement, such as how many people open a notification.

On mobile, some of these technologies are controlled via your device’s system settings rather than via browser cookies, but many regulators treat them similarly to cookies for legal purposes. ICO+2privacymatters.dlapiper.com+2

We do not use push notification tokens or device identifiers to track you across other apps for advertising purposes.

4.1 EU/EEA, UK and similar jurisdictions

In the EU/EEA and UK, the use of cookies and similar technologies is governed by:

  • The ePrivacy Directive and national laws implementing it (such as the UK’s PECR), which require prior informed consent for storing or accessing information on your device, except where it is strictly necessary for the service you requested. Fieldfisher+4ICO+4TechReg+4
  • The GDPR/UK GDPR, which apply to any personal data collected via cookies and similar technologies and require a lawful basis for processing, usually consent for non-essential cookies. EDPB+2cookiebot.com+2

In practice, this means:

  • We do not place or read non-essential cookies or analytics SDKs in these regions until you have given us your explicit consent via our cookie banner or in-app consent flows.
  • Consent must be freely given, specific, informed and unambiguous, given by a clear positive action (for example, clicking “Accept” on our cookie banner). Scrolling, swiping or continued browsing alone is not treated as consent. EDPB+2cookiebot.com+2
  • You must be able to reject non-essential cookies as easily as you can accept them and to change your mind later. Cookie Information+3CNIL+3ICO+3

4.2 California and certain other US states

Under the California Consumer Privacy Act (CCPA), as amended by the CPRA, some cookies and tracking technologies can be considered a “sale” or “sharing” of personal information when they are used for cross-context behavioural advertising (targeted advertising based on data collected across different websites or apps). IAPP+6California Attorney General+6cookieyes.com+6

At the time this Cookies Policy was last updated:

  • We do not sell or share personal information collected via cookies or SDKs for cross-context behavioural advertising.
  • If this changes in the future, we will:
    • Update our Privacy Policy and Cookies Policy, and
    • Provide a clear and prominent “Do Not Sell or Share My Personal Information” option or equivalent, as required by law.

Other U.S. states and countries have introduced similar concepts or specific consent/opt-out requirements for tracking technologies. We aim to respect these requirements by providing clear choices and honouring legally-recognized opt-out signals where applicable and technically feasible.

5. How you can manage cookies and similar technologies

Because Oolfa is used by Muslims across many countries, we try to provide a clear, layered approach to managing cookies and trackers.

On the website:

  • On your first visit from certain regions (for example, the EU/EEA or UK), you will see a cookie banner explaining our use of cookies and giving you choices to accept, reject, or customize non-essential cookies.
  • You can revisit your cookie choices at any time by using the “Cookie Settings” or similar link (for example, in the footer or within the banner, depending on our implementation at that time).

If you choose to reject or disable certain cookies, some features (especially those relying on analytics or personalization) may not work optimally, but the core parts of the Service should still function.

5.2 Browser settings

Most web browsers allow you to:

  • See which cookies are stored on your device,
  • Delete some or all cookies, and
  • Block cookies for specific sites or all sites.

The methods for doing this vary between browsers. You will normally find instructions in the browser’s help or settings menu.

If you delete cookies, you may need to re-set your preferences every time you visit (including your cookie consent preferences).

5.3 Mobile app controls

On Android and iOS, you can use system settings to control certain identifiers and permissions. For example:

  • Tracking / advertising identifiers – you can reset your advertising ID and limit tracking in your device’s privacy or advertising settings.
  • Push notifications – you can turn notifications on or off for the Oolfa app via system settings.
  • Location permissions – you can allow or deny the app access to location services.

These settings are managed by your device’s operating system; changing them may affect how some Oolfa features work.

5.4 Analytics and third-party controls

Some analytics and tracking providers also offer their own opt-out tools or settings (for example, browser add-ons or account-level privacy controls).

Where we use such providers, you may be able to:

  • Turn off certain forms of measurement or personalization from within the provider’s privacy or account settings, and/or
  • Use specific opt-out mechanisms they offer.

Details about these options are usually available in the privacy documentation of the relevant provider.

6. How long we keep cookies and identifiers

Different cookies and identifiers last for different periods:

  • Session cookies typically last only until you close your browser.
  • Persistent cookies may last for a longer period (for example, several months) unless you delete them earlier.
  • SDK identifiers and local app storage may remain on your device until you clear app data, uninstall the app, or until we update or remove the SDK.

We aim, where possible, to configure non-essential cookies and similar identifiers:

  • To persist only for as long as necessary to achieve their stated purpose, and
  • In line with applicable regulatory guidance, which often recommends limiting non-essential cookies (such as analytics cookies) to around 13 months or less. cookieyes.com+2Pinsent Masons+2

The actual lifespan of each cookie or SDK identifier may vary depending on our technical configuration and the third-party provider. If your region’s laws require more detailed information (for example, per-cookie duration and provider), we may provide it via our cookie banner, a cookie table, or on request.

7. Relationship with our Privacy Policy

This Cookies Policy focuses specifically on technologies that store or access information on your device.

For more information about:

  • What personal data we collect,
  • Our legal bases for processing,
  • The rights available to you (access, deletion, objection, etc.), and
  • How long we keep different categories of personal data,

please refer to our Privacy Policy.

If you have questions about how cookies relate to your personal data rights (for example, access or deletion), you can contact us using the details in Section 8.

8. Changes to this Cookies Policy

We may update this Cookies Policy from time to time, for example when we:

  • Add new cookies, SDKs, or similar technologies,
  • Change our use of existing technologies, or
  • Respond to legal, technical, or business developments.

When we make material changes, we will:

  • Update the “Current as of” date at the top of this page, and
  • Provide additional notice where appropriate (for example, through a banner on the website, in-app notices, or email).

We encourage you to review this Cookies Policy periodically to stay informed about our use of cookies and similar technologies.

9. Contact us

If you have any questions, concerns, or requests regarding this Cookies Policy or our use of cookies and similar technologies, you can contact us:

    • By email:
      info@oolfa.com
    • Through our Help page:
      By submitting a request via the Contact Us form available on Our Help page on the Website.
    • From within the Application:
      By using the in-app support (for example, from the Messages section inside the Oolfa App).

    We will use reasonable efforts to review and respond to Your request within a reasonable time, in accordance with applicable law.