Legal

Cookie Policy

Last updated · 14 July 2026

This policy lists every cookie Dulaxa sets, and why. We keep the list short on purpose.

Dulaxa runs no advertising cookies, no analytics cookies, and no third-party tracking scripts. We do not build advertising profiles, and we do not share browsing behaviour with anyone. Because we set only strictly-necessary and preference cookies, you will not find a consent banner nagging you on this site.

1. What cookies are

A cookie is a small text file a website stores in your browser. It lets the site remember something between requests — for example, that you are signed in, or that you prefer Arabic.

2. The cookies we set

Cookie	Purpose	Type	Lifetime
sb-<project>-auth-token	Keeps you signed in to your dashboard and refreshes your session securely. Set by our authentication provider, Supabase.	Strictly necessary	Session / until sign-out
dulaxa_locale	Remembers whether you chose English or Arabic, so the site opens in your language.	Preference	1 year

Strictly-necessary cookies cannot be switched off without breaking sign-in — they exist only to deliver a service you asked for. The preference cookie is set only when you actively choose a language.

3. Performance measurement (not a cookie)

We measure Core Web Vitals — how quickly pages render and respond — by sending anonymous timing measurements to our own server. This uses no cookie, sets no identifier, and cannot be tied back to you or used to track you across sites. We use it solely to keep the site fast.

4. Third parties

The site loads images from Cloudinary and communicates with Supabase to power your account. These providers may process technical data such as your IP address in order to deliver content securely, but they do not set advertising or tracking cookies through this site. See the Privacy Policy for the full list of providers.

5. How to control cookies

You can delete or block cookies in your browser settings at any time. If you block strictly-necessary cookies, you will not be able to stay signed in to your dashboard; the public site will still work. Clearing the preference cookie simply means the site will ask for your language again.

6. Changes

If we ever introduce a new cookie, we will list it here before it goes live, and update the “last updated” date. If we ever adopted a cookie that required consent, we would ask for it first.