Version v1.3 · 20 October 2026. · Last updated 20 October 2026

IndabaPay Data Processing Agreement

FieldValue
Versionv1.3
Effective date20 October 2026
Last updated20 October 2026
RelatedTerms of Service v1.7; Privacy Notice v1.2

This Data Processing Agreement (DPA) is between the Client (responsible party) and IndabaPay, operated by Coetzee Accounting and Labour Relations (Pty) Ltd, Reg 2018/434623/07 (IndabaPay, operator), and forms part of the IndabaPay Terms of Service (Terms).

It implements POPIA sections 20 and 21 (operator duties and written contract) and related Conditions for Lawful Processing.


1. Definitions

Terms used here have the meanings in the Protection of Personal Information Act 4 of 2013 (POPIA) unless stated otherwise, including: personal information, special personal information, data subject, responsible party, operator, processing, Information Regulator.

Service means the IndabaPay payroll / HR SaaS. Sub-operator means a third party engaged by IndabaPay to process personal information on IndabaPay’s behalf in providing the Service. AI-assisted document reading means optional sending of a Client-uploaded court / garnishee / maintenance order or labour award / settlement to a vetted AI document-reading sub-operator to suggest fields for Client confirmation.


2. Roles

  • The Client is the responsible party for personal information of its employees and related data subjects that it enters into or uploads to the Service.
  • IndabaPay is the Client’s operator for that processing.
  • For IndabaPay’s own customer-account, billing, and marketing data about Client users, IndabaPay may be a responsible party (see Privacy Notice). Those activities are outside the operator mandate of this DPA except where they overlap with Service delivery.

3. Subject matter, duration, nature and purpose

ItemDescription
Subject matterHosting and processing of Client HR / payroll data to provide the Service
DurationFrom account creation until deletion under the Terms (including trial archive up to 5 years from lock / paid post-termination windows), plus any legal hold or permitted tombstone
NatureCollection, storage, organisation, retrieval, calculation, disclosure to Client users, transmission to Client-authorised sub-operators, deletion
PurposeProvide payroll, payslips, statutory calculation assists, leave/clocking, HR document tools, EE reporting assists, order/award capture, billing of the Service, and security/support

IndabaPay processes only on the Client’s documented instructions (configuration in the Service, uploads, toggles, and these Terms/DPA), unless law requires otherwise (POPIA s20).


4. Data subjects and categories of personal information

Data subjects may include: employees and workers; contractors captured in payroll/HR; job applicants (if stored); dependants / children named on maintenance orders; Client users (Owners, Payroll admins, Clocking agents, Viewers, brokers where enabled).

Ordinary personal information may include: names, identity / passport numbers, contact details, addresses, bank details, employment history, remuneration, tax and UIF references, leave and hours, documents uploaded to the vault.

Special personal information (POPIA s26) may include, where the Client chooses to process it in the Service: race / population group and disability (EE); health-related information (e.g. sick notes or medical certificates if uploaded); information concerning criminal behaviour or alleged offences in disciplinary records; trade union membership.

Children’s information (POPIA s34–s35) may appear on maintenance orders or similar uploads.

The Client determines which categories it loads. IndabaPay does not require special personal information beyond what a given feature needs.


5. Client instructions and lawful basis

The Client warrants that it has a lawful basis under POPIA (including s11 and, where applicable, s27 / s35) for the processing it instructs, and that it has given any required notifications to data subjects (s18). IndabaPay does not decide employment outcomes and does not submit statutory returns unless a specific assist feature sends mail on the Client’s instruction (e.g. certain UIF assists); the Client remains responsible for correctness and authority filings.


6. Confidentiality

IndabaPay ensures that persons authorised to process personal information are bound by confidentiality (contract or law) and access only what their role requires.


7. Security (POPIA s19)

IndabaPay implements appropriate technical and organisational measures as summarised in Schedule B, including access control, encryption in transit, EE identity encryption at rest where implemented, audit logging, and backups. The Client must also secure its own devices, passwords, and downloaded files.


8. Breach notification (POPIA s21 / s22)

If IndabaPay becomes aware of a personal-information security compromise affecting Client data, it will notify the Client without undue delay, with a target of seventy-two (72) hours of becoming aware, including: nature of the compromise (known facts); categories of data subjects and information affected (where known); measures taken or proposed; and a contact point. The Client remains responsible for any notification to the Information Regulator and data subjects required of a responsible party, unless law assigns a duty to IndabaPay.


9. Sub-operators

