Operator (Data-Processing) Agreement

Last updated: 10 November 2026

Every company that uses FreightOps accepts this agreement together with our terms and conditions. It sets out how we process personal information on the company's behalf, as the Protection of Personal Information Act requires.

Purpose: the written contract POPIA s.20–21 requires between a Responsible Party (the client — e.g. TCT Freight) and an Operator (Digital Blast Media, the company that provides FreightOps) when the operator processes personal information on the responsible party’s behalf. It is signed by each client at onboarding, together with the FreightOps Service Agreement, of which it forms part (clause 11.2).


Parties

1. Definitions

Terms used here (“personal information”, “processing”, “data subject”, “responsible party”, “operator”, “Regulator”) have the meanings given in the Protection of Personal Information Act 4 of 2013 (“POPIA”).

2. Subject matter and roles

2.1The Client is the Responsible Party; FreightOps is the Operator.

2.2FreightOps processes personal information only on the documented instructions of the Client and only to provide the FreightOps service. This agreement, the Service Agreement and the Client’s use of the service’s features are those instructions.

2.3Nature of processing: collection, storage, and display of freight operational data, including driver GPS location captured on trip events, driver and staff account data, load/cost records, images of receipts and slips (fuel, toll, tyre and expense documents) uploaded by the Client’s staff or drivers, and the contact details of the Client’s own customers entered so that tracking links and delivery notifications can be sent to them. A receipt image may incidentally show a driver’s name or signature, an identity or passport number, or a vehicle registration, where the issuer printed it. Identity and passport numbers are unique identifiers under POPIA. FreightOps processes them only as part of the image: it does not read them, does not extract them into any field, and does not link them to information held by any other responsible party. Prior authorisation under POPIA s.57(1)(a) is therefore not required, because that section applies only where both a different purpose and an aim of linking are present. If FreightOps ever builds reconciliation against fuel-card, telematics or other third-party records, s.57 must be reassessed before that feature ships.

2.3A Images that must not be uploaded. The Client will instruct its staff and drivers not to upload medical, pharmacy, clinic or other images containing special personal information (POPIA s.26) or a child’s information. FreightOps deletes any such image it becomes aware of and does not submit it for automated reading.

2.3B Retention of images. Receipt and slip images are kept for as long as the underlying cost record is needed for the Client’s accounting and tax purposes, and are then deleted with that record under clause 7.

2.4Data subjects: the Client’s drivers and operational staff; the contact persons at the Client’s customers who receive tracking links or notification emails; the Client’s customers and suppliers that are companies or other juristic persons, whose information POPIA also protects; and, incidentally, any other person whose details appear on an uploaded receipt.

3. Operator’s obligations (POPIA s.20–21)

3.1Process personal information only for the purpose above and only per the Client’s instructions; not for FreightOps’ own purposes, except the billing described in clause 5.3.

3.2Treat all personal information as confidential.

3.3Maintain appropriate, reasonable technical and organisational security measures (POPIA s.19) — including tenant isolation (row-level security), encryption in transit, access controls, audit logging, rate limiting, and an encrypted nightly off-site backup whose key is held only by FreightOps.

3.4Notify the Client immediately (POPIA s.21(2)), and in any event within 24 hours, of having reasonable grounds to believe that personal information has been accessed or acquired by an unauthorised person or lost — stating what is known about the information affected, the data subjects concerned, the likely consequences and the steps taken, and updating the Client as more becomes known — so the Client can meet its own s.22 duties to notify the Regulator (through the Regulator’s eServices portal) and data subjects, which remain the Client’s.

3.5Assist the Client, so far as reasonably possible, in responding to data subject requests (access / correction / deletion / objection) and Regulator enquiries.

3.6On termination, delete or return the Client’s personal information per clause 7.

4. Driver privacy notice (adoption)

4.1FreightOps provides a standard driver privacy notice within the driver app. Each version of the notice carries a version number, shown in the app; version 1.3 is current at the date of this agreement.

