Version v1.2 (aligned to DPA v1.3) · Effective 20 October 2026 · Last updated 20 October 2026
IndabaPay Privacy Notice
| Field | Value |
|---|---|
| Version | v1.2 (aligned to DPA v1.3) |
| Effective date | 20 October 2026 |
| Last updated | 20 October 2026 |
This notice explains how IndabaPay (operated by Coetzee Accounting and Labour Relations (Pty) Ltd, Reg 2018/434623/07, VAT 4230302343) processes personal information under the Protection of Personal Information Act 4 of 2013 (POPIA). It is our section 18-style notification for people whose information we process as a responsible party, and it also explains how we act as an operator for employers.
1. Who we are and how to contact us
| Product / trading name | IndabaPay |
| Registered name (POPIA s18) | Coetzee Accounting and Labour Relations (Pty) Ltd (Reg 2018/434623/07, VAT 4230302343) |
| admin@indabapay.com | |
| Information Officer | Roandi Coetzee (director) — email above |
Website / app: https://indabapay.com
Other purpose-specific addresses (support, billing, lifecycle, marketing, security, formal legal) are listed in the Terms of Service contact-emails table.
Physical address and further supplier details (where ECTA s43 applies) are in the Terms of Service supplier table — not repeated here.
2. Two roles (please read this carefully)
A. Operator for employer clients. When an employer uses IndabaPay for payroll and HR, that employer is the responsible party for its employees’ (and related) personal information. IndabaPay processes that information as the employer’s operator under a Data Processing Agreement (DPA). Employees who want access, correction, or deletion of employment data should usually contact their employer first. We will assist the employer under the DPA.
B. Responsible party for our own customer data. For accounts of Client users (names, work emails, login, billing contacts, invoices, support tickets, and limited marketing where lawful), IndabaPay is the responsible party.
3. What we collect
Client-user / billing data (we are often responsible party): name, work email, phone (if provided), role, organisation details (legal name, CIPC, addresses, VAT), payment references via PayFast, support correspondence, IP address and approximate login metadata for security.
Employee / HR / payroll data (client is responsible party; we are operator): identity and contact details; bank and tax/UIF references; pay, leave, hours; documents (contracts, IDs, court orders, awards, certificates); EE demographics where the client uses that module; disciplinary records if stored; other fields the client enters.
Special personal information / children: processed only as instructed by the client (e.g. EE race/disability; health documents; disciplinary content; children’s details on maintenance orders). See DPA.
We do not knowingly use the Service as a consumer social network for children.
4. Purposes and lawful bases (POPIA s11)
Depending on context, we process because:
- it is necessary to perform a contract with the Client (provide the Service, trial, support, billing);
- it is necessary for a legitimate interest (security, fraud prevention, improving service reliability) balanced against your rights;
- we must comply with a legal obligation (tax invoices, responding to the Information Regulator or a court);
- you consented (e.g. optional marketing — see below); or
- another s11 ground applies.
For operator processing, the client’s lawful basis applies to employee data (often legal obligation / contract of employment / legitimate interests of the employer).
5. AI-assisted document reading
AI-assisted document reading. If your organisation enables this feature, IndabaPay may send a court order, garnishee / maintenance order, labour award or settlement agreement you upload to a vetted third-party AI document-reading service in the European Union so we can suggest fields for you to check. We send only that document, not your wider employee file. The provider is contractually required not to use your data to train AI models and does not keep the document after processing. You confirm every field before it is saved. You can turn the feature off and enter details manually. See our Data Processing Agreement (DPA) for sub-operators and transfer safeguards.
The organisation toggle defaults to OFF. The feature stays blocked until the current DPA is accepted.
6. Sharing and sub-operators
We share personal information with:
- sub-operators in these categories (names and exact regions are in DPA Schedule A, provided in-app when you accept the DPA, or on written request to admin@indabapay.com):
- application hosting and related infrastructure (primarily USA);
- database hosting (primarily USA);
- private file / document storage (primarily USA);
- transactional email delivery (primarily USA);
- payment processing (South Africa);
- optional address-suggestion tooling (Germany / EU, where used);
- optional AI-assisted document reading (only if your organisation enables it; European Union; the provider does not keep the document or use it to train AI models);
- a licensed financial services partner, only when you request quotes;
- professional advisers under confidentiality;
- authorities when legally required.
That licensed financial services partner is a separate responsible party. It is not a sub-operator and is not listed in DPA Schedule A.
We do not sell personal information.
7. Cross-border transfers
Employee and related personal information in IndabaPay is hosted primarily in the United States (application, database, file storage, and transactional email). Payment processing is in South Africa. Optional address suggestions may be processed in Germany / the EU. Named providers appear in DPA Schedule A (in-app or on request). AI-assisted document reading, if your organisation enables it, is processed in the European Union.
Transfers outside South Africa are made under POPIA s72(1)(a): the recipients are bound by written agreements that provide protection substantially similar to POPIA, including onward-transfer controls. By accepting the Data Processing Agreement (at signup or on re-acceptance), the client employer authorises those transfers for the purposes of the Service. See DPA clause 10 and Schedule A.
8. Retention
| Context | Retention |
|---|---|
| Active paid account | For the life of the account, then typically up to 90 days after termination, then deletion (subject to legal hold and supplier tax/billing records). During that window you may download payslips/reports while access remains, or request PDF payslips and pay registers in writing (service@indabapay.com; reasonable admin fee may apply; not an importable data dump). |
| Free trial (no subscribe) | Locked after 30 days (Subscribe only in-app). Trial data is moved to a secure archive for up to 5 years from the lock date (encrypted; no tenant access; staff restore/legal access only), as authorised in the Terms and DPA at signup. Subscribe within that period to restore in full. After 5 years, permanent deletion (subject to legal hold), then a minimal tombstone for 3 years. You may instruct earlier deletion in writing (service@indabapay.com); we delete within 30 days subject to legal hold. While archived you may request PDF payslips and pay registers (reasonable admin fee; not importable). Documents already downloaded or printed remain yours. |
| Trial tombstone | Org id, org name, created/locked/deleted dates, reason, notice counts — no employee data — kept 3 years after permanent deletion, then purged |
| Invoices / supplier records | As required for tax and accounting |
| Legal hold | Suspends deletion / purge for the duration of the hold |
Employers must keep their own payroll records (including Tax Administration Act ~5 years, BCEA s31 ~3 years, and UIF/COIDA duties). IndabaPay’s archive does not replace that duty. Please download the payslips and reports you need, or subscribe to keep using your payroll.
9. Security
We use role-based access, HTTPS (TLS enforced on indabapay.com), private document storage in production, and audit logging. EE identity / passport fields are encrypted in-application with AES-256-GCM. Broader database and file-storage encryption at rest follows provider defaults (AES-256); IndabaPay has not configured customer-managed encryption keys for those stores. Database backups / point-in-time recovery follow the database provider’s plan defaults for the production project (region USA). Exact retention days depend on the live plan tier and are confirmable in the provider console; IndabaPay does not currently publish a fixed multi-day figure beyond those provider defaults. See DPA Schedule B.
10. Your rights
Depending on your role (Client user vs employee of a Client), you may have rights under POPIA to access, correct, delete or object to processing, and to complain to the Information Regulator.
- Client users: contact admin@indabapay.com / the Information Officer.
- Employees: contact your employer (responsible party); we will assist them under the DPA.
Information Regulator (South Africa) Website: https://inforegulator.org.za/ General: enquiries@inforegulator.org.za · Tel 010 023 5200 · Toll-free 0800 017 160 POPIA complaints: POPIAComplaints@inforegulator.org.za (Form 5) PAIA complaints: PAIAComplaints@inforegulator.org.za Address: Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191
11. Cookies
We use essential cookies / storage only for login and session security (portal session cookies and authentication / next-auth-style session cookies). We do not use non-essential cookies (including marketing or analytics cookies), so no cookie consent banner is required for the current cookie set. If we introduce non-essential cookies later, we will update this notice and obtain consent where required.
12. Direct marketing (POPIA s69)
We may send Service and account messages (transactional). For optional electronic marketing to Client contacts, we will honour opt-out requests. Reply “unsubscribe” or email admin@indabapay.com.
13. PAIA
A Promotion of Access to Information Act 2 of 2000 (PAIA) manual for Coetzee Accounting and Labour Relations (Pty) Ltd is available on request from admin@indabapay.com.
14. Changes
We may update this notice. Material changes will be notified in-app or by email. The effective date appears at the top.
15. Contact
Information Officer: Roandi Coetzee Email: admin@indabapay.com
Our registered name and physical address are in the Terms of Service.
