Cookie Policy

Last updated 28 May 2026.

There are two kinds of cookies you might encounter while using Morocco.so: the cookies we set ourselves, and the cookies our partners set when you click through to them. The first list is small and functional. The second list lives on partner domains, under each partner's own terms, and we have neither access to it nor control over it. This page documents both as plainly as we can.

1. Cookies we set ourselves

The static pages on Morocco.so (the homepage, the six service pages, About, Contact, Privacy, the Disclosure page, this Cookies page) are flat HTML and set no cookies at all. Nothing to consent to, nothing to clear.

The journal at /blog runs on WordPress, which sets a small number of functional cookies in response to specific actions. Casual readers do not receive any of these. They appear only if you log in, comment, or interact with the page in a way that needs state to be kept across requests.

That is the full list of cookies Morocco.so sets on its own domain. No analytics. No advertising. No retargeting. No fingerprinting.

2. Cookies our partners set

When you click an outbound button to a partner ("Check rates on Booking.com", "Compare GetYourGuide tours", "Find a Morocco eSIM on Airalo", etc.), you leave Morocco.so and arrive on the partner's domain. The partner then sets its own cookies, on its own domain, under its own privacy and cookie policy. We do not place those cookies, do not read them, and do not control how long they last.

The cookies partners set fall into three rough buckets:

• Referral cookies — credit the click-through to Morocco.so so the partner can pay us the agreed referral if a booking is completed within the partner's cookie window. Examples: Booking.com aid, GetYourGuide partner_id / partner_ref, Skyscanner associateid, Airalo airalo_aff, SafetyWing sw_referral. Duration is typically 30 to 90 days.
• Functional cookies — remember your search filters, your selected dates, your cart state, your language preference inside the partner's own site. These power the partner's booking flow itself and are not set by us.
• Analytics, advertising and retargeting cookies — the partner's own measurement and ad stack (Google Analytics, Meta Pixel, Criteo, Bing UET, etc.). These follow you across the wider web if you have not opted out. They are entirely a partner matter; opting out of them happens through the partner's own consent banner or your browser's tracker-blocking setting.

Each partner's authoritative cookie list lives on their site:

3. Cookie consent and why there is no banner

European ePrivacy rules and the GDPR require informed consent for cookies that are not strictly necessary. Morocco.so does not show a consent banner because no consent is required for what we do on our own pages: no analytics, no advertising, no third-party measurement. The functional WordPress cookies above only fire after you have already opted into the feature they support (you logged in, you ticked "remember me" on a comment), so they sit under the strictly-necessary exemption.

Partners are a different matter. Their consent banner is the one that governs what they set when you land on their site. If you decline cookies there, the partner's site usually still works, but features depending on cookies (the cart, retargeting, optional analytics) will be turned off.

4. What we deliberately do not set

• No analytics cookies. Not Google Analytics, not Hotjar, not Microsoft Clarity, not Plausible, not Fathom. Nothing. We currently have no tool that measures who visits, where from, or for how long. The only data we see from Morocco.so itself is partner referral counts from each partner's own dashboard, in aggregate, after the click left our site.
• No advertising or retargeting cookies. No Meta Pixel, no Google Ads tag, no Criteo, no LinkedIn Insight. No banner ads, no display network, no "people who viewed this also looked at" widgets.
• No third-party social embeds with default tracking. The social icons in our footer are static HTML links. Clicking them opens the social site in a new tab; visiting our pages does not load YouTube, Twitter / X, Instagram or TikTok scripts.
• No fingerprinting. We do not run libraries that profile your device, fonts, canvas or audio context.
• No data sale. We have no data to sell. If we ever did, this page and the Privacy Policy would say so explicitly 60 days before any change takes effect.

5. How to refuse or remove cookies

Browser settings let you block or clear cookies per-domain:

• Chrome: Settings → Privacy and security → Cookies and other site data → See all site data → search "morocco.so" and / or the partner domain → Remove.
• Firefox: about:preferences#privacy → Cookies and Site Data → Manage Data.
• Safari: Preferences → Privacy → Manage Website Data.
• Edge: Settings → Cookies and site permissions → Manage and delete cookies and site data → See all cookies and site data.

Blocking cookies on morocco.so has no observable effect because no cookies are set for casual readers in the first place. Blocking cookies on a partner domain may break the partner's checkout flow; that is a partner-side limitation we cannot fix.

6. Do Not Track and Global Privacy Control

Morocco.so honours the Do Not Track (DNT) browser signal and the Global Privacy Control (GPC) signal by default. There is no behaviour to change because we never set tracking cookies in the first place. The signal is logged where supported and the answer is always the same: nothing tracked, nothing shared.

7. Updates to this policy

If we add a new tool that needs cookies (analytics, even a cookieless one, or a new functional feature), this page will be updated and a notice will appear at the top for 60 days before the change takes effect. The "last updated" date at the top is the authoritative version date.

For broader data questions see the Privacy Policy.