Cookie Policy

A cookie is a small text item that a website asks your browser to store and to send back on subsequent visits. Cookies allow a website to remember things about your visit — for example, that you are signed in, or that you prefer the Arabic interface — without re-asking you each time.

In addition to traditional cookies, the Service relies on two equivalent storage mechanisms: localStorage (used to mirror the locale and theme preferences across tabs) and Service-Worker-managed Cache Storage (used to cache static assets so the portal loads quickly). For brevity, this Policy refers to all of these as "cookies."

Skyline Cloud Email is a paid business service. We do not need to track our customers across the internet to make money, and we do not. The authenticated portal at cloud.alskyline.com deliberately does not run any of the following:

The cookies we do set fall into only two categories: strictly necessary, and functional UI preferences. Both are listed in the inventory table further down this page.

Strictly necessary cookies are required for core operation of the portal. The Service cannot function without them. Under the PDPL Implementing Regulations and equivalent international standards (e.g. ePrivacy Directive Article 5(3) exemption), these cookies do not require prior consent because they are strictly necessary for the service explicitly requested by you (signing in to your account).

Functional cookies remember UI preferences such as your selected language and theme. We treat these as opt-in by your action of changing the setting; if you reset your browser, the next visit will start in our defaults (English, light theme).

Analytics cookies: none. We do not run analytics cookies on the authenticated portal. The marketing site at alskyline.com may use server-side analytics that do not set cookies.

Marketing cookies: none. We do not advertise inside the Service and we do not target ads based on Customer Content.

The Saudi Personal Data Protection Law and its Implementing Regulations require that the processing of personal data is lawful, fair, and transparent, and — where consent is the basis — that consent is freely given, specific, informed, and unambiguous.

For the strictly-necessary cookies described above, the lawful basis is performance of the contract you entered into when you signed up for the Service: without these cookies the Service cannot deliver to you the very thing you asked for.

For functional cookies, the lawful basis is your specific action in changing the setting. We will, in a future portal release, surface a one-time consent banner offering an explicit accept / reject control on the first visit; until that banner ships, the only functional cookies we set are those that record an action you have just taken (changing language or theme).

You can clear, block, or restrict cookies through your browser's settings. The exact path varies by browser; the official guidance is:

Blocking the strictly-necessary cookies will prevent the portal from working — you will not be able to sign in. Blocking the functional cookies will reset your language and theme to the defaults on every visit.

The portal honours the spirit of the "Do Not Track" (DNT) browser signal by virtue of running no tracking in the first place. The presence or absence of a DNT header therefore makes no operational difference: we do not change behaviour based on it because there is no tracking to disable.

If we add a new category of cookie — for example, a privacy-respecting analytics product, or a customer-support chat widget — we will update this Policy and, where the new cookie is non-essential, will surface an explicit consent control before setting it.