Gateway to Morocco’s cinema country

Ouarzazate · Drâa-Tafilalet
Sign in

OUARZAZATE CITY

Cookies & storage

Device storage used by the current portal, and how to control it.

Updated 7 October 2026

Sign-in and requested services

Authentication can use necessary session cookies controlled by the sign-in service. Browser permission for location is separate from cookie consent. Storage strictly necessary for a service you explicitly request may be exempt from consent under § 25(2) TDDDG; other storage needs the appropriate consent before use.

Language, currency and theme

The portal stores ocz-language, ocz-currency and ocz-theme in local storage to remember your selected settings. The ocz-language cookie also indicates the current language and is scoped to this website. Local-storage values remain until you clear them or change the setting. These values do not contain your name or payment details.

Session display preference

ocz-splash-seen in session storage remembers whether the introduction has been shown in the current tab. It normally clears when that tab’s browser session ends. It is not an advertising identifier.

External services and advertising trackers

The current portal does not load advertising or analytics trackers in its page code. External websites have their own policies when you open them. Adding advertisements does not authorise tracking: any future non-essential analytics, advertising cookies or embeds must be reviewed and, where required, blocked until consent, with an equally accessible refusal option.

Control your storage

Change language, currency and theme in the header. Clear this website’s cookies and site data in your browser to remove local settings; this can sign you out. Deleting browser data does not delete server-side saved items or account records: request their deletion separately. Blocking necessary cookies can prevent account features from working.

Administrator security

Private administrator access uses a salted password hash and an eight-hour, secure HTTP-only session cookie. Session tokens are stored as hashes. Password changes revoke other password sessions. Failed login attempts are limited using hashed connection identifiers and short-lived counters. Brevo keys saved in the dashboard are encrypted and are not displayed again; they are sent only to Brevo to verify the connection and send requested emails.

Useful links