Cookiepolicy
The short version: this website sets no cookies. Not analytics, not advertising, not a session cookie. One entry is written to your browser's own local storage if you dismiss the notice, and that is the whole of it. This page explains how we know.
What a cookie is, briefly
A small file a website asks your browser to keep, so that it can recognise the browser later. Cookies are how a site remembers you are logged in. They are also how advertising networks follow you between websites, which is the part people object to and the part this site does not do.
What this site sets
No cookies. On the home page, the start page and these legal pages, the number of cookies set is zero. No analytics cookie, no advertising pixel, and no embedded video, map or font service setting one on our behalf.
There is one thing stored in your browser, and it is not a cookie. When you dismiss the notice at the bottom of the screen, the site writes a single entry to your browser's local storage recording that you have seen it, so it does not reappear on every page. It holds the value "1". It contains no identifier, it is never sent to us or to anyone else, it never leaves your browser, and clearing your site data removes it. Until you dismiss the notice, even that is not written.
There is no Google Analytics on this site, no Meta pixel, no LinkedIn tag, no heatmap recorder and no consent-management platform. The fonts are served from our own domain rather than from a font service, which is one of the more common ways a site quietly contacts a third party without meaning to.
How we checked
By loading the site in a real browser and reading back everything it had stored: the browser's full cookie table, the cookies visible to scripts, local storage, session storage, and every outside host the page contacted while loading. Cookies, session storage and the list of outside hosts all came back empty. So did local storage, until the notice is dismissed, which writes the single entry described above.
This matters because it is easy to believe a site is clean and be wrong. A single embedded video or a hosted font is enough to make the claim false. So it is a measurement, and it gets re-run when the site changes.
The one exception
Our own operations dashboard, which lives behind a login on the same domain, sets one cookie when a member of the team signs in. It is the sign-in token. It is strictly necessary for a login you deliberately performed, it holds no tracking information, and it is set only after somebody types a password.
If you have not signed in to that — and you have not, because it is ours — nothing is set on your browser by this domain at all.
Why there is no accept-or-reject banner
Because there is nothing to consent to. The one local-storage entry is set only when you dismiss the notice, which is an action you took, and it records nothing about you. South African law does not have a standalone cookie rule; what applies is POPIA, which governs the processing of personal information whatever the mechanism. A cookie that stores no personal information and is set for a login you asked for does not require consent under it.
The notice on the site therefore has a single button. Offering you a choice between accepting and rejecting would be a choice about nothing, and a consent dialog that appears where no consent is needed is worse than useless: it teaches people to dismiss the ones that matter without reading them.
If you are in the EU or the UK
The ePrivacy rules there do require consent before non-essential cookies are stored, and they apply to visitors regardless of where the website is. We meet that requirement the only way that is not negotiable: by not storing anything. There is no non-essential cookie to ask you about.
Controlling cookies anyway
Every browser lets you block or delete cookies, usually under Privacy or Site settings. Doing that will not affect this site, since there is nothing here to block. It is worth doing for the rest of the web.
What the site does send elsewhere
No cookies is not the same as no data leaving. If you use the assistant, what you type is sent to Anthropic to generate a reply, and if you send an enquiry it reaches our inbox through Resend and is stored with our host. None of that uses a cookie, and all of it is set out in the privacy policy, which is the page to read if that is your actual question.
Anything else, write to ai@miax.co.za.
If MIAX ever adds analytics or any third-party script, this page changes first, the notice on the site gets a real refusal button beside its accept button, and neither ships before the other.
Who you are dealing with
Disclosed in terms of section 43 of the Electronic Communications and Transactions Act 25 of 2002.
- Full name: Michael Pienaar, trading as MIAX
- Legal status: Sole proprietorship. MIAX is a trading name of Michael Pienaar and is not a separate legal person.
- Registration number: None. MIAX is a sole proprietorship and is not a registered company.
- VAT: Not a registered VAT vendor. No VAT is charged and no tax invoices are issued.
- Physical and postal address: Oxford & Glenhove, 114 Oxford Road, cnr Glenhove Road, Houghton Estate, Johannesburg, 2198, South Africa
- Email: ai@miax.co.za
- Website: miax.co.za
- Information Officer (POPIA): Michael Pienaar, ai@miax.co.za
- Self-regulatory bodies: None. MIAX is not a member of any industry body or accredited scheme, and claims no accreditation it does not hold.
- Governing law: The law of the Republic of South Africa.