The fine print
FinalOps (Pty) Ltd, South Africa. In effect from 30 October 2026.
1. Who we are
FinalOps is operated by FinalOps (Pty) Ltd (registration number 2026/777368/07), a company incorporated in South Africa, at 194 Bancor Avenue, Park Lane West Building, Waterkloof Glen, Pretoria, 0181. This policy explains how we handle personal information under the Protection of Personal Information Act, 4 of 2013 (POPIA). We have written it to be compatible with the EU General Data Protection Regulation for anyone reading it from there.
Information Officer: Alwyn Kotze, CTO. Deputy Information Officer: David Turner, CFO. Questions and requests about personal information go to support@finalops.co.za. Our PAIA manual is at /legal/paia.
2. Two roles: responsible party and operator
For information about visitors to this website and about the people who hold accounts with us, we are the responsible party. For the business data our customers bring into FinalOps, including the personal information of their own customers, suppliers and staff that is held in their ERP, the customer is the responsible party and we act as their operator under sections 20 and 21 of POPIA. We process that data only on the customer's instructions, under our terms of service and our data processing addendum, and we do not use it for our own purposes.
3. What we collect
On this website
- What you type into the contact form: name, company, email address, the ERP you run, your message.
- Server logs: IP address, browser type, the pages requested and when, kept for security and troubleshooting.
- How you arrived, only if you allow it in the cookie notice: the campaign parameters in the link you followed, the site that referred you and the first page you saw, kept in cookies of our own (section 10) so that, if you start a trial or write to us, we know which campaign brought you.
- Analytics: Google Tag Manager and Google Analytics load only after you allow them in the cookie notice. If you decline or ignore the notice, nothing is requested from Google and no analytics cookies are set.
When you open an account
- Your name, email address, organisation name and role.
- Login records: when and from where you signed in, and the security events on your account.
- Billing records: your plan, invoices and payment status. Card details go directly to Paystack and never reach our servers.
- Support correspondence.
- Product usage inside the applications, through PostHog, so we can see which features are used and where people get stuck.
When you connect an ERP
- An access token for your ERP, stored encrypted, used only to sync the data you authorised.
- A synchronised copy of the records you connect: contacts, items, accounts, invoices, bills, journals and related documents. This is customer data; we hold it as your operator.
4. Why we use it, and on what basis
| Purpose | Lawful basis (POPIA section 11) |
|---|---|
| Answering an enquiry sent through the contact form | Your consent, and our legitimate interest in replying to you |
| Providing the service you signed up for, including the ERP sync | Performance of a contract |
| Billing and collecting subscriptions | Performance of a contract; legal obligation to keep accounting records |
| Securing accounts and detecting abuse | Legitimate interest |
| Measuring website traffic | Your consent, given in the cookie notice |
| Improving the product from usage inside the applications | Legitimate interest, disclosed in the terms of service |
| Sending service and security email about your account | Performance of a contract |
| Sending marketing email | Your consent, which you can withdraw at any time |
5. Who we share it with
We do not sell personal information. We share it only with the operators below, each bound by a written agreement to protect it and to use it only for the stated purpose, and with authorities where the law requires. The sub-processors page adds what each one handles and the safeguard for it.
| Operator | Purpose | Where |
|---|---|---|
| Vercel | Hosting the website and the web applications, the edge network and the firewall | Germany (Frankfurt) for the servers that run our code; a global edge network; the company is in the United States |
| Hetzner | The database, the background worker, file storage and backups | Germany (Nuremberg) |
| Cloudflare | DNS, and network security for the servers that are not on Vercel | Global network |
| Resend | The email the service sends: sign-in, invitations, invoices and notices | United States |
| Paystack | Subscription payments | Nigeria and South Africa |
| Xero | The accounting system a customer connects | As Xero's own terms say (Xero is the customer's own provider) |
| Google Workspace mailboxes (support and the founders); Google Tag Manager and Google Analytics on the website, only after consent | Global | |
| Anthropic | Language models that help us operate the service | United States |
| PostHog | Product analytics inside the applications | European Union (PostHog's EU cloud) |
| Sentry | Error reporting | European Union (Sentry's EU region) |
| GitHub | Source code, the automation that builds the service, issue tracking | United States |
6. Transfers outside South Africa
Our databases and background workers run in Germany, and the web applications are served from Germany with a global content network in front of them. Section 72 of POPIA allows a transfer outside South Africa where the recipient is subject to a law or binding agreement that gives substantially similar protection. Germany applies the GDPR, and each operator above is bound by contract to standards at least as strong as POPIA. Where an operator processes data in the United States, we rely on contractual safeguards with that operator.
7. How long we keep it
- Contact form messages: until the enquiry is closed, and at most 24 months.
- Account and organisation records: for as long as the account is open, then 30 days after closure, after which they are deleted.
- Customer data synced from an ERP: deleted 30 days after the organisation is closed.
- Accounting records, including our invoices to you: 7 years, as the Companies Act requires.
- Tax records: 5 years, as the Tax Administration Act requires.
- Backups: 30 days, encrypted, then overwritten. Data deleted from the service stays in these backups until they expire.
- Sign-in and security records: 12 months.
- Server logs: 30 days.
8. How we protect it
- Encryption in transit everywhere, and at rest on our disks and backups.
- ERP tokens and integration secrets are encrypted with keys held separately from the data.
- Every customer's data is separated from every other customer's at the database level.
- Multi-factor authentication for our staff on every system, and access limited to what a role needs.
- Dependency and image scanning, rate limits on sign-in, and monitoring for unusual activity.
If a security compromise affects personal information, we will notify the Information Regulator and the affected people as soon as reasonably possible, as section 22 of POPIA requires, and tell you what happened and what we are doing about it.
9. Your rights
Under POPIA you may:
- ask whether we hold personal information about you, and get a copy of it;
- ask us to correct or delete it;
- object to processing based on legitimate interest, and to direct marketing at any time;
- withdraw consent where consent is the basis, without affecting what was done before;
- complain to the Information Regulator (South Africa) at inforegulator.org.za.
Send requests to support@finalops.co.za. We answer within 30 days. Account owners can also export and delete their organisation's data from inside the application. If your information sits in a customer's organisation, we will refer your request to that customer, who is the responsible party for it.
10. Cookies
Until you answer the cookie notice this website stores nothing on your device. Your answer is kept in one cookie, and two more are set only if the answer is Allow:
fo_consentremembers your answer to the cookie notice for 180 days so we do not ask again.fo_attr, only after Allow, records how you first arrived: campaign parameters such asutm_sourceandgclid, the referring site, the first page you saw and when. It is written once, kept for 90 days, identifies no one on its own, and is passed to the application if you start a trial, and to us if you write to us.fo_attr_last, only after Allow, holds the same facts for your most recent arrival through a campaign link, for 90 days.
If you choose Decline, both fo_attr cookies are removed if they were there. Google Tag Manager and Google Analytics load, and set their cookies, only after you choose Allow in the notice. The applications set a session cookie needed to keep you signed in, which is not optional, and use PostHog for product analytics as disclosed in the terms of service.
11. Children
The service is for businesses and is not directed at anyone under 18. We do not knowingly collect personal information from children.
12. Changes
When this policy changes we will put the new date at the top and, for material changes, tell account holders by email before they take effect.