Cookie Policy

1. What Are Cookies?

Cookies are small text files that are placed on your device when you visit a website. They are widely used to make websites work, improve user experience, and provide information to site owners.

2. Types of Cookies We Use

• Strictly necessary cookies: required for the operation of the Platform. These include the session cookie used to keep you signed in and a security cookie used to protect forms against cross-site request forgery. These cannot be switched off in our systems. If you block them in your browser, you may not be able to sign in or use the Platform.
• Consent preference: when you respond to our cookie banner, we store your choice in your browser’s local storage so we can remember it on later visits. This is a similar technology to a cookie and is not used for advertising.
• Checkout hand-off: during a paid purchase we may use temporary browser storage so we can return you to the correct confirmation page after PayFast checkout. This storage is short-lived and is not used for advertising.
• Support chat (functional): on selected learner and customer pages we may load Crisp’s customer support widget so you can contact IT Support. Crisp may set first-party cookies on our domain with the prefix crisp-client/, and may use similar browser storage, to keep your support conversation available as you move between those pages. These are used to operate the support chat, not for advertising or marketing tracking.
• Advertising measurement (optional): if you choose “Accept all”, selected public pages may load the Meta (Facebook) Pixel so we can measure advertising campaign performance, attribute conversions (such as course views, checkout starts, and completed purchases), and optimise Meta ads. Meta may set cookies or use similar technologies on Meta’s domains for that purpose. This does not load when you choose “Only necessary”, or before you make a choice.

Optional advertising/measurement scripts (including Meta Pixel) are gated behind the cookie banner’s “Accept all” option and are only present on selected public pages. Crisp support chat is a functional customer-support service and is not one of those optional marketing scripts.

3. Third-Party Cookies

Some features involve third-party services that may set their own cookies on their own domains:

• PayFast: when you pay for a Course, you are redirected to PayFast’s checkout, which may set cookies on PayFast’s domain.
• Cloudflare Turnstile: login, signup, password reset, and some contact forms may load Cloudflare’s human-verification widget, which may set cookies on Cloudflare’s domain.
• YouTube: some Course lessons embed YouTube videos, which may set cookies on YouTube’s domain when you play them.
• Crisp: we use Crisp as a functional customer-support service on selected learner and customer pages (for example the course catalogue, course pages, your learning dashboard, the lesson player, quizzes, certificates, your profile, and the contact page). Crisp may set first-party cookies on our domain with the prefix crisp-client/ and may use similar browser storage so your support conversation/session can continue as you move between those pages. These cookies/storage are used for support functionality, not advertising or marketing tracking. If you start a conversation, the messages you send and any screenshots or file attachments you upload in the chat are processed by Crisp to provide support. Because this is a support service rather than analytics or marketing, the widget may remain available even if you choose “Only necessary” or have not yet responded to the cookie banner. Support chat can still be switched off entirely by us. We do not claim that Crisp is cookie-free.
• Meta Pixel: on selected public pages, and only after you choose “Accept all”, we may load Meta’s Pixel script from Meta domains (for example connect.facebook.net) for advertising measurement, attribution, and campaign optimisation. Meta may set cookies or use similar technologies on its own domains as part of that service.

We do not allow third-party advertising networks to set marketing cookies on the Platform until you accept optional cookies via the banner. Choosing “Only necessary” keeps those optional marketing scripts blocked.

4. How to Manage Cookies

You can manage cookies through your browser settings. Most browsers allow you to:

• See what cookies are stored and delete them.
• Block cookies from specific sites.
• Block all cookies.
• Delete all cookies when you close your browser.

If you disable or block certain cookies, parts of the Platform may not function properly.

5. Cookie Consent Banner

When you first visit the Platform, we display a cookie banner until you make a choice. The banner explains that we use cookies to keep you signed in, understand how you use the Platform, and improve our courses, and it links to this Cookie Policy.

You can choose:

• Accept all: we record your consent and enable any optional, non-essential scripts that are gated behind consent (if present on the page), including Meta Pixel advertising measurement on selected public pages. This does not control the Crisp support widget.
• Only necessary: we record that you want strictly necessary cookies only. Optional scripts that are gated behind consent remain blocked. The Crisp customer support widget is a functional support service and may still load on selected learner and customer pages.

Your choice is stored in your browser’s local storage so the banner is not shown again on later visits from the same browser, unless you clear that site data. There is no separate in-app cookie preference centre. You can also control or delete cookies through your browser settings, as described in section 4.

Strictly necessary cookies (including those used for sign-in and security) are used whether you choose “Accept all” or “Only necessary”. Functional support-chat cookies described in sections 2 and 3 may also be used on selected pages so you can contact IT Support.

6. Changes to This Cookie Policy

We may update this Cookie Policy from time to time. When we do, we will update the "Last updated" date at the top of this page.