Privacy Policy
Last updated: 10 November 2026 · Version 1.10
This policy explains how Digital Blast Media (Pty) Ltd, the company that provides FreightOps ("we", "us"), handles personal information on this website (freightops.co.za) and in the FreightOps application (app.freightops.co.za and the FreightOps driver app), in line with the Protection of Personal Information Act 4 of 2013 ("POPIA").
1. Who we are
Digital Blast Media (Pty) Ltd (registration number 2016/387590/07), a private company registered in South Africa. FreightOps is our product. Our Information Officer is registered with the Information Regulator (registration number 2026-061664). Contact: sales@digitalblastmedia.co.za · 074 957 5418. Address: 39 Tuscani Lofts, 43 Van Tonder Road, Edenglen, 1609, South Africa.
2. What we collect, and why
- Website contact form: your name, company name and phone number, and, if you give them, your email address, fleet size and message — used only to respond to your enquiry. Cloudflare checks that the form was sent by a person and not a bot, and Resend delivers it to us by email.
- FreightOps app accounts: name, email address, cell number, and role — used to provide login access and operate the service.
- Billing and card payments: the invoices and payments of each client company. If a client company pays us by card, the card is entered on the payment page of Paystack, our payment provider — we never see or store the full card number. We keep the card's brand, last four digits, expiry date and issuing bank, so the company can see which card is saved, and Paystack's reference for it, so that we can charge the company's monthly invoice to it; those card details come to us from Paystack. Paystack receives the email address of the person who saved the card, the amounts we charge and, where its rules require, the company's name, address and telephone number. Saving a card is voluntary: without one, the company pays by EFT. For this information we are the responsible party, and we use it only to bill the company.
- Operational data: loads, costs, vehicles, and related records entered by our client companies. This data belongs to the client.
- Client companies' customer contacts: the name, email address and phone number of a contact person at a client company's own customer, entered by the client so that a tracking link or a delivery notification can be sent to that person. The client company is responsible for having the right to enter it.
- Driver location: the driver app captures GPS coordinates when a driver logs a trip event. Drivers are shown a dedicated privacy notice inside the app and must acknowledge it before first use.
- Receipts and slips: photos of fuel, toll, tyre and expense receipts uploaded by our client companies' staff or drivers, so that the cost can be recorded against a load. A receipt sometimes shows a driver's name, an ID or passport number, or a vehicle registration where the garage or border post printed it. When a user asks for a receipt to be read automatically, the photo is sent to an automated reading service (Anthropic — see sections 4 and 5) which returns the figures printed on it; the user checks those figures against the photo before anything is saved. Reading is optional and every figure can be typed in by hand.
3. Cookies and browser storage
We do not use tracking cookies — in fact, we set no cookies at all. There are no analytics, advertising, or social-media trackers on this website or in the FreightOps dashboard.
- Logging in to the FreightOps dashboard stores a session token in your browser's local storage. This is strictly necessary to keep you signed in and is removed on logout. It is not used to track you.
- This website loads the Inter typeface from Google Fonts; your browser's request to Google discloses your IP address to Google.
- The home page loads Cloudflare Turnstile, the spam check on the contact form. It reads technical details from your browser, such as your IP address and browser type, only to tell people from bots; Cloudflare does not use them for advertising. No other third-party resources are loaded.
If we ever introduce analytics or marketing tools that use cookies, we will ask for your consent first.
4. Where your data is stored
FreightOps data is hosted on Supabase in the European Union (Ireland, AWS eu-west-1). This is a transfer of personal information outside South Africa as contemplated by section 72 of POPIA. We rely on section 72(1)(a): the recipient is subject to the GDPR, which imposes obligations substantially similar to (and in many respects stricter than) POPIA, and to our data-processing terms with Supabase. This is supported by the operator agreements we sign with each client.
Every night we copy the database and uploaded files to a second location so that the service can be rebuilt if Supabase fails. That copy is encrypted before it is stored, with a key only we hold, and kept in Cloudflare storage in the European Union. The copy is made by a job that runs on GitHub's hosted computers, whose location GitHub does not publish; the data is encrypted on that computer in the same run and is not kept there.
Application error reports (technical diagnostics, not operational data) are processed by Sentry in the EU (Germany), configured not to send personal information by default.
Emails we send — password resets, tracking links, delivery notifications, and invoices and payment notices to client companies — go through Resend, a United States company. Those emails carry names, email addresses, load references and invoice amounts, never location records or receipt photos. Resend keeps its account records and email logs in the United States. For this transfer we rely on Resend's data-processing terms under section 72(1)(a) of POPIA.
Our own accounting records — each client company's name, its contact people, and its invoices and payments — are kept in QuickBooks, run by Intuit, a United States company, outside South Africa. For this transfer we rely on section 72(1)(a) of POPIA and Intuit's data-processing terms. Our email, including what client companies send us to set up their accounts, is hosted by HostAfrica, a South African hosting company.
Card payments are processed for us by Paystack South Africa (Pty) Ltd, a Stripe company licensed in South Africa as a third-party payment provider. Paystack collects the card details on its own payment page and processes our charges on our behalf, as our operator, under a data-processing agreement with us; for its own legal duties — fraud checks, sanctions screening, and keeping transaction records for at least five years — Paystack is responsible itself, under its own privacy policy. Card payments go through South African banks; Paystack keeps its records on Amazon Web Services servers in Ireland, in the European Union. Some of Paystack's own service providers and group companies are elsewhere, including the United States and the United Kingdom (its published list). For these transfers we rely on section 72(1)(a): the recipient is subject to the GDPR and to Paystack's data-processing agreement with us, which protects information about companies as well as people and binds Paystack to impose the same obligations on its own service providers. Like any payment information, it may be disclosed where the law requires — to a bank, a card network, a regulator or the police. Paystack never receives operational data, location records or receipt photos.
The place names typed on a load (for example a depot or a border post) are sent to Google's geocoding service to find their map coordinates. Place names are not personal information.
We use AI services from Anthropic, PBC, in the United States, in two ways. First, receipt photos a user chooses to have read automatically are sent to Anthropic, which returns the figures printed on them. Second, we use Anthropic's AI assistant to build, maintain and support FreightOps: while we investigate or fix a problem, it may read the records involved — account details, loads and costs, location records, receipt photos and correspondence about the service — but only as far as that task needs. It is not used to make decisions about anyone. This is a second transfer outside South Africa under section 72 of POPIA. The United States does not have a general adequacy standing like the EU, so we rely on section 72(1)(a)'s binding agreement limb: Anthropic's terms and data-processing addendum bind it to confidentiality, purpose limitation and security safeguards substantially similar to POPIA's conditions — for receipt reading, its commercial terms and data-processing addendum; for the assistant, its individual-account terms and privacy policy. Anthropic does not use our data to train its models: the commercial terms forbid it, and for the assistant model training is switched off in our account's settings. Anthropic keeps data only for a limited period for safety monitoring.
Some of our service providers also use AI within their own services, under their own terms with us. For example, Paystack uses OpenAI and Langfuse for search and data-analysis features in its merchant dashboard.
5. Service providers we use
- Supabase — database, authentication, and file storage (EU/Ireland)
- Cloudflare — hosting for this website and the spam check on its contact form (Cloudflare's worldwide network), and encrypted off-site backup storage (EU)
- GitHub — runs the nightly backup job (location not published; data encrypted in the same run)
- Resend — transactional emails (password resets, tracking links, delivery notifications, invoices and payment notices) from noreply@freightops.co.za, and delivery of this website's contact form to us (United States)
- Sentry — application error monitoring (EU/Germany)
- Google Maps Geocoding — place names to map coordinates
- Anthropic — AI services: automated reading of receipt photos, and the AI assistant we use to build and support FreightOps (United States); does not use our data to train its models
- Netlify — hosting for the app
- Paystack — card payments, for client companies that pay us by card (records in Ireland; some of its providers in the US and UK, including OpenAI for AI features in its dashboard)
- QuickBooks (Intuit) — our own accounting: client companies' invoices and payments (United States company)
- HostAfrica — our email, sales@digitalblastmedia.co.za (South African hosting company)
We do not sell personal information, and we do not use it for advertising.
6. Your rights
Under POPIA you may:
- ask what personal information we hold about you (access);
- ask us to correct or delete it;
- object to processing;
- complain to the Information Regulator of South Africa: POPIAComplaints@inforegulator.org.za, enquiries@inforegulator.org.za, 010 023 5200, Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191.
To exercise any of these rights, contact our Information Officer, Revendran Pillay, at sales@digitalblastmedia.co.za. If your request concerns data processed on behalf of one of our client companies (for example, driver location data), we will assist and refer you to that company, which is the responsible party for that data. Drivers who use the FreightOps Driver app will find the steps for asking to delete their data at freightops.co.za/delete-data.
7. How long we keep it
Operational data is kept for as long as the client company's account is active. When an account ends, the client may ask for an export or deletion within 30 days; if they do not, we delete the data within 90 days. Copies in our encrypted backups are removed within 35 days after that. Invoices and payment records are kept for as long as company and tax law require: the current financial year and the seven before it, and longer while a tax return for that period is outstanding or a SARS audit, objection or appeal is open. On those records we keep only a card's brand and last four digits. When a card is removed, we ask Paystack to cancel our permission to charge it and delete its expiry date, bank and Paystack's reference for it; a removed card is never charged again. Website contact-form messages are kept only as long as needed to respond.
8. Changes to this policy
We will update this page when our practices change and revise the "Last updated" date and version above.