9.1 The Client gives general written authorisation for IndabaPay to appoint sub-operators listed in Schedule A (as updated).

9.2 IndabaPay will bind each sub-operator by written contract to confidentiality, security measures no less protective than POPIA s19, breach notification, deletion or return on request, and restrictions on further transfer consistent with this DPA.

9.3 IndabaPay will give the Client at least thirty (30) days’ prior notice of a new sub-operator or a material change to Schedule A (email or in-app). The Client may object on reasonable POPIA grounds. If the parties cannot resolve the objection, the Client may terminate the affected Service as its sole remedy (pro-rata refund of prepaid unused subscription fees where applicable, to the extent required by law).

9.4 AI-assisted document reading — sub-operator clause

Sub-operators and AI-assisted document reading. The Client authorises IndabaPay to engage vetted sub-operators to process personal information on the Client’s behalf, including hosting, email delivery, payment processing, and AI-assisted reading of documents the Client uploads (court orders, garnishee / emoluments attachment orders, maintenance orders, and CCMA / bargaining-council awards or settlements) solely to suggest fields for the Client’s review. IndabaPay will: (a) list material sub-operators in Schedule A (or an in-product sub-operator list), updated on reasonable notice; (b) bind each sub-operator by written contract to confidentiality, security measures no less protective than POPIA s19, breach notification, deletion or return on request, no use of Client data to train models, and no retention longer than needed to return the extraction result (zero or short retention where the provider offers it); (c) not send employee personal information to an AI provider except the uploaded document the Client chooses to analyse; and (d) require a Client user to confirm or correct each extracted field before it is saved to payroll. The Client remains the responsible party; IndabaPay remains the operator. The Client may disable AI-assisted extraction for its organisation; manual capture remains available.

9.5 AI-assisted document reading is off by default (per-organisation toggle). It remains blocked until the organisation has accepted the current DPA version. Enabling the toggle constitutes a documented instruction to use the AI sub-operator for subsequent uploads the Client chooses to analyse with AI.


10. Cross-border transfers (POPIA s72; s57 / s58)

10.1 Plain statement. Personal information in the Service — including employee personal information — is hosted primarily in the United States of America (application hosting, database, private file storage, and transactional email). Payment processing is in South Africa. Optional address suggestions may be processed in Germany / the EU. Named sub-operators and regions are in Schedule A (provided in-app on or immediately after acceptance, or on written request to admin@indabapay.com). If the Client enables AI-assisted document reading, the uploaded document is processed in the European Union (Sweden) and is not kept by the provider; the named provider is in Schedule A.

10.2 Transfers outside the Republic rely primarily on POPIA s72(1)(a): each relevant sub-operator is bound by a written agreement (and/or applicable law / binding corporate rules) that provides an adequate level of protection substantially similar to POPIA’s Conditions for Lawful Processing, including controls on onward transfer.

10.3 By accepting this DPA (including at signup or on re-acceptance), the Client instructs and authorises IndabaPay to make those transfers to the sub-operators in Schedule A for the stated purposes, and acknowledges the same disclosure in the Privacy Notice.

10.4 Where prior authorisation under s57 / s58 may be required (including transfer of special personal information or children’s information to a third party in a foreign country that does not provide adequate protection), IndabaPay will not enable that processing path until the parties have addressed the requirement (provider terms / region giving adequate protection, or attorney-confirmed filing). Residual risk is managed carefully; this clause is not a waiver of POPIA.


11. Assistance — data subject rights, Regulator, assessments

Taking into account the nature of processing, IndabaPay will reasonably assist the Client with:

  • data-subject requests under POPIA s23–s25 (access, correction, destruction/deletion, objection) insofar as they relate to data in the Service;
  • Information Regulator queries; and
  • data-protection impact assessments where reasonably required,

at the Client’s request and, for disproportionate work, at the Client’s reasonable cost.


12. Return and deletion

12.1 Paid accounts. On termination of a paid subscription, after the post-termination window in the Terms (typically 90 days, unless legal hold), IndabaPay will delete or irreversibly anonymise Client personal information in live systems, except: (a) data IndabaPay must retain as a responsible party (e.g. invoices); (b) legal hold; (c) backups cycling out on normal schedules. During that window the Client may download payslips and reports while access remains available, or request in writing (service@indabapay.com) PDF payslips and pay registers (not a format for import into other software); a reasonable admin fee may apply. Documents already downloaded or printed remain the Client’s.

