Privacy, POPIA and security

POPIA and security for a scheme's records

A scheme's register, votes and complaints are personal information about its owners and residents. Estate Manager protects them with two-factor sign-in, keeps each estate's data apart from every other's, and gives every person a privacy centre built for the Protection of Personal Information Act (POPIA). The body corporate stays in charge of its records.

POPIA s19 Security safeguardsPOPIA s21 A written agreement with the operatorPOPIA s22 Notice of a security compromisePOPIA s14 Kept no longer than needed
The audit log of a fictional scheme narrowed to the managing agent's reads of personal information: quote requests with the trustees' declarations of interest, the contractors' details and a request with its reporter, each with its time.
Who read personal information, and when.

Who is responsible for what

The body corporate decides, and Nanotech processes for it

POPIA gives each party its own duties.

The body corporate

It decides why and how its owners' and residents' information is used, so it is the responsible party for its records. Its managers decide who sees what, and its Information Officer answers requests about them.

POPIA s1

Nanotech Computers

Nanotech processes each estate's records as its operator, and section 21 requires a written agreement between them that binds Nanotech to the security measures of section 19 and to tell the estate immediately of any compromise. It uses them only with the scheme's authority and keeps them confidential. Nanotech's own administrators of Estate Manager can see and administer every estate, to run and support the service.

POPIA s20 and s21

Every person who signs in

Each person accepts the privacy notice before reaching an estate, downloads what is kept about them and corrects their own details.

POPIA s18 and s23

Signing in

Two-factor sign-in for everyone who manages an estate

The chair, the trustees and the managing agent add an authenticator app at their next sign-in, before they can continue, because they see and change other people's information. A stolen password alone does not reach the estate's records. Any owner may turn two-factor sign-in on too, and one-time recovery codes cover a lost phone.

Estate Manager runs its own sign-in server rather than a third party's. An account signs in only once its email address is confirmed, repeated attempts are slowed down, and three wrong passwords lock the account for 5 minutes.

The two-factor sign-in page asking for the code from the authenticator app, with an option to remember the device and a link to sign in with a recovery code.
After the password, the code from the authenticator app.

Isolation and hosting

Each estate's data kept apart, and hosted in the EU

Every estate's records are isolated from every other estate's by row-level security in the database, behind the application's own checks. The application connects as a database role that the policies bind, so a query that lost its filter still sees only its own estate. Automated tests check that a request for one estate cannot read or change another's records.

Estate Manager is hosted on Amazon Web Services in a European Union region from launch. For a South African scheme, that is a transfer of personal information outside the Republic, which section 72 of POPIA allows where the recipient is subject to a law that gives an adequate level of protection. The privacy notice discloses the transfer and its basis.

  • A managing agent switches estates without signing in again
  • Emails go through a provider that the privacy notice names
POPIA s72 Transfers outside the Republic
A managing agent's estate switcher open over the dashboard, listing two fictional schemes to choose between.
One sign-in for an agent's schemes, each kept apart.

The privacy centre

A privacy centre for every person

Every user accepts the privacy notice when they register, and again at their next sign-in when a new version takes effect. Each person downloads what Estate Manager keeps about them in their account and their estates' records as machine-readable files, asking the estate for what the download leaves out, such as complaints others filed about their unit, sees when lists holding their details were read and by which role, and corrects their own details.

When an owner sells and leaves, the managers close their account. Where the scheme must keep its records of meetings and votes, the person's account is anonymised rather than deleted, so the votes still count and the account no longer carries the name, though records the scheme keeps in its own right, such as the owner register and the attendance registers of its meetings, may still name them. The managers can also download a template of the estate's own privacy notice to residents, to complete with a legal adviser.

POPIA s18 The noticePOPIA s23 and s24 Access and correction
The privacy centre in the dark theme: the privacy notice in effect and when the person accepted it, the versions they accepted, the estate's Information Officer and the download of their own information.
The notice accepted, and a download of one's own information.

The audit trail

An append-only audit trail the trustees can read

Every change in an estate is written to an audit trail, and so is each read of the register, the members, the invitations, the complaints and the requests, among other records that hold people's details. The database itself refuses any change to it or deletion from it, outside the retention schedule. Entries name records by their ids rather than by people's details, and the trustees read the trail to oversee the managing agent on the owners' behalf.

The audit log in the dark theme, listing what an administrator did and read in the estate, each entry with its time, the person's role, the action and its details.
Who did what in the estate, and when.

Nothing kept longer than needed

Many kinds of record have a retention period, and a daily job deletes what has reached the end of it, or removes from it the details that identify a person, as section 14 of POPIA asks. Others, such as the register, the meetings and the library, stay until the managers delete them. Some of the periods:

RecordKept for
The audit trail5 years from each entry
Complaints resolved or dismissed5 years from the outcome
Requests completed or declined5 years from the outcome
Quote requests closed, declined or withdrawn6 years from closing
Budgets superseded, withdrawn or not approved6 years
Emails in the outbox90 days
Documents a manager deleted90 days, then gone with every version
Proof of delivery of a meeting's noticeAs long as the scheme keeps the meeting's records

