Privacy policy

This policy describes the processing of personal data carried out through this site, in accordance with Loi 18-07 of 10 June 2018 on the protection of natural persons in the processing of personal data.

The data controller is DERDAR RYAD, an auto-entrepreneur who operates this site under the trade name Algeria Agency; full details appear in the legal notice.

Contact form on the industry pages and the “Client acquisition” page: name, company, phone, email address, what you sell and whether you already advertise.

Contact form: name, email address, subject and message content. Call booking form: chosen slot, name, company, email address and, if you wish, a note. Call-back form (the “Book a free call” page): name, phone number, when you would like to be called and, if you wish, an email address, a company, your line of business and a note.

The free consultation page (Google advertising): your business name, your name, a mobile number, your e-mail address if you wish, and your agreement to be called back; then, if you wish, your line of business, your wilaya, a link to your page or website and an advertising-budget range. With the request we record the advertisement that brought you (the Google click identifier gclid, gbraid or wbraid, the utm parameters and the headline shown), the landing page, your browser, an irreversible fingerprint of your IP address and how far you watched the explainer video.

We collect no sensitive data within the meaning of Loi 18-07, and we ask you not to enter any in a free-text field.

The site sets two analytics cookies and advertising cookies — those of the Meta pixel and the Google Ads tag — all third-party and all set the moment you arrive; a single link at the foot of every page stops all of them and deletes them: see the cookie policy for details.

Data from the contact form on the industry pages and the “Client acquisition” page is used solely to look at your request and get back to you about it. Booking and call-back form data is used solely to arrange the call you asked for, and contact form data solely to answer your message.

Data from the free consultation page is used to call you back to arrange the consultation. The advertisement that brought you is used to tell Google Ads which of its advertisements produce consultations and clients: each week we send it back the click identifier, the date and, if you become a client, the amount signed — never your name or your number.

The basis is your consent, given by voluntarily submitting the form. You can withdraw it at any time.

We do not use this data for unsolicited outreach, and we do not add it to any mailing list without an explicit request from you.

Data is not sold, rented or transferred to third parties for commercial purposes.

Your submission is stored in our own database: that record is the authoritative one, and it is what we consult in order to reply to you.

That database and this site are hosted outside Algeria, with specialist providers. The site is served by Vercel, which also measures its traffic — which pages are requested and how fast they render, with no cookie and no profiling; the database, the accounts and the files you send us are with Supabase; the technical counters that limit abuse are with Upstash; error reports, which contain neither your contact details nor the content of your messages, are with Sentry. Our domain name is registered with Hostinger and resolved by Cloudflare: in that capacity Cloudflare sees the address you are asking for this site from, and not what you do on it. Cloudflare also forwards mail sent to our contact address into our mailbox, and so sees its contents in passing. That mailbox is hosted by Google, and since August 2026 our team reads and answers it from our own administration console over an IMAP connection: a message sent to contact@algeriaagency.com is therefore read there as it would be in any mail client, and our replies go out from that same address. We hosted this site in Algeria until August 2026 and no longer do: we would rather say so plainly than leave an older sentence implying otherwise.

A copy of the content you send us also leaves by email, through Resend, a delivery provider established in the United States, to notify us of your message. We limit ourselves to providers offering contractual confidentiality guarantees; if you would rather no copy left the country, call 0792 53 50 30 instead of using the form.

If you have a client account, your dashboard notifications are also sent to you by email, through the same provider. The message carries the notification’s own heading — an invoice number, a document name, a ticket subject — and never the content of a message or an attachment. Every one carries an unsubscribe link that stops these notifications without closing your account; invitation and password-reset mail keeps arriving, because it is the only way to regain control of an account.

On the free consultation page the form may be protected by Cloudflare Turnstile, a bot check run by Cloudflare: it then sees your IP address and technical signals from your browser, once, to verify that the submission comes from a person. That page’s explainer video is served from Supabase; it loads only if you press play, and Supabase then sees your IP address, as any server sending you a file does.

If you use the Algeria Agency app on your phone, it receives its notifications through Expo, a service based in the United States that hands them to Apple or Google depending on your device. Expo sees your phone’s notification identifier, the notification’s heading and the screen it opens — never the content of a message or an attachment. The app keeps your session, your language, your settings and a copy of the screens you last opened on the phone, so that it opens without a connection; the photos, videos, voice notes and transfer receipts you send through it are stored at Supabase, like the files you send us through the site. Its error reports go to Sentry, as the site’s do, without your contact details or the content of your messages. In the app you can switch off each kind of notification except those about an invoice or a payment, and your phone’s settings can switch them all off. Signing out erases the session and the offline copy.