12.2 Free trial — archive, restore, purge. If the Client does not subscribe by trial end, the organisation is locked (Subscribe only in-app). IndabaPay then moves the trial organisation’s personal information into a secure archive for up to five (5) years from the lock date: encrypted; no tenant access; access limited to authorised IndabaPay staff for restore and legal purposes. By accepting the Terms and this DPA at signup, the Client instructs and authorises that retention (POPIA s20 documented instructions; s14 retention authorised by agreement), as disclosed in the Terms Free trial clause and the Privacy Notice. If the Client subscribes within the archive period, IndabaPay restores the data in full. After five years (or earlier under clause 12.3), archived operational data is permanently deleted, subject to legal hold. A minimal tombstone (organisation id and name; created / locked / deleted dates; reason; notice counts — no employee data) may be kept for three (3) years, then purged.

12.3 Earlier deletion on request. The Client may instruct earlier deletion of archived trial data by written request to service@indabapay.com. Subject to legal hold, IndabaPay will delete within thirty (30) days. While archived, the Client may request PDF payslips and pay registers as in clause 12.1.

12.4 The Client remains responsible for its own statutory retention (including Tax Administration Act ~5 years; BCEA s31 ~3 years; UIF/COIDA). IndabaPay’s archive does not discharge those duties. The Client should download the payslips and reports it needs, or subscribe to keep using its payroll.


13. Audit and information rights

On reasonable written notice (at least 14 days), no more than once per calendar year (unless a personal-information compromise or Regulator request requires more), IndabaPay will provide information reasonably necessary to demonstrate compliance with this DPA, which may include security summaries or third-party certifications where available. On-site audits are by mutual agreement, during business hours, without disrupting operations, and at the Client’s cost unless a material breach of this DPA is found.


14. Liability and precedence

Liability arising from this DPA is subject to the limitation of liability and indemnity in the Terms. On data-protection subject matter, this DPA prevails over the Terms if they conflict.


15. Amendments and re-acceptance

15.1 IndabaPay will give at least thirty (30) days’ notice of material changes to this DPA or of new sub-operators (clause 9.3).

15.2 Material DPA wording changes require the Client’s re-acceptance (tick or equivalent). Until accepted, AI-assisted document reading and other features that depend on the new authorisation may remain blocked; core payroll continues where the Terms allow.

15.3 This version (v1.3) is effective from 20 October 2026. The Client accepts it when signing up.


16. Governing law

This DPA is governed by the laws of South Africa. Dispute resolution follows the Terms.


Schedule A — Sub-operators

Public summary. IndabaPay uses sub-operators in these categories: application hosting, database hosting, private file storage, transactional email (each primarily USA); payment processing (South Africa); optional address suggestions (Germany / EU); and, only if enabled by the Client, AI-assisted document reading (European Union; the provider does not keep the document or use it to train AI models).

Named list. The current named providers, regions, and evidence notes are provided in-app on or immediately after acceptance, and on written request to admin@indabapay.com. IndabaPay will give at least thirty (30) days’ prior notice of a new sub-operator or material Schedule A change (email or in-app), with objection rights as in clause 9.3.

Cross-border note: Employee and related personal information is hosted primarily in the United States. Payment processing is in South Africa. Optional address suggestions may be processed in Germany / the EU. Transfers are authorised under clause 10 and the Client’s acceptance of this DPA. AI-assisted document reading, if enabled by the Client, is processed in the European Union.


Schedule B — Security measures (summary)

  1. Access control / RBAC — organisation-scoped data; roles (Owner, Payroll admin, Clocking, Viewer) and capability checks in application code.
  2. Authentication — credentialed login (session / next-auth-style); password hashing; invite / set-password flows.
  3. Encryption in transit — TLS / HTTPS enforced for Service access on indabapay.com (hosting provider).
  4. Encryption at rest — EE identity / passport fields 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.
  5. Private document storage — production uploads use private object storage via the file-storage provider; fails closed if the private store is unavailable.
  6. Audit logs — security-relevant actions logged (including document upload and EE POPIA acknowledgement patterns).
  7. Backups — 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.
  8. Minimality for AI — only the uploaded order/award document may be sent; field confirmation required; feature default OFF; provider listed in Schedule A before the feature is enabled.
  9. Vulnerability / dependency management — reasonable dependency and patch management for the application stack; formal penetration testing may be commissioned periodically as the Service scales.
  10. Personnel — access limited to those who need it for support and operations, under confidentiality.

End of DPA v1.3

Data Processing Agreement