The full schedule is on the application's legal page, open to anyone.

If something goes wrong

What happens after a security compromise

When there are reasonable grounds to believe that someone without authority has accessed or acquired personal information, these are the steps.

  1. 01

    Contain

    We stop the access, secure the evidence and find out what happened.

  2. 02

    Tell the estate

    We tell each estate whose records are affected immediately, as section 21(2) requires.

    POPIA s21(2)
  3. 03

    Help it notify

    The body corporate, as the responsible party, notifies the Information Regulator and the people affected as soon as reasonably possible. We give it the facts it needs.

    POPIA s22
  4. 04

    Our own records

    For information Nanotech is itself responsible for, such as sign-in accounts, we notify the Regulator and the people affected ourselves.

    POPIA s22
  5. 05

    Fix and review

    We restore the service, fix the cause and update our safeguards.

    POPIA s19(2)

What the law says

POPIA and sectional title schemes: the points that matter

The Protection of Personal Information Act 4 of 2013 sets eight conditions for lawful processing (section 4), and section 16 of the practice directive of the Community Schemes Ombud Service (CSOS) applies them to community schemes.

General information, not legal advice.

POPIA s1, CSOS directive 16.5

Responsible party and operator

The body corporate determines why and how its members' information is processed, so it is the responsible party. A provider that processes the information for it under a contract is an operator, and the scheme must have an operator's agreement with it.

POPIA s19

Security safeguards

The responsible party takes appropriate, reasonable technical and organisational measures against loss, damage and unlawful access. It identifies the risks, maintains safeguards against them, checks that they work and updates them.

POPIA s20 and s21

The operator's duties

An operator processes the information only with the responsible party's knowledge or authorisation and keeps it confidential. A written contract requires it to maintain the section 19 measures, and it tells the responsible party immediately of any unauthorised access.

POPIA s22

Security compromises

The responsible party notifies the Information Regulator and the people affected as soon as reasonably possible, in writing, with enough detail for them to protect themselves. The Regulator asks for reports through its eServices portal.

POPIA s14

Retention

Records are kept no longer than their purpose needs, unless a law requires or authorises it, the responsible party reasonably needs them, a contract requires it or the person consents. Then they are destroyed, deleted or de-identified.

POPIA s18, s23 and s24

Openness and access

People are told what is collected, why, by whom and where it goes, including any transfer abroad. They may ask what is held about them and who has had access to it, and ask for corrections or deletion.

POPIA s55(2), CSOS directive 16.11

The Information Officer

Each scheme designates an Information Officer, who may take up the duties only once registered with the Information Regulator.

Questions

Questions about POPIA and security

Anything else: ask us when you book a demo, or write to info@nanotech-computers.com.

What is POPIA, and what does it stand for?
POPIA is South Africa's data protection law, the Protection of Personal Information Act 4 of 2013. It governs how responsible parties, bodies corporate among them, process personal information. Its main provisions took effect on 1 July 2020, with a year's grace that ended on 30 June 2021, and the Information Regulator enforces it.
Does POPIA apply to a body corporate?
Yes. A body corporate keeps personal information about its owners, tenants and trustees, such as the names, identity numbers, addresses and contact details that prescribed management rule 27(2)(b) asks it to list, and it decides how that information is used. That makes it the responsible party for its records. Estate Manager keeps owners' identity or passport numbers encrypted, and only the trustees, the managing agent and the owner can see them, each time recorded.
Who is a body corporate's Information Officer?
Under POPIA it is the head of the body corporate, or a person whom the head duly authorises. The CSOS practice directive has each scheme designate one, such as a trustee, a building or estate manager or a member of the managing agent (paragraphs 16.11 and 16.12), though paragraph 16.19 lets a managing agent be only a deputy. The officer must be registered with the Information Regulator before taking up the duties (section 55(2)). General information, not legal advice.
Is Estate Manager POPIA compliant?
Compliance depends on how each body corporate collects and uses personal information, so no software can be compliant on a scheme's behalf. Estate Manager is built for POPIA: the privacy notice at sign-in, a download of each person's own information, anonymisation where records must be kept, retention periods applied every day and an audit trail of who read personal information.
Can we take our records with us?
Yes. The register exports to CSV, budgets to Excel, the rules and minutes drafts to Word, and every document in the library downloads as the file it is. Each person can also download their own information, up to three times a day.
Does Estate Manager send marketing to owners?
No. It sends only the emails the service needs: invitations, sign-in emails, meeting notice packs, notices, and updates on complaints, requests and quotes. Each email says why the recipient receives it.

See how a scheme's records are protected

A demo shows the privacy centre, the audit trail and two-factor sign-in on a fictional scheme, with time for your questions about how records are kept.