If you use Sahbi, our assistant, the text of your question and the extracts of our own pages used to answer it are sent to Cerebras, a compute provider established in the United States, for as long as it takes to produce the reply. The content of our pages is also sent to Google to be indexed, so that Sahbi can find the right page; that is our own public text, never your messages. Sahbi is not required to use this site — every page it cites can be read directly.

If you call Sahbi rather than writing to it, the conversation happens directly between your browser and Google: your voice is sent there to be understood, and the reply comes back spoken. It passes through no server of ours, and we keep neither a recording nor a transcript of it — so Google’s privacy policy applies to that exchange in addition to this one. Your browser asks your permission to use the microphone before a first call, refusing it prevents nothing else on this site, and a call stops by itself after ten minutes. During the call the assistant searches our own pages: it is those searches, a few words each, that reach us, and nothing of your voice.

On this site’s optician demonstration (Optique Gouraya, a fictional shop), you can choose to send a photo of a prescription to have it read. The photo goes from our server to Google’s model, which reads the values off it and sends them back to be shown on your screen; we do not keep it, it is not written to our logs, and the values read are not recorded anywhere — they exist only in the open page, for the length of your visit. Google is established in the United States and acts here as a processor. Nothing obliges you to send a photo: you can type the prescription in yourself, or use one of the four fictional samples provided.

On this site’s insurance demonstration (Hima Insurance, a fictional company), you can choose to add a photo of damage of your own to a demonstration claim. The photo goes from our server to Google’s model, which estimates the damage, and is then kept for twenty-four hours at most in our storage at Supabase, attached to your own demonstration space alone, before being deleted with it; it is not written to our logs. Google is established in the United States and acts here as a processor. Nothing obliges you to send a photo: the demonstration provides four sample photos, and its identity documents are fictional specimens, never yours.

On this site’s fashion demonstration (IBRA, a fictional label), you can try a garment on a photo of yourself, once you have agreed to it. Your photo and the garment’s then go once from our server to Google’s image model, which composes the preview and sends it back to us to show you; we keep neither your photo nor the preview, and neither is written to our logs. If, with a second agreement, you choose “Save to my profile”, the preview is kept for twenty-four hours at most in our storage, with Supabase, attached to your own demonstration space alone, and then deleted. Google is based in the United States and acts here as a processor. Nothing obliges you to send a photo: trying pieces on the demonstration’s models needs none.

On this site’s building-materials demonstration (Qarmoud, a fictional group), you can choose to show its assistant a photo of a room you want to renovate or of a handwritten materials list, once you have agreed to it. The photo goes once from our server to Google’s model, which describes the room or reads the list’s lines and sends that text back to us to show you; we do not keep the photo and it is not written to our logs. It is our own search, not the model, that matches each line to a catalogue item. Google is based in the United States and acts here as a processor. Nothing obliges you to send a photo: the assistant answers in writing too, and the demonstration provides sample photos.

On this site’s logistics demonstration (Khatt, a fictional carrier), a seller can photograph a page of her order notebook to turn it into shipments, once she has agreed to it. The photo goes once from our server to Google’s model, which copies out its lines and sends that text back to us; we do not keep the photo and it is not written to our logs. She can also paste an order message received through a messaging app: the phone numbers in it are masked on our server, then the text goes once to Cerebras, which reads it to suggest a draft shipment; we do not keep it. In both cases our own code recognises the places and amounts, and every line is checked by hand before anything is created. Google and Cerebras are based in the United States and act here as processors. Nothing obliges anyone to send a photo or a message: the demonstration provides sample pages and messages.

If you are a client and we run your campaigns or your search visibility, we read the statistics of your own accounts on your behalf: Meta for social advertising, Google for Google Ads and for Search Console. What leaves is the account identifier or the site address — both yours — and what comes back are your own figures. No data about your customers passes through there, and you can revoke our access at any time from those platforms’ own interfaces, without going through us.

If you write to us on WhatsApp — the link is in the footer of every page — your number and the content of your messages pass through Meta’s platform before they reach us, and Meta’s privacy policy applies to that in addition to this one. That is how WhatsApp itself works, not an additional processing choice of ours. To reach us without going through Meta: the form, email, or the telephone.

