pleks
Why PleksThe workCharterWho built thisPricingFounding agentsContact
PLEKS · LEGAL REGISTRY · BOOK 04FOL. 0117 · POPIA · CPA · NCAFORM · POPIA-S22CONSENTCLAUSE LEDGER · S04§ 04.01 acceptance§ 04.02 service description§ 04.03 subscription & payment§ 04.04 cancellation · 90 days§ 04.05 prohibited uses§ 04.06 limitation of liability§ 04.07 governing law · ZA · WCREPUBLIC OF SOUTH AFRICAPOPIAACT 4 OF 2013¶ 01¶ 02¶ 03¶ 04
COOKIES · TRACKINGbrowser storagev1.4.1

Cookie policy

How Pleks uses cookies and similar browser storage technologies to keep you signed in, measure performance, and improve the platform.

Last reviewed2026 · 08 · 14
In force from2026 · 05 · 05
JurisdictionRepublic of South Africa
FrameworkPOPIA s11 · s69
On this page
  • —Summary
  • 01What are cookies
  • 02Essential cookies
  • 03Analytics cookies
  • 04Third-party cookies
  • 05Managing cookies
  • 06Changes
Legal docs
  • §Definitionsv1.2.3
  • §Cookie policyv1.4.1
  • §Credit check policyv1.6.0
  • §PAIA manualv1.3.0
  • §POPIA registerv2.6.0
  • §Privacy policyv4.9.0
  • §Terms of servicev3.7.0
Pleks (Pty) Ltd · ZA

Plain-language summary

What you need to know about cookies on Pleks

  • Pleks uses essential cookies to keep you signed in and to protect your session. These cannot be disabled without breaking the platform.
  • We use Vercel Analytics for performance measurement. IP addresses and user agents are converted to a daily-rotating one-way hash by Vercel; raw values are not retained. We treat this as processed in a privacy-preserving aggregated form.
  • We do not use advertising cookies, tracking pixels, or any cross-site behavioural profiling. Vercel Analytics measures aggregate site performance and does not profile individual visitors.
  • You can clear or block cookies in your browser settings at any time. Essential cookies will be re-set on next sign-in.
  • The public marketing site (pleks.co.za) uses fewer cookies than the authenticated dashboard — see section 02 for the full list.
  • Pleks does not show a cookie consent banner because we do not set any cookies that require POPIA s11(1)(a) consent. If that ever changes, a banner will appear and this policy will be updated.

01 · Background

What are cookies

Cookies are small text files that a website places on your device when you visit. They allow the site to remember information between page loads — such as whether you are signed in, your language preference, or how you arrived at the site.

In addition to cookies, Pleks may use local storage and session storage — browser-based key-value stores that behave similarly to cookies but are not sent to the server with every request. The same rules apply to these technologies as to cookies under this policy.

Under POPIA, we are required to inform you about cookies that process personal information and to rely on a valid lawful basis — consent (POPIA · S11(1)(a)), contract (POPIA · S11(1)(b)), or legitimate interest (POPIA · S11(1)(f)) — before processing. SA law does not have a direct equivalent of the EU ePrivacy Directive’s cookie rule; our requirements are set by POPIA s11 (lawful basis) and, for direct-marketing cookies, POPIA s69.

This policy should be read together with our Privacy Policy and Terms of Service, which describe how we handle personal information more broadly.

Pleks operates under South African law. If you access Pleks from outside South Africa, additional local cookie or e-privacy laws may apply; this policy describes our compliance with SA law and is not a determination of compliance with any other jurisdiction’s regime.

02 · Essential cookies

Essential cookies

These cookies are strictly necessary for Pleks to function. They cannot be disabled without preventing you from signing in or using the platform. No consent is required for these cookies under POPIA · S11(1)(b) — they are necessary for the performance of the contract (the Pleks Terms of Service) you have entered into with us.

Storage itemPurposeDuration
sb-[projectId]-auth-tokenSupabase · cookieStores your authenticated session after sign-in. Required to access the dashboard. Sent to the server with every request so your session can be verified. Where the token exceeds the browser’s 4 KB cookie limit it is split across numbered companions (…auth-token.0, …auth-token.1). [projectId] is the unique identifier of the Pleks Supabase project.Up to 12 hours; renewed while you are signed in and active; cleared on sign-out
sb-[projectId]-auth-token-code-verifierSupabase · cookiePKCE code verifier used during the sign-in exchange. Cleared immediately after sign-in completes.Until sign-in completes
pub-themePleks · localStorageStores your light/dark mode preference on the marketing site.1 year
pleks_orgPleks · cookieCaches your current organisation, role and tier so each page load does not re-query the database. Treated as a hint only — organisation and role are always re-verified against the database before any data is returned.5 minutes
pleks_has_orgPleks · cookieRecords that your account has completed onboarding and belongs to an organisation, so the routing layer can admit you to the workspace without a database call.7 days
pleks_tos_versionPleks · cookieRecords which version of the Terms of Service you accepted, so you are only asked again when the Terms actually change.1 year
pleks_privacy_versionPleks · cookieRecords which version of the Privacy Policy you acknowledged, so you are only asked again when this policy actually changes.1 year
pleks_aalPleks · cookieRecords that you completed a passkey sign-in, so the routing layer can treat the session as multi-factor verified. Signed and bound to your specific session; it cannot be copied to another session or device.12 hours
pleks_rdrPleks · cookieCounts consecutive redirects so a misconfigured sign-in cannot trap your browser in a loop. Cleared as soon as you land on a page.15 seconds
pleks_tracePleks · cookieCarries a short random reference for one request so a support query can be matched to the correct server log. Contains no personal information.30 seconds