4.2The Client adopts the standard FreightOps driver privacy notice as its own and confirms it is accurate for the Client’s use. The Client remains the Responsible Party accountable to its drivers for that notice, and will tell FreightOps if it uses the data for any purpose the notice does not describe.

4.3Drivers acknowledge the notice in-app before use; FreightOps retains a per-driver, per-version record of acknowledgement.

5. Sub-processors

5.1The Client authorises FreightOps to use the following sub-processors:

(a) Automated reading of receipt and slip images. When a user submits a receipt image for automated reading, the image is sent to Anthropic’s API, which returns the figures printed on it (amount, currency, date, place, litres, registration). The user sees the image beside the returned figures and confirms or corrects them before anything is saved. Under Anthropic’s commercial terms, inputs and outputs are not used to train its models; they are retained, if at all, only for a limited period (at most 30 days under its published policy at the date of this version) for safety and abuse monitoring, as set out in those terms and Anthropic’s data-processing addendum, which FreightOps has accepted.

(b) Building, maintaining and supporting the service. FreightOps uses Anthropic’s AI assistant to write and test the software and to investigate and fix problems. While doing so the assistant may read service data — account details, load and cost records, location records, receipt images and correspondence about the service — but only as far as the task in hand needs. It changes service data only as FreightOps directs, and it is not used to make any decision about a person. The assistant runs under Anthropic’s individual-account terms, with model training switched off in the account’s privacy settings, so this data is not used to train Anthropic’s models.

Anthropic processes both in the United States (clause 6.4).

5.2FreightOps remains responsible for its sub-processors’ compliance and will give the Client reasonable notice of any intended change. FreightOps uses a sub-processor only under written terms that oblige it to protect the personal information to a standard no lower than this agreement requires. If the Client objects to an intended change, it may end the Service Agreement under that agreement’s notice clause before the change takes effect.

5.3FreightOps’ own billing is outside this agreement. Billing the Client for the service — invoices, payments and, where the Client saves a card, the card payments made through FreightOps’ payment provider, Paystack — is processing FreightOps does for its own purposes as a responsible party, with Paystack as FreightOps’ own operator, under its privacy policy and the Service Agreement, not on the Client’s instructions. Paystack is therefore not a sub-processor under clause 5.1. The Client authorises FreightOps to use, for that billing, the email address of a user who chooses to save a card. Paystack receives that email address, the amounts charged and FreightOps’ reference for each and, where its rules require, the Client’s company name, address, telephone number and a description of the service; it collects card details itself, on its own page, and receives no other personal information from the service. For its own legal duties — such as fraud checks, sanctions screening and keeping transaction records — Paystack is responsible itself, under its own privacy policy.

6. Cross-border transfer (POPIA s.72)

6.1The Client acknowledges that personal information is stored and processed on Supabase infrastructure in the European Union (Ireland).

6.2The transfer relies on POPIA s.72(1)(a) — the recipient jurisdiction (the EU, under the GDPR) provides an adequate level of protection comparable to POPIA — supported by this agreement and Supabase’s own data-processing terms; and on s.72(1)(c) to the extent the processing is necessary for the operational/employment relationship.

6.3The EU-hosting fact is disclosed to drivers in the in-app privacy notice (clause 4).

6.4Data processed by Anthropic under clause 5.1 — receipt images sent for automated reading, and service data its AI assistant reads while FreightOps builds, maintains or supports the service — is transferred to Anthropic, PBC in the United States of America. The United States is not covered by the adequacy reasoning in 6.2. For these transfers FreightOps relies on POPIA s.72(1)(a) in its binding agreement limb. For automated reading, Anthropic’s commercial terms and data-processing addendum bind it to confidentiality, purpose limitation, security safeguards and onward-transfer restrictions substantially similar to the conditions for lawful processing under POPIA. For the AI assistant, the binding terms are Anthropic’s individual-account terms and privacy policy, with model training switched off; these are not a data-processing addendum. This is the only limb available for these flows: automated reading is optional, and the service could be supported without an AI assistant, so neither transfer is necessary for the performance of any contract.

