Cookie policy

1. Always on: needed for the site to work

• cp.locale: remembers whether you chose Arabic or English.
• cp-theme: remembers light or dark display.
• cp.token, cp.locationId (local storage): keep you signed in once you have an account.
• cp.consent: remembers your choice on the cookie notice.
• cp.attribution (local storage): remembers which campaign or link brought you here. It never leaves your browser until you create a store, when it is saved with the store so that we can tell which campaigns work. See the privacy policy.

2. Only if you accept: advertising and measurement

When you accept, these tags load on our public pages. They set their own cookies (such as _fbp, _ga and the li_ cookies), use them to recognise your browser across sites, and send the provider the pages you view and whether you signed up. If you click “Book a 15-min demo” or WhatsApp on the sign-up page, Meta also receives a lead event naming that button and nothing about you, and our server sends Meta the same lead (the same event id, the page address, and those Meta cookies if they are set).

• Meta Pixel (Meta): measures which Facebook and Instagram ads lead to sign-ups and helps show our ads to people who visited. Meta’s policy.
• Google tag (Google Ads and Analytics): measures which Google ads and pages lead to sign-ups. Google’s policy.
• LinkedIn Insight Tag (LinkedIn): measures which LinkedIn ads lead to sign-ups. LinkedIn’s policy.

These providers act as independent controllers of what their tags collect. We only load the tags that we have set up.

Creating a store is also reported from our server to Meta, so we can tell which ads lead to a real signup. That report carries a hashed email, your IP address, your browser and the page address, and it is sent whether or not you accepted these tags. If you did accept, it shares an id with the browser sign-up event so Meta does not count you twice.

3. Where the tags never run

Never inside the signed-in product, the register, receipts, or any page whose address carries a private link or token (such as a password reset). They run only on the home page, pricing, sign-up, developers and these policy pages.

4. Changing your mind

Choose “Cookie settings” in the footer of any page to accept or decline again. Declining is as easy as accepting, and nothing on the site depends on it. If your browser sends the Global Privacy Control signal, we treat it as a decline. You can also delete cookies and site data in your browser settings, which removes anything already stored.

5. Contact

Questions about cookies: support@pragmatech.work.