If you ask to be called back from the “Book a free call” page, your name, your number, when you would like the call and your language are also sent to us as a WhatsApp message, which Meta’s platform delivers to our own number so that we can call you back straight away. That information therefore passes through Meta, established in the United States, acting here as a processor. Your email address, company, line of business and note are not included.

Unless you have turned audience measurement off, Google receives the pages you view on this site, the date of your visit, your country and your device type, through Google Analytics. Google is established in the United States and acts here as a processor. This data is never joined to anything you send through the forms, and the "Turn off audience measurement" link at the foot of every page ends the transfer.

On the same terms, Meta receives the same information through the Meta pixel installed on this site, and the difference between the two transfers is worth stating plainly. Google Analytics tells us which pages get read. The pixel serves advertising: it lets Meta attribute a contact request or a booked call to the advertisement that brought you here, and build audiences of people who resemble you. If you have a Facebook or Instagram account, Meta is able to join all of this to that account. Meta is established in the United States and acts here as a processor. The same link at the foot of the page ends this transfer at the same time as the one above: there are not two settings to find.

Google Ads also receives the fact that a form was sent, and the same irreversible fingerprint of your address or number, when you reach the confirmation page. It exists to attribute a request to the Google advertisement that produced it, as the pixel does for Meta. Google is established in the United States and acts here as a processor. The "Turn off audience measurement" link at the foot of every page stops this transfer at the same time as the other two, and deletes the _gcl_au cookie Google Ads sets.

And when you send one of our forms, our own server sends Meta its own copy of that submission. This is worth saying, because it is the one transfer your browser does not make and an ad blocker therefore cannot stop. It contains the IP address you are writing to us from, the name of your browser, and the two identifiers the pixel has already set. Since September 2026 it also contains an irreversible fingerprint of the email address or telephone number you leave us: a string computed from that value, from which nobody can recover it, but which lets Meta recognise an account it already holds the same address for. We refused to send it for a long time and this page said we would not; we changed our minds, and saying so seemed more honest than not. What still does not go: your name, the content of your message, your company name, your budget, or the slot you chose. It exists so that requests the browser could not report are not lost from the count, and it carries the same identifier as the browser transfer so that Meta counts one rather than two. If you have turned audience measurement off it is not sent: your browser passes that decision to us with the form, because our server cannot read it.

Requests sent from the industry pages that did not become engagements: three years from last contact, then deleted.

Requests sent from the free consultation page that did not become engagements: three years from last contact, then deleted.

Contact messages: two years from the last exchange.

Client data: the duration of the contractual relationship, then the statutory retention period applying to accounting and contractual records.

Comments and reviews left publicly on our clients’ accounts, where we handle them: ninety days, then automatic erasure from our servers. They remain visible on the originating platform, which we do not control.

Conversations held with an assistant we run for a client: twelve months from the last message, then automatic erasure. They are kept with no identity attached to the person who wrote.

Appointments taken inside a demonstration on this site: seven days, then automatic erasure. Nothing real is booked, and no telephone number or email address is collected.

You have rights of access, rectification, objection and erasure over your data. Write to contact@algeriaagency.com; we respond within thirty days.

We may ask for something that lets us verify your identity, solely to avoid disclosing your data to someone else.

You may refer the matter to the Autorité nationale de protection des données à caractère personnel (ANPDP) if you consider the processing non-compliant.

On the server side, your submissions are kept in a database reachable only by the people in the company who handle enquiries. On the browser side the site uses only a language cookie, a technical anti-spam token, the audience-measurement and advertising cookies described in the cookie policy, and — if you closed the strip announcing that measurement, or turned it off — the record of those two facts. The message offering you the other languages leaves the same kind of record, once you have closed or followed it, so that it does not return. If you have access to your client area, your browser additionally keeps the session cookie issued by Supabase, which identifies you for the length of your sign-in. If you are a client and you read the help guides in your portal, your browser keeps an offline copy of them, with no data from your account in it. If you open Sahbi, our assistant, your browser keeps, for the life of the tab, a random identifier tying your questions together and a note that its greetings have already been shown to you — counted separately for the public site and for your own area, because the message is not the same in each; none of them holds personal data and all disappear when the tab closes. If you are a client and have not yet turned on two-factor authentication, your browser also remembers that you dismissed the offer to turn it on, so that it is not put to you on every visit; that record disappears by itself once you turn it on. Finally, the site’s search keeps your last five searches, in your browser only, until you clear them. All are described in the cookie policy.

The Numidia Voyages demonstration pages add two cookies, nv_session and nv_prefs, described in the cookie policy; they concern that fictional agency alone and hold no personal data. The Hima Insurance demonstration pages add one, hm_session, described in the same place, which holds no personal data either.