6.5Two further flows leave the European Union.

(a) Notification and account emails are sent through Resend, a United States company, which retains the account records and delivery logs for those emails in the United States. Those emails carry names, email addresses, load references and places, never GPS records or receipt images. For this transfer FreightOps relies principally on s.72(1)(c) — the transfer is necessary to perform the contract between the data subject and the Client, or, where the recipient is a person at the Client’s customer, on s.72(1)(d), the transfer being necessary to perform a contract concluded in that person’s interest between the Client and a third party — supported by Resend’s data-processing terms under s.72(1)(a).

(b) The nightly backup is produced on a hosted build machine supplied by GitHub, in a region GitHub does not disclose, encrypted on that machine with a key only FreightOps holds, and then stored in the European Union. The data exists in unencrypted form on that machine for the few minutes of the run before it is encrypted. FreightOps relies on s.72(1)(a), the provider’s data-processing terms, together with that encryption. FreightOps is moving this job to compute in a named European region, after which this paragraph will name the country.

The Client’s authorisation of these flows is given under clause 2.2 as part of its documented instructions; it is not itself a s.72 ground, and nothing in this clause asks the Client to supply one.

6.6Apart from 6.1, 6.4 and 6.5, GPS locations, account data, load/cost records and receipt images are stored only on the infrastructure in 6.1. An image is sent to Anthropic for reading only when a user chooses to have it read; every other function of the service works without automated reading, and a user may type the figures in by hand instead. Service data read by the AI assistant under clause 5.1(b) is read, not stored elsewhere by FreightOps.

6.7Sub-processors named in clause 5.1 may use AI tools within their own services; their data-processing terms with FreightOps apply to that use as to any other.

7. Retention and deletion

7.1Personal information is retained only as long as needed for the operational purpose (see the in-app notice), or as law requires.

7.2On termination, FreightOps will, at the Client’s election made in writing within 30 days, return or delete the Client’s personal information; absent an election it will delete it within 90 days of termination, save where law requires retention. Copies held in the encrypted backup are removed within 35 days after deletion.

8. Audit

8.1FreightOps will make available, on reasonable request, the information needed to demonstrate compliance with this agreement.

8.2If that information does not reasonably satisfy the Client, the Client may, once in any 12 months and on at least 30 days’ written notice, have FreightOps’ compliance with this agreement audited by the Client or by an independent auditor bound by confidentiality, at the Client’s cost. The audit covers FreightOps’ own records and procedures; it does not extend to other clients’ data or to sub-processors’ facilities, for which FreightOps will provide the sub-processors’ own published security reports where available.

9. Term & termination

This agreement will be in place for the duration of the service relationship and will terminate once the relationship ends. Each party that wishes to end the relationship must do so by written notice to the other party; clauses 3.2 (confidentiality) and 7 (deletion) will survive the termination.

10. Information Officers

11. General

11.1Governing law and jurisdiction: the laws of the Republic of South Africa; the parties submit to the jurisdiction of the South African courts.

11.2Relationship to the Service Agreement. This agreement forms part of the FreightOps Service Agreement between the same parties. Where the two conflict on the processing of personal information, this agreement prevails; on all other matters the Service Agreement prevails. Terms defined in the Service Agreement carry the same meaning here unless stated otherwise.

11.3Variation. No variation of this agreement, including this clause, is of any force unless it is in writing and signed by both parties, “in writing” and “signed” having the meanings given in the Service Agreement — which include acceptance of a new version through the in-app acceptance screen by an authorised administrator of the Client.

11.4Entire agreement: this agreement, together with the Service Agreement, is the entire agreement between the parties on the processing of personal information, and supersedes any prior understanding on that subject.

11.5Severability: if any clause is unenforceable, the rest remains in force.

11.6No waiver: a failure to enforce a term is not a waiver of it.

11.7Notices: in writing to the email or address each party nominates.