Privacy Policy

Last updated 25 May 2026. Applies to morocco.so and the journal at morocco.so/blog.

Short version: Morocco.so collects almost nothing about you. We do not currently run analytics or marketing pixels on this site. When you click a partner link to book something, you leave our site and the partner's privacy policy takes over. If you want anything deleted, write to us at the address at the bottom.

1. Who runs Morocco.so

Morocco.so is operated by Abderrahim under the brand Morocco.so. Contact: contact form. For privacy-specific requests use the same address with subject line "Privacy request".

2. What data we collect

2.1 Analytics

Morocco.so does not currently run any analytics or marketing pixels. There is no Google Analytics, no Facebook Pixel, no third-party tracker on the page. If we add one later (the candidate is a cookieless tool such as Plausible or Fathom that does not store personal data) this page will be updated and a notice will appear at the top for 60 days before the change takes effect.

2.2 Blog comments

If you leave a comment on the journal, WordPress stores the name, email and comment text you submit. Your email is never displayed publicly. We require admin approval on every comment before it appears, which means we read every one. We do not sell, share or sync this data anywhere.

2.3 Contact form

The contact form sends an email to us. The email contains whatever you typed. We keep the email until the conversation is closed, then archive it on our own server. We do not export contact-form data to third parties.

2.4 Server logs

Our hosting provider keeps standard web server logs for around 14 days (IP address, request path, user agent). These are used only for debugging and to block abusive traffic. They are not joined to analytics data and they are not used to profile readers.

3. Outbound links and partner redirects

Most outbound links on Morocco.so go to partners (Booking.com, GetYourGuide, Viator, Skyscanner, DiscoverCars, Airalo, SafetyWing, Allianz Travel, AXA Partners). When you click one, the partner sets their own tracking cookies on their domain and operates under their own privacy policy. Morocco.so does not see what you book or how much you pay. We see only that the click happened, via the partner's referral dashboard, in aggregate. Read the partner's privacy policy before you book if you care about the details.

4. Cookies

Morocco.so does not set advertising or analytics cookies. WordPress at /blog sets a small number of functional cookies if you comment or log into the admin (none of which identify casual readers). The full breakdown lives at /cookies.

5. How long we keep things

6. Your rights

If you are in the EU, the UK or California, you have explicit rights to access, correct, delete or export the personal data we hold about you. In practice that mostly applies to blog comments and contact-form emails (everything else is anonymous). Write to us, give us enough detail to find your record, and we will action it within 30 days.

7. Children

Morocco.so is not directed at children under 16. We do not knowingly collect data from anyone under 16. If you believe a child has submitted data through the comment form or contact form, write to us and we will delete it.

8. International transfers

Our hosting is in Europe. Most of our partners route data through the US (Booking.com Holdings, Skyscanner under Trip.com Group, etc.). When you click a partner link your data crosses borders under the partner's terms, not ours.

9. Updates to this policy

We update this policy when the things it describes change. The "last updated" date at the top is the authoritative version date. Material changes (a new analytics provider, a new data source, a new partner category) will be noted at the top of the page for 60 days after the change.

10. Contact for privacy requests

Use the contact form with subject "Privacy request" and we will get back to you within five working days. For the EU you can also lodge a complaint with your national data protection authority if you are not happy with how we handle a request.