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 full identity of the data controller appears in the legal notice and remains to be completed ([TO BE COMPLETED]) before publication.

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.

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 five 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.

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.

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 an audit 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.

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 — and nothing else: not your name, not your email, not your number, not the content of your message, not even in encrypted form. 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.

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 two audience-measurement 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. All are described in the cookie policy.

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