Privacy Policy · Qasioun Cloud

This document explains what data we collect, why, who we share it with, and how long we keep it. It was written to describe what the site actually does, not to cover every eventuality.

The short version: contact form messages are forwarded to our inbox and not stored on the site, and we sell your data to nobody. Two measurement tools do run here, one of them an advertising one; both write cookies and report your visit to the company behind them. Both are named, with how to refuse them, in the cookies section below.

What we collect

From the contact form: your name, your email address, the subject or the service page you wrote from, and the text of your message. Those fields and no others.

From the newsletter form: an email address, and nothing else.

When you order hosting: name, email, a contact number, the domain you want, and what is needed to raise an invoice and record payment. These are handled in the billing and support system, which is separate from this site. Today an order reaches us over WhatsApp, so that conversation is governed by WhatsApp's privacy policy rather than ours.

Automatically, when you visit: the infrastructure provider writes technical server logs — IP address, request time, requested path, browser type — which are needed to run the site and protect it from abuse.

The site also runs Google Analytics 4, to count visits, see which pages are read and where a visitor arrived from. What we read from it is aggregate numbers we use to improve the site, not a file on you: we do not join them to your name, your email or your account with us, and we use them in no advertising. The cookies it writes on your device, and how to refuse them, are under Cookies below.

It also runs the Meta (Facebook) pixel. Most of the people who reach us reach us from a post on Facebook, and the pixel is what tells us which post — and later which ad — actually sent them. It records which pages you opened here and when, the kind of device and browser you are on, and the site you came from, and it sends that to Meta. We give it no name, no email and nothing you typed into a form, but it is an advertising tool rather than a counter: what reaches Meta is used for Meta's own purposes too, among them building an advertising audience, under its policy and not ours. How to stop it is under Cookies below.

Three actions on the site are reported to it as well, each as nothing more than the bare fact that it happened: tapping an order or enquiry button that opens WhatsApp, sending the contact form, and subscribing to the newsletter. The name, the address, the message and the domain you asked about are not part of any of them. We report them because ordering finishes on WhatsApp, off this site — without them the pixel could tell us that a post brought a reader and never that it brought an enquiry.

What we never collect: card or wallet details (no payment passes through this site), your geographic location, or any special-category data.

Why we collect it

To answer you. Contact form data is used to reply to your message and for nothing else. We do not add your address to a mailing list because you wrote to us.
To send the newsletter, if you subscribed to it yourself, and until you unsubscribe.
To perform the contract, if you become a subscriber: opening the account, invoicing, sending renewal reminders, providing support.
To operate and protect the service: the technical logs that surface a fault or an abuse attempt.
To know what works: which page, post or ad brought someone here, so that what we spend on reaching people is not spent blind.
To meet a legal obligation, where a competent authority requires it.

Who we share it with

We share only what is necessary. Most of those we share with are providers acting on our behalf; the two measurement platforms at the end of the list are the exception, in that each also uses what it receives for its own purposes. We do not sell, rent or trade your data for marketing purposes, with anyone, under any circumstances.

The hosting and infrastructure provider. Subscriber sites run on servers in a data centre in Frankfurt, Germany, and this site is served through a content delivery network. Both have technical access to what passes through their servers.
The email provider. Contact form messages and the newsletter are sent through a transactional email provider based in the European Union. It processes the content in order to deliver it, and holds newsletter subscriber addresses on our behalf.
The billing and support system, for subscribers, with the data needed to raise an invoice and open a support ticket.
Google, as the operator of the visitor-measurement tool. The visit data described above reaches it, and it processes that on our behalf under its own policies.
Meta, as the operator of the advertising pixel. The same visit data reaches it directly from your browser; it uses it on our behalf to measure what our posts and ads bring in, and for its own purposes under its own policy.

Your data is processed in Germany, given where those servers are, which may be outside your country of residence. That is a technical necessity of providing the hosting service itself, not a commercial choice.

You can ask us to name any of these providers at any time and we will.

How long we keep it

Contact form messages are not stored on the site. The server validates the shape of the fields, forwards the message to our inbox, and forgets it — there is no database and no log line carrying your address. The message then sits in our mailbox as any incoming email does, and is deleted on request.
Newsletter address: until you unsubscribe. Every message carries an unsubscribe link, and using it removes the address.
Subscriber data: for the life of the subscription, then 21 days after it is suspended or ended, as the Terms of Service set out, then deleted. Financial records that law requires us to keep are the exception, for as long as it requires.
Technical server logs: for a short period set by the infrastructure provider; they rotate and are overwritten automatically.
The measurement cookies: for as long as each is set to last, below — clearing them at any point ends it earlier.

Your rights

At any time you may ask for:

Access to what we hold about you.
Correction, where it is wrong or out of date.
Deletion, for anything we are not required to keep under a live contract or a legal obligation.
A copy of your data in a readable format, if you are a subscriber.
Unsubscription from the newsletter, without it affecting your service.
Objection to a particular processing activity — we will either show you its basis or stop.

Send your request to info@qasioun.cloud from the address we hold for you, and we will answer within 30 days at the latest. There is no charge for this.

Cookies

We show no advertising on this site and sell no ad space on it — but it carries an advertising pixel serving our own ads on Facebook. These are the files that may be written to your device, and no others:

The language cookie, a functional one recording the display language you chose — Arabic or English — so the site opens in it next time. It carries no identity, is read by nobody else, and deleting it breaks nothing beyond that memory.
_ga, written by Google Analytics. It holds a random number that tells one browser from another, so a visitor is counted once rather than twice. It lasts two years.
_ga_ followed by the property id, also written by Google Analytics, holding the state of the current session. It lasts two years.
_fbp, written by the Meta pixel, holding a random number identifying the browser, by which Meta attributes a visit to a post or an ad. It lasts three months.
_fbc, written only if you arrived from a link carrying an ad identifier, which it stores for the same purpose. It lasts three months.

None of those last four carries your name, your email or anything that identifies you as a person — a random number means nothing outside the count and the attribution. Meta, however, may link its own number to your account with it if you are signed in to Facebook in the same browser, and that happens at their end, not ours.

How to refuse them. Clearing cookies in your browser removes them; an ad blocker or the browser's own tracking protection stops both tools loading at all; Google publishes an official add-on that turns its measurement off across every site, at tools.google.com/dlpage/gaoptout; and Meta's ads and what feeds them are controlled from your own Facebook settings. The site works fully in every one of those cases — nothing here is conditional on accepting a cookie.

We use no fingerprinting of any kind, and there is no third-party embedded content on these pages — no maps, no video players, no social buttons loading anything from their own servers — beyond the two measurement scripts named above. Links to other sites are ordinary links: what those sites do once you follow them is governed by their policies.

If we later add an anti-automation check on the forms, or any component that writes a technical cookie, it will be named here and the last-updated date at the top of the page will change.

Changes to this policy

We may amend it if what we collect or who we share it with changes. The amended version is published here with a new date, and a material change is notified to subscribers by email.

Contact

For any privacy question, or to exercise any of the rights above: info@qasioun.cloud