MLM Software Company in California

Two things differ here

Neither is a feature. Both are records.

California’s consumer privacy law gives people rights that only work if the underlying data was captured and is retrievable, and worker classification makes some entirely ordinary software features into evidence you would rather not have created.

We have no California office and no local staff. The federal position — retail classification, income disclosure, income claim controls, contractor reporting, economic nexus sales tax — is on the US page.

Privacy: the same infrastructure, different labels

The requirements California imposes and the ones POPIA imposes in South Africa are close enough that building for one substantially covers the other. Four capabilities:

Access, answered completely. In a direct selling platform, one person’s data sits in more places than in an ordinary business: the distributor or customer record, orders they placed, orders attributed to them as a seller, their position in the placement tree and in the sponsorship tree, every commission line, uploaded identity and banking documents, consent records, support tickets and marketing communications. Assembled by hand, each request costs a day and probably misses something. As one query, minutes.

Deletion that does not break the ledger. Names, contact details, documents and banking details removed or hashed. Commission lines, tree positions and closed-period statements retained as anonymised entries, because a paid commission is a financial record with its own retention duty and removing it would invalidate every statement above and below that position.

Opt-out, honoured everywhere. Platform messaging, the replicated sites you host, and outbound email and SMS through their integrations. A preference respected in one channel and ignored in another is worse than not offering it, because the record now shows you knew.

Consent with the wording shown. Per channel, with timestamp, source and the exact text as displayed. The obligation is to demonstrate a preference, not to assert one.

The Pretoria page covers request handling and retention mechanics in more depth, since the POPIA framing is where we wrote them up first.

The distributor is a data subject too

Assume the rights apply to distributors as well as retail customers, and confirm the specifics with counsel.

The practical reason is not legal caution. A platform that can produce a customer’s data but not a distributor’s cannot answer most of the requests it will actually receive, and distributors are by far the likelier requesters — a departing leader, a commission dispute, or a competitor recruiting your field each produce several at once. One mechanism handling both is also cheaper to build than two.

Retention, because accumulation is the exposure

Nothing breaks when you skip retention, which is why it gets skipped. The system works and quietly accumulates identity documents, bank details and communications indefinitely.

The data you no longer need is the data most likely to cause harm if it leaves. So retention is configured per category with an action at expiry that runs on a schedule: delete, anonymise or archive. The periods are a legal question and yours to set; the mechanism should exist from launch.

Classification: what the software should not do

Whether your participants are correctly treated as independent contractors is a question for California counsel, and it turns on how the relationship actually operates rather than on what the agreement says. California’s framework includes a carve-out for direct sales salespersons meeting stated conditions, and whether your programme meets them is not something a software vendor should be telling you.

What is squarely our responsibility is narrower: software features that look like control become evidence of control. So the distributor tools deliberately do not include:

• scheduling or shift assignment,
• time tracking or clock-in,
• mandatory activity quotas enforced as a gate,
• supervisory approval flows over a distributor’s own selling activity.

Every one of those is an ordinary, useful feature in a workforce application. Here each one is a fact somebody can point at.

What the platform does record instead:

The back office page covers where agreement versioning sits in the corporate console, and the replicated website page covers the distributor-facing tools where these distinctions show up in practice.

Why this weighs more than a feature list

Every capability on a feature list can be bought in year two for roughly what it would have cost in year one. A record you did not capture cannot be bought at all — you cannot retrospectively produce the text somebody accepted in March, or reconstruct which channel a person consented to.

That asymmetry is the argument the compliance comparison makes at length, and it applies with particular force in a state that gives people enforceable rights over the answer.

Working with us from California

Calls in Pacific Time. This is the poorest overlap with our South African working hours of any US zone, and we schedule around it with fixed windows rather than pretending it is not there.

Ask us to demonstrate this page rather than describe it: an access request assembled live for a test distributor, a deletion that leaves the ledger reconcilable, and a consent record showing the wording that was displayed.