← Legal Workspaceinternal · Access-gated

legal/ — contracts, consents and privacy

Canonical source: biz/legal/README.md — edit the markdown, re-run npm run sync in workspace-site, rebuild, redeploy. Internal only — this one has no client-facing PDF.

These are plain-language drafts written by Claude for Daniel's review. They are not legal advice and no attorney has seen them. They exist so that the business stops operating on WhatsApp goodwill alone, and so there is something concrete for an attorney to mark up cheaply rather than draft from scratch. Each document says at the top whether it is safe to use as-is or genuinely wants a professional read first.
The statutory claims were verified 2026-08-10 against the Acts, the Information Regulator, SARS, the HPCSA rules and the Cape Town by-law — sources are in LEGAL-PLAN.md section by section, and its last table lists the five things the first draft got wrong. Three items still want a professional and are marked 🔴 there: one hour on the contract template (the s22(3) copyright assignment plus the liability clause — the highest-value legal spend available), a free written query to the Professional Board for Psychology before the first named case study, and a tax practitioner on incorporation if that ever comes up.
On 10 August 2026 service-agreement.md was reworked to v2.0, with every mechanism in it checked verbatim against the primary text of the Copyright Act, the CPA and ECTA rather than against a summary. That narrowed the attorney hour without removing it — statute-verified is not attorney-reviewed, so item 13 stays 🔴. What is left for that hour is now two specific questions, both written up in the agreement's own internal header: whether a signature on an emailed PDF satisfies s22(3), and the half-up-front deposit against the ECTA s44 right where a client declines an immediate start.

South African context: Daniel Slater trades as Leachie, a sole proprietorship in Cape Town, not VAT-registered. The law that actually touches this business is POPIA (client and site-visitor personal information), the Copyright Act (who owns the site), the Consumer Protection Act (his clients are mostly natural persons, so it applies), and ECTA (what a site that takes payment must display). LEGAL-PLAN.md explains all of it in one read.

File	What it is	Use it when
`LEGAL-PLAN.md`	The orientation document — the whole legal picture for Leachie, written to be read once and understood. Includes what is exposed today and in what order to fix it.	Read first
`care-plan-terms.md`	What the R450/month Care plan does and does not include, in referenceable form	Any client on a care plan
`service-agreement.md`	v2.0 — the build contract for client #2 onward: deposit, scope, timeline, change orders, IP transfer on final payment, POPIA operator terms, capped liability	Before starting a paid build
`ONBOARDING.md`	The running order for signing and onboarding a client, with the covering email. Internal — never sent	Every new engagement
`privacy-popia.md`	A privacy notice a client can publish, plus Leachie's own position as operator	Every client site that collects an enquiry
`case-study-consent.md`	Permission to publish a named case study with before/after metrics	Before any founding-discount deal, and before publishing anything

The rules that hold regardless of paperwork

A discount traded for rights needs the rights in writing, first. Policy, not preference. The register below is the record.
Client domains stay in the client's name. We take delegated access; we never resell.
Healthcare-practitioner clients are constrained by HPCSA advertising rules, which bite on testimonials and results claims. That constrains our own case-study copy about them, not just theirs. Check LEGAL-PLAN.md before writing marketing copy about a psychologist client.
Third-party assets need a licence on file. Fonts, stock imagery and video clips are the live exposure — see the open items in REGISTER.md.
Agents draft, Daniel signs and sends. No document leaves here automatically.