| Name | CountPilot (Pty) Ltd |
|---|---|
| Legal status | a private company incorporated in South Africa |
| Registration number | 2026/604793/07 |
| Trading as | Tender Pack Engine |
| Physical address | Roodepoort, Johannesburg, South Africa |
| Postal address | Correspondence by email to admin@countpilot.co.za |
| Telephone | +27 81 209 0248 |
| Website | https://tpe.countpilot.co.za |
What the business does. We operate web-based software that helps small and medium South African businesses prepare responsive bids for public-sector tenders: storing their compliance documents and tracking expiry dates, reading published bid documents, checking a bid against what the document requires, filling MBD and SBD forms, and assembling an indexed submission pack.
| Information Officer | Zuko Nkonjane (head of the private body) |
|---|---|
| admin@countpilot.co.za | |
| Telephone | +27 81 209 0248 |
| Postal address | Correspondence by email to admin@countpilot.co.za |
| Physical address | Roodepoort, Johannesburg, South Africa |
| Registered with the Information Regulator | Registration in progress; the reference will be published here once issued. |
All requests under PAIA, and all requests, objections and complaints under POPIA, go to the Information Officer at the address above. No deputy information officer has been designated; the business is small enough that the head deals with these personally.
Section 10 of PAIA requires the Information Regulator to publish a guide, in each official language, explaining how to use the Act. It tells a requester in plain terms what their rights are, how to make a request to a public or a private body, and what to do if a request is refused.
The guide is available free of charge from the Information Regulator:
If you cannot obtain it from the Regulator, ask us and we will send you a copy.
No notice has been published in respect of this body under section 52(2) of PAIA. Nevertheless, the following are available to anyone, free, without a PAIA request:
Certain records are accessible in terms of other laws, on the terms those laws set, rather than through this manual:
Listing a category here does not mean access to it will be granted; some of it is protected by the grounds of refusal in clause 13, particularly records belonging to our customers.
| Subject | Categories of record |
|---|---|
| Company | Founding documents, CIPC registration, director and shareholder records, minutes and resolutions, licences, insurance policies. |
| Financial | Annual financial statements, ledgers, bank records, invoices, receipts, tax returns and assessments, payment gateway settlement records. |
| Customer accounts | Registration details, plan and subscription history, invoices, correspondence, support requests, usage and AI metering records. |
| Customer business profiles | Registered name, CIPC and CSD numbers, VAT number, B-BBEE level, CIDB grading, industry classification, contact details, and director details captured for bid forms. |
| Customer compliance documents | Documents uploaded to a compliance vault: certified identity copies, CSD reports, SARS tax compliance letters, B-BBEE certificates and affidavits, CIPC documents, municipal accounts, COIDA letters, insurance, CVs and company profiles. These belong to the customer. We hold them as an operator. |
| Tender workspaces | Public bid documents, filled forms, responsiveness checklists, submission packs, SHA-256 manifests and hash-chained audit logs. |
| Employees and contractors | Contracts, payroll, statutory deductions, leave, disciplinary records — to the extent any exist. |
| Suppliers | Contracts and correspondence with the hosting provider, the payment gateway, Anthropic PBC and other service providers; invoices from them. |
| Systems | Source code, configuration, server and security logs, backups, incident records. |
| Marketing | Website content, enquiry-form submissions, mailing list records. |
| Legal | Correspondence with advisers, records of disputes, records of any regulatory engagement. |
Set out in full in our Privacy Notice. In summary:
| Purpose of processing | Operating the service: storing and reading compliance documents, checking a bid for responsiveness, filling forms, building submission packs, tracking deadlines, matching opportunities, metering optional AI actions, billing, support and security. |
|---|---|
| Categories of data subjects | Customers and their users; directors, members and employees of customer businesses whose details appear in bid documents; suppliers and service providers; our own employees and contractors; people who send us enquiries. |
| Categories of personal information | Names, contact details, identity numbers and identity documents, company registration and tax numbers, banking details where entered on a bid form, B-BBEE status (which includes information about race — special personal information under section 26 of POPIA, processed on the section 31 justification), usage records, billing records, IP addresses and log data. |
| Recipients | The hosting provider, the payment gateway, the outbound email provider, Anthropic PBC, an ESD sponsor where a customer is on a cohort (outcome projections only), and professional advisers or a court where legally required. The full list, with what each receives, is in the Privacy Notice. |
| Planned transborder flows | Text sent to the Claude API operated by Anthropic PBC in the United States: public tender documents, and a small number of business profile facts. Compliance vault documents are never sent. The transfer is made under section 72 on the bases stated in the Privacy Notice. |
| Security measures | Per-account separation of stored documents resolved from the login session; TLS in transit; encryption at rest on the data volume and on off-server backups; salted password hashes; sign-in rate limiting and lockout; hash-chained audit records; access restricted to the Information Officer; written operator agreements with every recipient. |
There is no charge for a correction, deletion or objection. We respond within 30 days, and we will confirm in writing what we did.
You may:
If you cannot read or write, or have a disability that prevents you from completing the form, tell the Information Officer and we will take your request verbally and complete the form for you, then give you a copy.
PAIA requires or permits refusal in the following cases, among others:
Where part of a record may be refused, we grant access to the rest of it (section 28).
There is no internal appeal against a decision of a private body. Your remedies are:
We will say in our written decision which of these applies, and by when.
This manual is available free of charge:
If you need it in another format because of a disability, ask and we will provide it in a reasonable alternative form. The manual is reviewed at least once a year, and whenever the business changes in a way that affects it.
Details current at the date of this manual; check inforegulator.org.za for any change.
The Information Regulator (South Africa)
JD House, 27 Stiemens Street, Braamfontein, Johannesburg, 2001
PO Box 31533, Braamfontein, Johannesburg, 2017
General enquiries: enquiries@inforegulator.org.za
PAIA complaints: PAIAComplaints@inforegulator.org.za
POPIA complaints: POPIAComplaints@inforegulator.org.za