Skip to main content
Draft for legal review

Privacy and POPIA notice

How we handle your information, written so that you can actually read it.

Draft, not yet adopted

This notice is a working draft prepared for the MyEngineer platform. It must be reviewed and adopted by a South African attorney before the site goes live.

1. Who we are

REAN Consulting (Pty) Ltd, trading as MyEngineer, operates www.myengineer.co.za, a platform that connects members of the public and businesses with verified engineering professionals, built-environment professionals, artisans and contractors in South Africa. We are the responsible party for the personal information described in this notice.

Responsible party
REAN Consulting (Pty) Ltd, trading as MyEngineer
Registration number
2018/408540/07
Information Officer
Phendukani Ntini, registration number 2026-067663
VAT number
4330319221
Address
Unit 2, 74 Old Main Road, Kloof, Durban, 3610

Our Information Officer is registered with the Information Regulator. Send privacy requests, including a request to see, correct or delete your information, to the email address above: they reach the Information Officer and are answered by a person. How to request records is set out in our PAIA manual.

2. The law we work under

We process personal information in accordance with the Protection of Personal Information Act, 4 of 2013 (POPIA), and the eight conditions for lawful processing set out in it. Where the Electronic Communications and Transactions Act or the Consumer Protection Act apply, we comply with those too.

3. What we collect, and why

3.1 If you are a client or member of the public

What we collect from clients and members of the public, why we need it, and the lawful basis
InformationWhy we need itLawful basis
Name, email address, mobile numberTo answer your enquiry and co-ordinate an appointmentPerformance of a contract, or your consent
Suburb, municipality, province, site addressTo match you to a professional who works in your areaPerformance of a contract
Description of your problem, photographs, plans, municipal correspondenceTo scope the work correctlyPerformance of a contract
Enquiry and job historyTo manage your appointment and support youPerformance of a contract, or legitimate interest
Payment and milestone recordsTo administer payments and comply with financial and tax lawLegal obligation

3.2 If you are a professional or contractor

What we collect from professionals and contractors, why we need it, and the lawful basis
InformationWhy we need itLawful basis
Name, identity or passport number, contact detailsIdentity verification and fraud preventionYour consent, or legal obligation
Qualifications, transcripts and trade certificatesTo verify competence before you are listedYour consent
CV, work history and reference lettersTo verify your experience in the disciplines you chooseYour consent
Professional or trade registration number and statusTo confirm with the issuing council that your registration is current and in good standingYour consent
Insurance, COIDA and tax documentsTo confirm that you can lawfully be appointedYour consent, or legal obligation
Banking detailsTo pay youPerformance of a contract
Work history and client ratings on the platformTo match you accurately and maintain qualityPerformance of a contract, or legitimate interest

3.3 If you have an account, or simply use the site

The platform itself keeps the records below. They exist because this is an application with accounts, stored enquiries and a verification queue, not a brochure site.

What the platform records for every account and visit, why it is needed, and the lawful basis
InformationWhy we need itLawful basis
Account record: name, email address, mobile number, account type, organisation and organisation typeTo let you sign in, see your own enquiries and manage your detailsPerformance of a contract
Your passwordHeld only as a one-way hash. We never hold the password itself and cannot read itPerformance of a contract
Consent records: the version of this notice and of the terms you accepted, and whenTo show which text you agreed toLegal obligation
Files you attach to an enquiry or an applicationTo scope the work, and to verify competencePerformance of a contract, or your consent
Access log entries: who opened a private document, when, and for what purposeTo keep the promise that every access to a credential document is recordedLegitimate interest, and legal obligation
A one-way hash of your network address and browser user agentTo rate limit the forms against automated abuse. The address itself is not stored and never appears in a logLegitimate interest
Your email address, if you subscribe to Knowledge Centre updatesTo send you the updates you asked for, until you unsubscribeYour consent

We do not build advertising profiles, and we do not track you across other websites.

4. How professional credentials are protected

This is the commitment the platform is built around, not merely a policy statement.

  • Documents are never published. Uploaded documents go to private, encrypted storage with no public address. They are not served from the website and cannot be reached by a search engine.
  • Access is restricted and logged. Only you and a named verification officer may open one of your documents. Every download goes through a permission check, is handed out as a link that stops working after 60 seconds, and writes a log entry recording who opened it and why.
  • Identity and registration numbers are encrypted at rest. Your identity or passport number and your council registration number are encrypted with AES-256-GCM the moment you save that step, so the plain number is never written to the database. Your own view of your application shows the last four characters only, for example ********1080. They are decrypted in two places only: the strict check when you submit your application, and a verification officer’s view, which writes an access log entry.
  • The desk never receives your registration number by email. The registration enquiry that reaches the co-ordination desk reads [supplied, held privately] where the number would be.
  • The public directory is a separate dataset. Your public card is built field by field from your status, category, disciplines, years of experience, location and platform statistics. It contains no name, no identity number, no registration number, no employer, no document reference and no contact detail: those fields are not present in it at all, as keys or as values. Automated tests check this on every change.
  • Identity is released on appointment only. A client learns who you are once you accept a job and both parties are on the platform agreement.
  • Verification results are stated, not evidenced publicly. Clients see that a registration was confirmed current, never the underlying certificate.

What the public can see about a professional is limited to: an anonymous platform reference, registration category, discipline and competence, province and municipality, an experience band, availability, work mode, completed job count and rating. There is a worked example on how verification works.