A note on storage type: Your Pleks session is held in cookies, not in browser localStorage. Because the server must verify your session on every request, the session cookie is transmitted with each request. It is not marked HttpOnly: the sign-in library running in your browser reads and refreshes the session itself, so a script running in the page could read it. It is marked Secure (sent only over HTTPS) and SameSite=Lax, lasts at most 12 hours unless your session is refreshed, and our content security policy limits where scripts may be loaded from. Cookies are cleared when you sign out or clear your browser data. The same POPIA obligations apply regardless of whether data is stored in a cookie or in browser storage.

Session validation and the underlying user record are stored at our database and storage provider’s Ireland (EU) infrastructure (see the operators directory in the POPIA processing register). Transfers outside South Africa are governed by Standard Contractual Clauses per POPIA · S72(1)(a).

03 · Analytics cookies

Analytics cookies

Pleks uses Vercel Analytics to measure page performance and visitor counts on the marketing site. Vercel Analytics does not set cookies. IP addresses and user agents are converted to a daily-rotating one-way hash by Vercel; raw values are not retained and no individual user profiles are built.

Pleks treats Vercel Analytics data as processed in a privacy-preserving aggregated form and does not consider it to require POPIA s11(1)(a) consent. If you disagree, you can block analytics via your browser’s developer tools or a content blocker — the platform continues to function normally.

We do not use Google Analytics, Meta Pixel, or any other third-party analytics that sets cookies or tracks individuals across sites.

04 · Third-party cookies

Third-party cookies

Some features of Pleks involve third-party services that may set their own cookies. Where this occurs, the third party’s own cookie and privacy policy applies. Pleks does not control these cookies.

ServiceWhen cookies are setTheir policy
PayFastpayment processorCookies are set by PayFast upon redirection to their secure payment gateway — this occurs when completing a subscription payment or setting up a recurring debit mandate. These typically include session and fraud-prevention cookies on the PayFast domain. Pleks does not control or access them; the PayFast cookie policy is the authoritative description.payfast.io/privacy-policy

The e-signature workflow (DocuSeal) is self-hosted on Pleks’s own infrastructure — no data is transferred to a third-party DocuSeal service, and any storage items set during document signing are first-party Pleks items governed by this policy. This is consistent with the Operator Agreement classification in the POPIA processing register.

Pleks does not embed social media plugins, advertising networks, or any third-party scripts that would track you across websites for marketing purposes.

05 · Managing cookies

Managing cookies

You can control and delete cookies through your browser settings. Most browsers allow you to:

  • View all cookies currently stored by your browser.
  • Delete all cookies, or cookies from a specific site.
  • Block all cookies, or block cookies from specific sites.
  • Set the browser to warn you before a cookie is placed.

Be aware: blocking or deleting the essential cookies listed in section 02 will sign you out of Pleks and prevent the platform from working correctly. You will need to sign in again after clearing session cookies.

Browser-specific guides: Chrome Firefox Safari Edge

06 · Changes

Changes to this policy

We may update this cookie policy from time to time as the platform evolves or as legal requirements change. Material changes include adding a new cookie or storage item, changing a cookie’s purpose, adding a third-party recipient, or changing the lawful basis. Non-material changes (typographical corrections, link updates) take effect on publication. When we make material changes, we will update the “Last reviewed” date at the top of this page and, where appropriate, notify you by email.

If an inconsistency exists between this Cookie Policy and the Pleks Terms of Service, the Terms of Service prevail unless mandatory law requires otherwise.

For any questions about how Pleks uses cookies, contact our Information Officer.

Information
officer
Stéan Bouwer
legal@pleks.co.za
PEND · COOKIE POLICY · v1.4.1Effective 5 May 2026
pleks

Built from the inside out.
Every feature earned in the field.

Checking status…
  • Why Pleks
  • The work
  • Charter
  • Pricing
  • Founding agents
  • Contact
  • Cookie Policy
  • Credit Check Policy
  • Definitions
  • PAIA Manual
  • POPIA Register
  • Privacy Policy
  • Terms of Service
  • hello@pleks.co.za
  • support@pleks.co.za
  • legal@pleks.co.za

© 2026 Pleks (Pty) Ltd. Built in South Africa.

Built by Yoros