Digitise SA
What cookies Digitise SA uses and why. No paid advertising, and declining the optional ones costs you nothing.
Applies to
digitisesa.co.za
Operated by
Hodisa SA NPC, a registered South African non-profit company
Effective
1 May 2025
Last updated
19 September 2026
Cookies are small files a website stores on your device. We use a small number of them, and we use them for two reasons only: to make the site work, and to understand which parts of it people find useful.
We sell no advertising and we run no ads. Nothing on this site is paid placement, and we do not build a profile of you to sell to anyone.
One honest exception. Pages that embed a YouTube video set cookies that Google classifies as advertising cookies. We do not place ads and we receive nothing from them, but they are set on your device all the same, by Google rather than by us. Section 6 explains which pages and what we are doing about it.
Declining the optional ones costs you nothing. Every template, course, guide and download on this platform works exactly the same whether you accept them or not.
This policy covers digitisesa.co.za, operated by Hodisa SA NPC, a registered South African non-profit company. It sits alongside our Privacy Statement, which explains what we do with personal information generally.
A cookie is a small text file that a website asks your browser to store. When you come back, the site can read it again.
Some cookies last only while your browser is open and disappear when you close it. Those are session cookies. Others stay on your device for a set period so the site remembers you next time. Those are persistent cookies.
Some are set by us. Others are set by a service we use, for example a video player embedded in a page. Those are third-party cookies.
Strictly necessary. These make the site function. They keep you logged in, remember what you have put in a form so you do not lose it, protect against certain attacks, and remember your cookie choices so we stop asking. Without these the site does not work properly, so they are always on and cannot be switched off.
Functional. These remember a preference you have set, such as whether you are using light or dark mode. They are a convenience and nothing more.
Analytics. These tell us which pages get read, which templates get downloaded and where people give up. We use that to decide what to build next. The information is about how the site is used, not about who you are, and we look at it in aggregate rather than person by person.
Advertising. We place none of our own. Four cookies in this category appear on our site, and every one of them is set by the YouTube player on pages that embed a video. Google uses them for its own purposes. We do not read them, we do not benefit from them, and we do not allow anyone to use our site to target advertising at you.
From the CookieYes scan of 19 September 2026: 93 pages scanned, 15 cookies found across four categories. Descriptions below are ours, written in plain language.
| Cookie | Set by | What it does | Lasts |
|---|---|---|---|
| Strictly necessary · always on | |||
cookieyes-* | CookieYes | Stores the cookie choice you made, so we honour it and stop asking | 1 year |
elementor | Digitise SA | Lets our page builder render pages correctly | Does not expire |
wordpress_test_cookie | Digitise SA | Checks your browser accepts cookies, used when logging in | Session |
wpEmojiSettingsSupports | Digitise SA | Checks whether your browser can display emoji characters | Session |
| Analytics · optional | |||
_ga | Google Analytics | Tells one visitor apart from another, without knowing who you are | 1 year 1 month |
_ga_* | Google Analytics | Counts page views | 1 year 1 month |
_gid | Google Analytics | Records how the site is used over a single day | 1 day |
_gat_gtag_UA_* | Google Analytics | Limits how often data is sent | 1 minute |
| Functional · optional | |||
YSC | YouTube | Counts views of a video embedded in one of our pages | Session |
VISITOR_INFO1_LIVE | YouTube | Estimates your connection speed to choose a video player version | 6 months |
ytidb::LAST_RESULT_ENTRY_KEY | YouTube | Remembers the last video result you clicked | Does not expire |
| Advertising · optional, and none of it is ours | |||
VISITOR_PRIVACY_METADATA | YouTube | Stores your cookie consent state for YouTube itself | 6 months |
__Secure-YNID | YouTube | Security and fraud prevention, mainly around signing in to Google | 6 months |
__Secure-ROLLOUT_TOKEN | YouTube | Decides which version of the video player features you are shown | 6 months |
__Secure-YEC | YouTube | Purpose not documented by Google | Short lived |
Every cookie in the last two groups comes from the embedded YouTube player, not from us. They appear on the Video Hub and on two articles. See section 6.
Some pages include content from other services, and those services may set their own cookies when the content loads.
Embedded video. Our Video Hub and two of our articles embed videos hosted on YouTube. When one of those pages loads, YouTube sets cookies on your device, including the four in the advertising category above. This happens whether or not you press play.
This is the single largest source of cookies on our site, and it comes from a service we use rather than from anything we are doing. These embeds currently use the standard YouTube player. You can manage optional cookies through our cookie banner. Blocking optional cookies may prevent embedded videos from loading until you allow them.
Consent management. Our cookie banner is provided by CookieYes, which stores a record of the choice you made so we can honour it and prove it was given.
Analytics. Where analytics are active, the provider is named in the table above along with what it stores and for how long.
We do not allow these services to use what they collect on our site to target advertising at you.
You can change your cookie choices at any time using the cookie preferences link in the footer of every page. Your new choice takes effect immediately.
You can also control cookies in your browser. Every major browser lets you see what is stored, delete it, and block cookies entirely. The help pages for Chrome, Safari, Firefox and Edge all explain how.
Be aware that blocking all cookies in your browser will break the login on most websites, including ours. Using the footer link is the better route if you only want to opt out of the optional ones here.
Some browsers can send a Do Not Track signal. There is no agreed standard for how websites should respond to it, so we do not rely on it. Use the cookie preferences link instead, which we do honour.
The Protection of Personal Information Act (POPIA) governs how we handle personal information, including information collected through cookies where it relates to an identifiable person. It does not contain a cookie-specific rule the way European law does.
We have chosen to ask for your consent before setting anything that is not strictly necessary, and to block those cookies until you agree. That is stricter than we are required to be, and we think it is the right way round.
You have rights over your personal information under POPIA, including the right to ask what we hold and to have it deleted. Our Privacy Statement explains how to use them, and every account holder can do both from their profile page.
We update this policy when the cookies we use change. The date at the top shows when it last changed. If we ever add a category of cookie, we will ask for your consent again rather than assuming the old answer still applies.
If anything here is unclear, or you want to know exactly what is stored on your device, email info@digitisesa.co.za. You can also complain to the Information Regulator of South Africa.