The fine print
FinalOps (Pty) Ltd, South Africa. In effect from 30 October 2026.
These are the companies that handle personal information for us while we run FinalOps. POPIA calls them operators; a contract usually calls them sub-processors. Each one is bound by a written contract to keep the information secure, as section 21 of POPIA requires.
1. Who they are
Vercel
| What we use it for | Hosting the website and the web applications, the edge network and the firewall |
|---|---|
| Personal information handled | Everything a request carries: IP address, cookies, form fields, pages rendered with a customer's data; server logs |
| Where | Germany (Frankfurt) for the servers that run our code; a global edge network; the company is in the United States |
| Safeguard | Section 72(1)(a): Vercel's data processing addendum with EU standard contractual clauses; our code runs in the EU |
| Contract | Vercel data processing addendum |
Hetzner
| What we use it for | The database, the background worker, file storage and backups |
|---|---|
| Personal information handled | All platform data at rest: accounts, customers' data, documents, backups |
| Where | Germany (Nuremberg) |
| Safeguard | Section 72(1)(a): Germany applies the GDPR |
| Contract | Hetzner data processing agreement (Auftragsverarbeitungsvertrag) |
Cloudflare
| What we use it for | DNS, and network security for the servers that are not on Vercel |
|---|---|
| Personal information handled | IP addresses and request details in transit |
| Where | Global network |
| Safeguard | Section 72(1)(a): Cloudflare's data processing addendum with standard contractual clauses |
| Contract | Cloudflare data processing addendum |
Resend
| What we use it for | The email the service sends: sign-in, invitations, invoices and notices |
|---|---|
| Personal information handled | The recipient's email address and name; the content of the mail (links, invoice numbers) |
| Where | United States |
| Safeguard | Section 72(1)(a): Resend's data processing addendum; section 72(1)(c) for account mail |
| Contract | Resend data processing addendum |
Paystack
| What we use it for | Subscription payments |
|---|---|
| Personal information handled | Billing email, name, amount, payment references. Card details go to Paystack only, never to us |
| Where | Nigeria and South Africa |
| Safeguard | Section 72(1)(c): necessary for the subscription contract |
| Contract | Paystack merchant terms |
Xero
| What we use it for | The accounting system a customer connects |
|---|---|
| Personal information handled | The customer's accounting data, flowing both ways; the Xero identity of the person who connected it |
| Where | As Xero's own terms say (Xero is the customer's own provider) |
| Safeguard | Section 72(1)(d): the customer's instruction under its own Xero contract |
| Contract | Xero Developer Platform terms |
| What we use it for | Google Workspace mailboxes (support and the founders); Google Tag Manager and Google Analytics on the website, only after consent |
|---|---|
| Personal information handled | Email correspondence; website analytics identifiers |
| Where | Global |
| Safeguard | Section 72(1)(a): Google Workspace and Google Ads data processing terms; consent for analytics (section 72(1)(b)) |
| Contract | Google Cloud and Workspace data processing addendum |
Anthropic
| What we use it for | Language models that help us operate the service |
|---|---|
| Personal information handled | The content of support tickets and logs sent to a model |
| Where | United States |
| Safeguard | Section 72(1)(a): Anthropic's commercial terms and data processing addendum; under those terms what we send is not used to train models |
| Contract | Anthropic data processing addendum |
PostHog
| What we use it for | Product analytics inside the applications |
|---|---|
| Personal information handled | A user id, events, page views, device, IP address |
| Where | European Union (PostHog's EU cloud) |
| Safeguard | Section 72(1)(a): hosted in the EU, under the GDPR |
| Contract | PostHog data processing agreement |
Sentry
| What we use it for | Error reporting |
|---|---|
| Personal information handled | Request details, user id, IP address, error traces |
| Where | European Union (Sentry's EU region) |
| Safeguard | Section 72(1)(a): Sentry's data processing addendum |
| Contract | Sentry data processing addendum |
GitHub
| What we use it for | Source code, the automation that builds the service, issue tracking |
|---|---|
| Personal information handled | Contributors' names and email addresses. No customer data, by rule: secrets and data never enter the repository |
| Where | United States |
| Safeguard | Section 72(1)(a): GitHub's data processing agreement |
| Contract | GitHub data processing agreement |
2. Transfers outside South Africa
Section 72(1) of POPIA allows personal information to be sent to another country only on one of the grounds it lists. The safeguard line under each name says which ground we rely on. Section 6 of the privacy policy says the same in fewer words.
3. When this list changes
A new sub-processor is added to this page before it handles any personal information. If you are a customer, we email your account owners at least 30 days before, and you may object, as clause 5 of the data processing addendum sets out.
4. Questions
Write to support@finalops.co.za.