The Tarab demonstration (ticketing and events agency) adds one cookie, ev_session, and its door-control app keeps an offline scan queue in your browser (IndexedDB “tarab_scan”) and a copy of its own screens; all of it is described in the cookie policy, concerns that fictional company alone and holds no personal data. Messages you write in a demonstration livestream chat are public to other visitors, signed with a generated alias, and erased within twenty-four hours.

The Nakhla School demonstration adds one cookie, ep_session, described in the cookie policy; it concerns that fictional school alone and holds no personal data.

The Maison Nouara demonstration adds one cookie, nr_session, and one tab key, nr.curtain-seen, both described in the cookie policy. Its beauty-analysis page reads the photo you choose to produce written advice, then forgets it: the photo is never stored, neither on our servers nor by the analysis provider beyond the time of the answer.

The Sakina Clinic demonstration adds one cookie, sk_session, and four tab keys, sk.large-text, sk.intro-seen, sk.triage-prefill and sk.tour-step, all described in the cookie policy. All of its health data is fictional: no field lets you type your identity, the only free text (your question to the assistant or to the triage, 600 characters at most) stays twenty-four hours in your demonstration space and is then deleted, and a photo shared during a teleconsultation goes straight from one browser to the other and is kept nowhere. If you dictate your question to the triage, your own browser’s speech-recognition service transcribes the audio, not us.

The Qaws Real Estate demonstration adds one cookie, im_session, four local-storage keys, im.saved-homes, im.compare-list, im.saved-searches and im.price-unit, and one tab key, im.curtain-seen, all described in the cookie policy. It collects no personal data: its viewings, offers, reservations and payments use demonstration contacts and cards already filled in, and its messages are shown in the app instead of being sent.

The IBRA fashion demonstration adds one cookie, ib_session, and three browser keys, ib.curtain-seen, ib.fit-answers and ib.recent, all described in the cookie policy; they concern that fictional label alone. What you do in it — bag, orders, measurements, saved try-ons, messages — is kept in a demonstration space in our database, deleted twenty-four hours after your last action. Messages you write in the chat of a demonstration live are filtered, then broadcast through Supabase Realtime to the other people watching the same live, under an anonymous label and without your name; they stay in your space for twenty-four hours at most.

The Qarmoud demonstration adds one cookie, qm_session, one tab key, qm.preloader-seen, and three local-storage keys, qm.favourites, qm.recent-searches and qm.planner-draft, all described in the cookie policy; they concern that fictional group alone. What you do in it — bag, quotes, orders, planner projects, renovation requests — is kept in a demonstration space in our database, deleted twenty-four hours after your last action. Its forms use pre-filled demonstration contacts and its messages are shown in the app instead of being sent; the only free texts, bounded in length (your question to the assistant, a project note), stay in that space and disappear with it.

The Khatt demonstration adds one cookie, kh_session, two tab keys, kh.preloader-seen and kh.calc-draft, one local-storage key, kh.recent-tracking, and, for the courier app offline, an IndexedDB database, kh.courier-queue, and a cache, kh.courier-v1, all described in the cookie policy; they concern that fictional carrier alone. What you do in it — shipments, scans, cash collected, quotes, bookings, settings — is kept in a demonstration space in our database, deleted twenty-four hours after your last action. A barcode scanned with the camera is decoded in the page: no image leaves your device. Its recipients, phones and addresses are demonstration data picked from a list, and its messages are shown in the app instead of being sent.

The Dar Chemâa demonstration adds one cookie, dc_session, one tab key, dc.preloader-seen, and three local-storage keys, dc.mood, dc.ramadan and dc.table-cart, all described in the cookie policy; they concern that fictional hotel alone. What you do in it — room and table bookings, orders, requests, quotes, settings — is kept in a demonstration space in our database, deleted twenty-four hours after your last action. Its guests, their identity documents and their contact details are demonstration data picked from a list; a short free text you write (a special request, an allergy, a gift card’s message) stays in that space and goes with it. Its e-mails, text messages and chats are shown in the app instead of being sent.

The forms are protected against automated submissions. In the event of a security incident affecting your data, we will inform you promptly.

The Pizzeria Dar Zitoun demonstration keeps one key in your browser, aa.demo-pizza, holding only what you did in it — events of a fictional shop, with no name or number — and, so that a second device can join it, a copy of that list stays on our server for 24 hours before it is deleted.