Cookie Policy.

This Cookie Policy explains how daralpashmina.com uses cookies and similar browser technologies. A cookie is a small text file stored by a browser. Similar technologies include local storage, pixels, tags and scripts that store information or cause information to be transmitted.

The Website is operated by [[LEGAL OPERATOR NAME AND LEGAL FORM]], trading as Dar Al Pashmina, Commercial Registration number [[CR NUMBER]] and e-commerce licence number [[E-COMMERCE LICENCE NUMBER]]. This Policy must be read with the final Privacy Policy.

WooCommerce uses first-party session technologies when a visitor interacts with the Bag and checkout. The expected core records are:

• woocommerce_cart_hash — session — detects changes to Bag contents;
• woocommerce_items_in_cart — session — tells the Website whether the Bag contains Pieces;
• wp_woocommerce_session_* — ordinarily two days — links the browser to its stored shopping session;
• woocommerce_recently_viewed — session — only if the recently viewed feature is used; and
• store_notice* — session — only if a dismissible store notice is used.

These technologies do not intentionally store names, addresses or complete payment details inside the cookie itself. The session reference may connect to Bag or session data held by the Website. Exact active names and durations must be verified against the launch version of WooCommerce.

The custom Dar Al Pashmina pages currently save the key dap-language in browser local storage when English or Arabic is selected. Its value is limited to the language code. It helps pages reopen in the chosen language and is not intended to identify a person.

Unlike a session cookie, this preference remains until it is replaced or the browser’s site data is cleared. If storage is unavailable or cleared, the Website returns to English. This function is treated as a limited preference technology rather than advertising or behavioural tracking.

WordPress, the hosting environment and security tools may use cookies or server-side identifiers for authentication, fraud prevention, load balancing, abuse protection, preferences and technical administration. Login and administrator cookies normally apply only when an authorized user signs in; customer-account cookies apply only if accounts are enabled and used.

The launch audit must record every active security, hosting, caching, account and consent technology, including its provider, purpose and duration. A security label must not be used to disguise analytics or advertising.

No analytics platform is approved for launch at the date of this draft. Google Analytics or another audience-measurement tool must remain disabled until the House has documented the provider, data, purpose, lawful basis, destinations, retention and safeguards.

If consent is required, the tool and its scripts must remain technically blocked until the visitor chooses to accept that category. Aggregated reports do not remove the need to assess the collection and transmission that produced them.

Meta Pixel, advertising cookies, remarketing audiences and cross-site behavioural tracking are not approved for launch and must remain off. They may be considered later only after a documented necessity and privacy assessment, an updated Policy and consent interface, appropriate provider terms and any other measure required by Qatar law.

Where consent is the basis, it must be specific, informed and expressed by a positive choice. Advertising must not load merely because a visitor continues browsing, closes a banner or fails to change a pre-selected setting.

The future card, PayPal, Fawran or other payment integration may use cookies, device identifiers or scripts for authentication, fraud prevention and payment completion. The final provider has not been selected. Its technology must be inventoried and disclosed before activation, with strictly necessary payment functions separated from optional measurement or marketing.

The current custom pages request Google Fonts. A font request may transmit technical data such as IP address and browser information even if no cookie is set. The preferred Layer 2 action is to self-host the approved fonts. If an external service remains, it must be recorded in the final Privacy and Cookie Policies.

The obsolete newsletter/contact form and Google reCAPTCHA should be removed if no longer used. If retained, their scripts, data, providers and consent position must be included in the production inventory.

If non-essential technology is introduced, the Website will present a concise choice before it loads. Accepting and rejecting non-essential categories must be comparably clear and easy. Optional categories will not be pre-selected, bundled with essential service or made a condition of using the boutique.

A persistent Cookie Settings control will allow the visitor to review and change the choice. Withdrawal will prevent future optional processing but cannot undo processing lawfully completed beforehand. A limited consent record may be retained to remember and demonstrate the choice.

Most browsers allow cookies and site data to be viewed, deleted or blocked. Browser controls operate separately from any Website preference centre. Clearing site data will normally remove the saved language choice and may empty the Bag, end a session, sign an account out or require checkout information to be entered again.

Strictly necessary technologies cannot be disabled through an optional-cookie setting while the dependent service is being used. A visitor may still block them through the browser, but the Bag, authentication, security or checkout may then fail. Refusing optional analytics or advertising will not prevent ordinary access or purchase.

We will review this Policy whenever the Website, WooCommerce, a plugin, payment method, embedded service or marketing tool changes. The published inventory must reflect what the production Website actually deploys, not merely what a provider says may be used. Material changes will be disclosed and fresh consent obtained where required.

Questions or privacy requests may be sent through Private Assistance, WhatsApp [[WHATSAPP NUMBER]] or email [[PRIVACY EMAIL]]. This Policy is governed by the laws of the State of Qatar and does not limit any mandatory privacy right or official complaint route.

English and Arabic are supplied for accessibility. Before publication, both must be reviewed for legal equivalence by Qatar counsel and the final Policy must state the controlling version to the extent permitted by law. Effective date: [[DAY MONTH YEAR]]. Version: [[FINAL VERSION NUMBER]].