Skip to content
FinalOps

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 forHosting the website and the web applications, the edge network and the firewall
Personal information handledEverything a request carries: IP address, cookies, form fields, pages rendered with a customer's data; server logs
WhereGermany (Frankfurt) for the servers that run our code; a global edge network; the company is in the United States
SafeguardSection 72(1)(a): Vercel's data processing addendum with EU standard contractual clauses; our code runs in the EU
ContractVercel data processing addendum

Hetzner

What we use it forThe database, the background worker, file storage and backups
Personal information handledAll platform data at rest: accounts, customers' data, documents, backups
WhereGermany (Nuremberg)
SafeguardSection 72(1)(a): Germany applies the GDPR
ContractHetzner data processing agreement (Auftragsverarbeitungsvertrag)

Cloudflare

What we use it forDNS, and network security for the servers that are not on Vercel
Personal information handledIP addresses and request details in transit
WhereGlobal network
SafeguardSection 72(1)(a): Cloudflare's data processing addendum with standard contractual clauses
ContractCloudflare data processing addendum

Resend

What we use it forThe email the service sends: sign-in, invitations, invoices and notices
Personal information handledThe recipient's email address and name; the content of the mail (links, invoice numbers)
WhereUnited States
SafeguardSection 72(1)(a): Resend's data processing addendum; section 72(1)(c) for account mail
ContractResend data processing addendum

Paystack

What we use it forSubscription payments
Personal information handledBilling email, name, amount, payment references. Card details go to Paystack only, never to us
WhereNigeria and South Africa
SafeguardSection 72(1)(c): necessary for the subscription contract
ContractPaystack merchant terms

Xero

What we use it forThe accounting system a customer connects
Personal information handledThe customer's accounting data, flowing both ways; the Xero identity of the person who connected it
WhereAs Xero's own terms say (Xero is the customer's own provider)
SafeguardSection 72(1)(d): the customer's instruction under its own Xero contract
ContractXero Developer Platform terms

Google

What we use it forGoogle Workspace mailboxes (support and the founders); Google Tag Manager and Google Analytics on the website, only after consent
Personal information handledEmail correspondence; website analytics identifiers
WhereGlobal
SafeguardSection 72(1)(a): Google Workspace and Google Ads data processing terms; consent for analytics (section 72(1)(b))
ContractGoogle Cloud and Workspace data processing addendum

Anthropic

What we use it forLanguage models that help us operate the service
Personal information handledThe content of support tickets and logs sent to a model
WhereUnited States
SafeguardSection 72(1)(a): Anthropic's commercial terms and data processing addendum; under those terms what we send is not used to train models
ContractAnthropic data processing addendum

PostHog

What we use it forProduct analytics inside the applications
Personal information handledA user id, events, page views, device, IP address
WhereEuropean Union (PostHog's EU cloud)
SafeguardSection 72(1)(a): hosted in the EU, under the GDPR
ContractPostHog data processing agreement

Sentry

What we use it forError reporting
Personal information handledRequest details, user id, IP address, error traces
WhereEuropean Union (Sentry's EU region)
SafeguardSection 72(1)(a): Sentry's data processing addendum
ContractSentry data processing addendum

GitHub

What we use it forSource code, the automation that builds the service, issue tracking
Personal information handledContributors' names and email addresses. No customer data, by rule: secrets and data never enter the repository
WhereUnited States
SafeguardSection 72(1)(a): GitHub's data processing agreement
ContractGitHub 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.