5. Who we share information with

  • The professional you appoint, and only the information needed to do the work.
  • The client who appoints you, and only once you have accepted the job.
  • Issuing bodies and councils, to confirm that a qualification or registration is genuine and current.
  • Service providers that host, secure, communicate or process payments for us, under written contracts that restrict them to our instructions. The providers that hold personal information for us today are Supabase (the database, private file storage and sign-in), Resend (the transactional email that carries your receipt and the desk notification) and the provider that hosts and delivers the website itself.
  • Regulators, councils and law enforcement, where the law requires it, or where professional misconduct must be reported.

We do not sell personal information. Advertisers receive aggregate, non-identifying audience information only.

6. Cross-border transfer

Our database, private file storage and sign-in run on Supabase, in its London region in the United Kingdom, and the server functions that handle the platform’s forms and pages run in London too. A Supabase project is held in one region, fixed when the project is created; no African region was available to us, so we chose the one closest to South Africa with acceptable latency. Our transactional email is sent through Resend, which also processes outside South Africa.

These are cross-border transfers, and section 72 of POPIA applies to them. We rely on the providers’ written data processing terms, which bind them to our instructions and impose protection substantially similar to the conditions for lawful processing in POPIA, and on the data protection law of the country the information is held in. Where any other service provider processes information outside South Africa, we do so only where that country has comparable protection, or where a written agreement imposes protection substantially similar to POPIA.

7. How long we keep it

  • Enquiries that do not proceed: 24 months, then deleted or anonymised.
  • Completed jobs and project records: retained for the period required for professional liability and statutory record keeping, generally not less than 5 years.
  • Financial and tax records: 5 years, as required by law.
  • Professional verification documents: for as long as you are registered on the platform, plus the period required to demonstrate that verification was properly performed.
  • Marketing consent records: until you withdraw consent, plus proof of the withdrawal.

Nothing is deleted automatically. A deletion request is recorded, given a reference and worked by a person, who keeps only what the law requires and deletes or anonymises the rest. While a professional application is a draft, or has changes requested, you can remove a document you uploaded yourself; after submission it is held for the period above.

8. Your rights

Under POPIA you may:

  • Ask what personal information we hold about you, and receive a copy
  • Ask us to correct information that is inaccurate, misleading or out of date
  • Ask us to delete information we no longer have a lawful reason to keep
  • Object to processing based on legitimate interest
  • Withdraw consent, where consent is the basis we rely on
  • Complain to the Information Regulator of South Africa

There are two routes:

  • Email admin@myengineer.co.za with the subject [MyEngineer] POPIA Request.
  • If you have an account, ask for deletion in your account settings. The request is recorded with a reference, placed in the co-ordination desk’s queue and answered by a person, so you can quote the reference when you follow it up.

We respond within the statutory period. We may need to verify your identity first, and some information must be retained where the law requires it. We tell you what we kept, and why.

9. Security

We apply appropriate, reasonable technical and organisational measures. In practice that means:

  • Encryption in transit, and encryption at rest for the whole database and the file storage
  • Field level encryption, with a separate key, for identity numbers and registration numbers, which are masked in your own view
  • Passwords held only as a one-way hash, which we cannot reverse
  • A sign-in cookie that scripts cannot read and that is restricted to this site. Signing out ends that session on the server, so the cookie cannot be used again, and changing your password ends every other session
  • Row level security in the database, so your records are readable by you and by the co-ordination desk, and by nobody else
  • Private file storage with no public address, permission-checked downloads and an access log
  • Rate limiting on the forms, keyed to a one-way hash of your network address, which is never stored or logged in a readable form
  • Server logs that carry references, error codes and tags only, never names, contact details, identity numbers or the contents of a message
  • Separation of identity data from public data, access on a need-to-know basis, and regular review

No system is perfectly secure. If a compromise affects your personal information, we will notify you and the Information Regulator, as POPIA requires.

10. Cookies, storage and messages you send

We use the minimum necessary.

  • A sign-in cookie, set only when you sign in. It keeps you signed in and is removed when you sign out.
  • A short list in your own browser of enquiries sent from that browser. It holds the reference, the title and the time, so you can find an enquiry again without an account. It holds no name, address or message, it never reaches us, and clearing your browser data removes it.
  • No cross-site advertising trackers, and no analytics product at all today. If we add one, it will be a privacy-respecting one that does not follow you to other websites, and this notice will say so first.

Your browser lets you refuse cookies. The public parts of the site still work; you will not be able to stay signed in.

What happens to an enquiry you send

An enquiry is submitted to MyEngineer. It is stored on the platform against a reference such as JOB-2609-K7QX, emailed to the co-ordination desk with the subject line shown in the preview, and a receipt with the same reference is emailed to you. Where a WhatsApp number is published and you choose to continue there instead, that message is sent from your own WhatsApp account, and the terms of your messaging provider apply to it.

11. Children

The platform is not directed at children under 18. Where a learner uses the Knowledge Centre career material, we do not knowingly collect their personal information without the consent of a competent person.

12. Changes

We will update this notice as the platform develops, and the version stamp and review date below change with it. Material changes affecting how we use your information will be communicated directly.

Document control

Version
2026-09-30-draft
Last reviewed
September 2026
Status
Draft for attorney review. Not yet adopted.

The version stamp above is recorded with every consent given on the platform, so we can show which text a person accepted and when.

Something here unclear or wrong?

These documents are still in draft. If a clause reads badly, or does not match what the platform actually does, tell the co-ordination desk and we will put it in front of the attorney reviewing the set.