Cookie Policy

1. Scope

This Policy applies to the Dar Al Tharwah public website, member accounts, login and signup flows, dashboards, profile pages, consultation forms, newsletters, downloads, and other digital services that link to it.

“Cookies” in this Policy includes browser cookies, local storage, pixels, tags, software development kits, and comparable technologies that store or read information on a device.

2. Why these technologies are used

• authenticate users and maintain secure sessions;
• protect accounts, forms, and services against fraud, abuse, and security threats;
• remember language, appearance, accessibility, and interface preferences;
• operate forms, restricted content, enrolment, downloads, and member features;
• diagnose technical problems and improve reliability and performance;
• measure audience and content performance where an analytics service is enabled;
• support communications or marketing only where lawfully configured.

3. Strictly necessary technologies

Strictly necessary technologies are required for functions requested by a user or for security and service operation. They may be used without optional consent where permitted by law. Blocking them may prevent login, account access, form submission, preference storage, or other core functions.

Necessary technologies are not used by Dar Al Tharwah to sell personal information or build advertising profiles.

4. Clerk authentication and session technologies

Dar Al Tharwah currently uses Clerk to provide authentication, user management, and session security. Clerk may set or use necessary session and client cookies when a person signs up, signs in, remains signed in, verifies an account, or accesses protected features.

Depending on the configuration and browser, Clerk cookies may include names such as __session and __client_uat, together with security or infrastructure cookies used by Clerk or its delivery providers. Cookie names, domains, and lifetimes may change when Clerk updates its service or when the authentication configuration changes.

These technologies are required for account authentication and cannot be disabled through an optional cookie preference without disabling the related account functionality.

5. Webflow and website infrastructure

The website is built and hosted using Webflow and may rely on Webflow or related infrastructure for page delivery, forms, content management, security, load balancing, diagnostics, and protection against misuse. Technical identifiers or short-lived cookies may be used where necessary to provide these functions.

Third-party infrastructure providers process information under their own technical and contractual controls and may update their technologies over time.

6. Local storage and preferences

The website currently stores the chosen light or dark appearance in browser local storage using the key dar-color-theme. This preference does not identify a person by itself and is used to keep the selected appearance across visits.

Other functional preferences may be stored locally if new accessibility, language, or member features are introduced. Material changes will be reflected in this Policy.

7. Analytics and performance measurement

Analytics or performance services may be enabled to understand visits, device types, referral sources, page performance, and engagement. Where such tools are not strictly necessary and applicable law requires consent, they should not be activated until the user has made a valid choice.

Analytics information should be used in aggregated or limited form where reasonably possible. Dar Al Tharwah does not use analytics data to make regulated financial decisions about users.

8. Embedded content, communications, and marketing

Embedded videos, maps, scheduling tools, social-media features, newsletter providers, or other third-party content may set their own technologies when loaded or used. Where an optional provider is introduced, its role and any required consent mechanism should be disclosed before or at the time of use.

Dar Al Tharwah does not currently promise that every page is free of third-party requests, because necessary hosting, authentication, security, and content-delivery services may operate across different domains.

9. Consent and controls

Where consent is required for optional technologies, users should be given a clear choice to accept, reject, or change that choice. Withdrawing consent does not affect processing already carried out lawfully and does not disable technologies that remain strictly necessary.

Browser settings can usually block, delete, or limit cookies and site storage. Doing so may sign a user out, reset preferences, or prevent some features from working. Account users may also sign out and manage active sessions through available account controls.

10. Retention

Cookie and storage lifetimes vary by purpose. Session technologies may expire when a session ends or after a configured security period. Preference storage may remain until it is replaced or deleted. Security and diagnostic records may be retained separately where reasonably necessary for fraud prevention, service integrity, legal claims, or compliance.

11. Changes to this Policy

This Policy may be updated when providers, features, consent requirements, or applicable laws change. The effective date will be revised, and material changes affecting registered users will be communicated through a reasonable channel where required.

12. Contact

Questions about cookies, consent, or personal information may be submitted through the contact and consultation page. Clearly state that the message concerns cookies or privacy.