The fine print
FinalOps (Pty) Ltd, South Africa. In effect from 30 October 2026.
Between the Customer named in the FinalOps account (the "Responsible Party") and FinalOps (Pty) Ltd, registration number 2026/777368/07, trading as FinalOps, of 194 Bancor Avenue, Park Lane West Building, Waterkloof Glen, Pretoria, 0181 (the "Operator").
This addendum forms part of the FinalOps terms of service between the parties. It applies to personal information that the Operator processes on the Responsible Party's behalf while providing the service. In it, "POPIA" means the Protection of Personal Information Act 4 of 2013. Terms defined in POPIA have the same meaning here.
1. Roles
For the personal information in the Customer's data (including the records synchronised from the Customer's ERP), the Customer is the responsible party and FinalOps is its operator (POPIA s1, s20, s21). For account, security and billing information about the Customer's users, FinalOps is a responsible party in its own right, under its privacy policy.
2. Instructions (s20(a))
The Operator processes the personal information only with the Responsible Party's knowledge or authorisation. The instructions are: the terms of service, this addendum, and the Responsible Party's configuration and use of the service (connecting an ERP, the sync and posting settings, the users it invites). The Operator does not use the information for its own purposes and does not sell it.
3. Confidentiality (s20(b))
The Operator treats the personal information as confidential and does not disclose it, unless the law requires it or disclosure is part of properly performing the service. Everyone at the Operator with access is bound to confidentiality.
4. Security measures (s19, s21(1))
The Operator establishes and maintains appropriate, reasonable technical and organisational measures, and regularly verifies them, to prevent loss, damage, unauthorised destruction, and unlawful access or processing. At the date of this addendum they include:
- encryption in transit (TLS) and at rest (encrypted disks and backups);
- ERP tokens and integration secrets encrypted with a key held apart from the data (AES-256-GCM);
- per-customer separation enforced in the database (row-level security, forced, per-application roles without bypass rights);
- multi-factor authentication for the Operator's staff on every system, least-privilege access, and an audit trail of support access;
- sign-in throttling, a web application firewall with rate limits on sign-in routes, dependency and container image scanning;
- backups kept 30 days and a tested restore.
The current list is published in the security section of the privacy policy. The Operator may improve the measures, but never reduce them below this level.
5. Sub-processors
The Responsible Party authorises the sub-processors listed at /legal/sub-processors. The Operator binds each one by written contract to protection at least equivalent to this addendum. It gives at least 30 days' notice by email to the account owners before adding or replacing a sub-processor. The Responsible Party may object on reasonable grounds, and if the parties cannot resolve the objection, it may end the service and receive a pro-rata refund of prepaid fees.
6. Security compromises (s21(2), s22)
The Operator notifies the Responsible Party immediately where there are reasonable grounds to believe that personal information has been accessed or acquired by an unauthorised person. It then provides what it knows and learns (nature, categories and approximate numbers of data subjects and records, likely consequences, the measures taken) so that the Responsible Party can notify the Information Regulator and data subjects under s22. The Operator does not notify the Responsible Party's data subjects itself unless the Responsible Party asks it to.
7. Data subject requests
If a data subject contacts the Operator about the Responsible Party's data, the Operator refers them to the Responsible Party. The service lets the Responsible Party's owners export all of its data and delete its organisation themselves. The Operator helps with other requests within a reasonable time.
8. Transfers (s72)
The Operator hosts the Responsible Party's data in Germany. Some sub-processors process data in other countries as listed at /legal/sub-processors. Each transfer relies on a ground in s72(1), as stated there.
9. Return and deletion
The Responsible Party can export its data at any time. When it closes its organisation, the Operator deletes the Responsible Party's data 30 days after closure (a cooling-off the owner can cancel). The exceptions are the Operator's own invoices and billing records, which the law requires it to keep, and data in backups, which expire 30 days later. Deletion revokes the Operator's access to the Responsible Party's ERP at the ERP provider.
10. Audit
On reasonable written notice, and no more than once a year unless there has been a security compromise, the Operator answers the Responsible Party's written security questionnaire and makes available its current security review (controls, proof commands and dates).
11. Liability and term
Liability is as limited in the terms of service. This addendum lasts as long as the Operator processes personal information for the Responsible Party.
12. Law
The law of the Republic of South Africa governs this addendum.
Signatures
Signed for the Operator, FinalOps (Pty) Ltd: name, capacity and date, on the signed copy.
Signed for the Responsible Party: accepted electronically in the FinalOps account by an owner on the date recorded in the audit log.