Qoncegate
Message us on WhatsApp

Your complex's WhatsApp group already has the record. Nobody can find it.

Send us your complex's WhatsApp export and get back exactly what a CSOS dispute, an AGM report, or a new managing agent's handover actually needs — every security, maintenance, and parking complaint, sorted and timestamped, instead of buried in a group chat scroll.

Unit 14 · 06:52 the boom's been stuck open since Friday, security walked past it twice and did nothing, this is the third time this month
↓
Security Flagged — recurring Boom gate malfunction, unresolved 3+ days

What you actually get back

Why the record matters, legally

Trustees carry a legal duty under the Sectional Titles Schemes Management Act to keep proper governance records. When something becomes a dispute, CSOS decides it — and CSOS has patience for a documented case, not for "everyone in the group remembers it." That documentation already exists; it's just sitting in a chat, out of order, mixed in with birthday wishes.

How it works

  1. Get the export from WhatsApp

    Android: open the chat, tap the three-dot menu top right, then More, then Export Chat, and choose "Without Media."

    iPhone: open the chat, tap the group name at the top, scroll down, tap Export Chat, and choose "Without Media."

    Just forward whatever WhatsApp hands you — a .txt or the .zip an iPhone produces. No need to unzip anything; we'll open it on our side.

  2. Forward it to us on WhatsApp

    No account, no login — the same app the group already runs on.

  3. Get your log back

    Categorised, timestamped, and anonymised — ready to hand over.

POPIA already applies to your complex — here's what that actually means

The Protection of Personal Information Act isn't only something large companies need a compliance department for. A body corporate or HOA counts as a "responsible party" too, the moment it handles residents' names, unit numbers, or contact details for anything beyond personal use — and forwarding a chat full of that around with no plan for who sees it or how long it's kept is exactly what the Act was written to prevent.

The Information Regulator can fine a responsible party up to R10 million, and for the most serious offences — such as ignoring a formal notice to fix a problem — the law allows criminal penalties too, including imprisonment, that can reach an individual trustee personally, not only "the scheme." Worth knowing honestly: every fine issued so far followed an organisation that was warned and didn't act, not a one-off honest mistake. That's the actual point — getting the basics right from the start is what keeps a complex out of that position, not luck.

This is what Qoncegate is built around, not something added afterwards: names and numbers become "Resident 1, 2, 3…" before a log ever leaves the tool, nothing is kept longer than it takes to generate that log, and anything that is kept — enquiries sent through this site — is encrypted, not just hidden behind a login.

This isn't a substitute for your scheme's own POPIA compliance sign-off — treat it as the record-keeping half of taking the Act seriously, not the legal half.

If you're a trustee

You didn't sign up to be a records clerk, and you're personally exposed if the scheme's governance turns out to be undocumented when it matters. This is a paper trail without becoming the person who reads the group chat every night.

If you're a managing agent

You're carrying this exposure for every scheme on your book. It's a cleaner answer than "we'll check the group chat" the next time a trustee or CSOS asks for evidence.

Why this is hands-on for now

Right now, a person runs your export, not a form. That's deliberate: the first few complexes get an actual person's attention while we learn what real chats throw at it, rather than a self-serve tool testing itself on your data. Once that's proven, this becomes a direct WhatsApp line, no forwarding required.