Legal notice

This English version is a courtesy translation provided for convenience only. The French version is the legally binding text.

Site publisher

GLOBAL CONSULTING TECHNOLOGY
Establishment (sole proprietorship)
Legal representative: Sylvère Alban Joël Bamenou
Quartier Zogbo (îlot 1898, parcelle F), 9ᵉ arrondissement, Cotonou, Littoral, Bénin
APIEx establishment declaration No. 0053781-COO (22/06/2020)
Contact: contact@atelieriacomplet.com

Hosting

The site, API and database are hosted on a virtual private server (VPS) provided by Hostinger International Limited, 61 Lordou Vironos Street, 6023 Larnaca, Cyprus. The server is located in the United Kingdom (Manchester data centre). Accounts (sign-in and email address) are managed by Firebase Authentication, provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

Intellectual property

The entire content of the handbook "The Complete AI Workshop" (original French title: "L'atelier IA complet"), including texts, illustrations and diagrams, is protected by copyright. Buying the handbook grants a personal reading right; any reproduction or distribution without authorisation is prohibited.

Personal data

The data collected (email, first name, reading progress, My workshop points, streak and badges, logbook ticks and notes, purchase history) is used to run the service. With your consent, and only with it, audience measurement and the TikTok and Meta advertising pixels described below are added to that: those measure our ads and target the next ones, which is not running the service. Declining, or withdrawing consent you had given, takes nothing away from the site. Card payments are processed by Stripe. Mobile Money payments are processed by KkiaPay, our payment provider. For that payment, the site passes on to it your email address (your account's if you are signed in, otherwise the one you enter on the purchase page), your account name if you are signed in (the first name given when signing up, or the full name on your Google account), the amount, the chosen country, a payment reference and the address of the purchase page. KkiaPay also receives the phone number you enter in its window; we do not keep that number. If you pay without being signed in and the payment does not go through, the email address you entered is deleted thirty days after the payment was started, which leaves time to settle a payment reported to us. No banking details are stored on our servers. To exercise your rights (access, rectification, deletion): contact@atelieriacomplet.com.

Account created for a gifted access

Access is sometimes given as a gift: in that case an account may be created at your email address on our initiative, without you asking for it, so the handbook opens for you. What is then kept is your email address and the record of that gifted access, for the sole purpose of giving you access to the handbook and telling you about it in a single message. No marketing, no resale, no sharing. To have that account and address deleted, write to contact@atelieriacomplet.com: the request is handled by hand, there is no automatic deletion.

Address left to follow updates to the handbook

At the bottom of the free sample, an optional form offers to leave an email address. Purpose: to tell you about updates to the handbook, and nothing else. No third-party marketing, no resale, no sharing. Legal basis: your consent, given by submitting the form; the sample is readable with no account and no address, and leaving yours unlocks nothing. What is recorded: your address, the date you signed up, the site language and the page you left it from. Retention: until you ask to be removed, and at most three years after the last message sent. Unsubscribing and deletion: write to contact@atelieriacomplet.com. There is no automatic unsubscribe link yet, the request is handled by hand. No automated mailing is wired up to date.

What the TikTok and Meta pixels report about your visit

If you have accepted the TikTok pixel, your browser reports four precise moments to TikTok: the purchase page being shown, leaving for card payment, the purchase itself, and the creation of an account. The first three carry the name of the handbook, the amount and the currency (in euros); the purchase also carries the payment session's number, which is precisely what keeps the same sale from being counted twice, since our server already reports it on its side. Mobile Money payments are never reported to TikTok, because it does not accept that currency. Until you accept, none of these events leaves, and TikTok's script is not even loaded.

At the moment of purchase, and only then, your email address also goes to TikTok, in hashed form (SHA-256). Its purpose is for TikTok to match that purchase with a person it already knows on its side. Better said plainly than dressed up: a hash is not anonymity. The same address always produces exactly the same hash, here as anywhere else, so it is a stable identifier that points to you; what it changes is that your address is never readable in the clear in what leaves, and nothing more. Our server, for its part, reports the purchase with no address at all, neither hashed nor in the clear: this send comes only from your browser, and only if you accepted the TikTok pixel.

If you have accepted the Meta pixel, your browser reports to it, on top of what the pixel sends by itself (detailed with the cookies, below), a single precise moment: the purchase itself, when you pay by card. What leaves then is the name of the handbook, the amount paid and the currency (in euros), and the payment session's number, which keeps the same sale from being counted twice, since our server also reports it on its side. Your email address does not go to Meta, hashed or in the clear: neither our code nor our server sends it, and "automatic advanced matching", the Meta setting that picks up addresses typed into forms, is switched off on our pixel. Mobile Money payments are not reported to Meta for now. Until you accept, none of these events leaves, and Meta's script is not even loaded.

Transfers outside the European Union

If you accept the advertising pixel, the information it sends (the page viewed, your IP address, your browser, the identifiers kept in its cookies) goes to TikTok. For the European Economic Area, the controller for that processing is TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland, jointly with TikTok Information Technologies UK Limited. Its EEA privacy policy, in its 30 November 2025 version, states that this information is stored on servers located in the United States, Malaysia and Singapore, and that these transfers rely on the European Commission's standard contractual clauses. If you have accepted, the purchase itself is sent to TikTok a second time, from our server rather than from your browser: what leaves is the amount, the currency, an order number and the advertising identifiers the pixel placed in your cookies. Nothing else. Neither your email address, nor your phone number, nor your IP address, nor your browser is sent that way, and the order number is the payment session's own, which says neither who you are nor what you have read. Until you accept, TikTok's script is not loaded at all and those identifiers do not exist: our server then has nothing to send, and sends nothing. Nothing leaves.

If you accept, the information the Meta pixel sends (the page viewed, the page you came from, your IP address, your browser, the identifiers kept in its cookies, the labels of the buttons you click, and, through a Meta setting we leave on, details about the content of the pages and the prices shown) goes to Meta. For the European Economic Area, the controller for that processing is Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland. That information is passed on to Meta Platforms, Inc. in the United States, on the basis of the "EU-U.S. Data Privacy Framework" adequacy decision adopted by the European Commission on 10 July 2023, with Meta reserving the European Commission's standard contractual clauses as an alternative mechanism. That framework is contested, and it is better said here than found out elsewhere: an appeal is pending before the Court of Justice of the European Union (case C-703/25 P), and if it succeeded, the basis for these transfers would change. For the collection carried out on this site and its transmission to Meta, Meta Platforms Ireland Limited and we are joint controllers within the meaning of Article 26 GDPR; what Meta does with that information afterwards is its responsibility alone, not ours. As with TikTok, if you have accepted, a purchase paid by card is sent to Meta a second time, from our server rather than from your browser: what leaves is the amount, the currency, an order number and the pixel's advertising identifiers, that is the ones it keeps in its "_fbp" and "_fbc" cookies, or, if it has not yet had time to write the latter, the "fbclid" of the landing address it is built from. Nothing else. Neither your email address, nor your phone number, nor your IP address, nor your browser is sent that way, and the order number is the payment session's own, which says neither who you are nor what you have read. Until you accept, Meta's script is not loaded at all and those identifiers are neither set nor read: nothing leaves from your browser, and our server has nothing to send, so it sends nothing.

Cookies

A banner asks for your consent on your first visit: until you have answered it, nothing is set, neither audience measurement, nor the referral cookie, nor the advertising pixels. You can accept everything, decline everything, or choose: audience measurement, the referral, the TikTok pixel and the Meta pixel each have their own switch, and accepting one does not accept the others. Declining takes nothing away from the site.

The full detail, cookie by cookie, follows the table, including the cookies TikTok and Meta set on their own domains.

Change my cookie choices

• Google Analytics 4 audience measurement, provided by Google: the "_ga" and "_ga_D17YYPKPKT" cookies, lasting up to 400 days. They count visits and show which pages are read. Set only if you accept.
• TikTok advertising pixel, provided by TikTok: the "_ttp", "ttcsid", "ttcsid_" followed by the pixel identifier, "ttclid" and "_tt_enable_cookie" cookies, lasting 13 months. TikTok also adds "ttclid" to the landing address when you have just clicked one of our ads. The script additionally keeps, for the lifetime of the tab, session and ad-context markers ("tt_sessionId", "tt_pixel_session_index", "tt_appInfo", and depending on the case "tt_hold_events", "tt_adInfo", "_tt_event_builder"). All of this measures the handbook's ads on TikTok and targets the next ones. Set only if you accept.
• When your browser downloads that script, TikTok sets a "_ttp" cookie of its own on its own domain (tiktok.com), for 13 months. It does not belong to us and cannot be deleted from this site. Set only if you accept.
• Meta advertising pixel, provided by Meta (Facebook, Instagram): the "_fbp" and "_fbc" cookies, lasting 90 days. Meta adds "fbclid" to the landing address when you have just clicked one of our ads, and "_fbc" is built from that parameter. According to Meta's own documentation, this pixel sends by default, with no setting on our part: the page you are viewing, the page you came from, your IP address, your browser, the pixel identifier, Meta cookies, and the labels of the buttons you click. That last point is written down by Meta and almost never repeated elsewhere, so we repeat it here. All of this measures the handbook's ads and targets the next ones. Set only if you accept.
• When your browser contacts Meta, Meta sets cookies of its own on its own domain (facebook.com), "fr" and "datr". They do not belong to us and cannot be deleted from this site. How long they last is set by Meta alone: no figure is given here, sources contradict each other and we would rather state nothing than state something false. Set only if you accept.
• Referral cookie "aff_ref", 30 days: it keeps the code of the person who recommended the handbook to you, so their commission can be credited if you buy. Set only if you accept.
• Reader local storage ("aic-page", "aic-visited", "aic-checks", "aic-fs", "aic-edition"): your current page, the chapters already read, the steps you ticked, the text size and the edition being displayed. This stays in your browser and is required for reading to work: it needs no consent. Points earned without an account ("aic-jeu-visiteur") stay there too, until you create an account: they then move to it and leave the device.
• Technical purchase storage ("aic-payconfig", for the tab only, and "aic-achats-signales"): the price shown and the purchases already confirmed, so the buy page is not left empty when the API is unavailable and the same payment is not confirmed twice. Required for the service.
• Sign-in hint ("aic-session"): remembers whether this browser was signed in to an account and whether the handbook was bought there, so the right header shows without downloading the sign-in module on every page. It contains no identifier, stays in your browser and needs no consent, as it is needed for the site to work.
• Your cookie choice itself is kept in your browser's local storage ("aic-consent-4"), so you are not asked again on every page. It is kept purpose by purpose: a yes or a no for audience measurement, one for the referral, one for the TikTok pixel, one for the Meta pixel. That name had already changed twice, each time something more was being asked for — advertising being added, then Meta — and the question was then asked again to everyone. Not this time: moving to a box-by-box choice asks for nothing more, so people who had already answered were not asked again. A yes given to the whole was carried over as a yes for each box, a no as a no for each, and the "Cookies" button now lets you refine it.

You can change your mind at any time, and box by box: the "Cookies" button reopens the banner on the detailed panel, with your current choices, and you can withdraw a single one before saving. Only the cookies of the box you withdrew are then deleted from your browser — "_ga" for audience measurement, "aff_ref" for the referral, the TikTok pixel's cookies and its session storage, "_fbp" and "_fbc" for the Meta pixel — and what it allowed is not loaded again; what you keep stays in place. One exception, said plainly: the "_ttp" cookie set on the tiktok.com domain and the "fr" and "datr" cookies set on the facebook.com domain do not belong to this site, and no site can erase another domain's cookie. You clear those from your browser's settings. Cookies

← Back to the home page