Skip to content
Back to Insights
A calm editorial illustration of a business owner checking a document before sharing it with an AI service, with a protected folder, discreet privacy shield and no legible personal data.

AI, Thought Through

Business Partner · 14 October 2026 · 5 min read

AI can help write a difficult email, summarise a document or explain a set of figures. The empty text box makes it feel as ordinary as typing a note to yourself, but submitting business information to an online service is a different kind of action. The convenience can obscure a question that ought to come first: what are you entitled to share?

The moment information leaves your own systems, another provider may process it. Its storage, retention, access and use for service improvement depend on its terms, configuration and your agreement with it. The useful rule is to share only what you are authorised to share, for a purpose you understand.

Begin with what is never needed

Passwords, one-time PINs, recovery answers and private access keys do not belong in ordinary AI prompts. Neither do online banking credentials, payment card details or anything that could give a stranger control over an account. An AI tool does not need your actual password to explain how password rules work, or your actual bank details to help draft a payment request.

The safer alternative is usually simple. Describe the problem, replace identifying or secret details with invented examples, and ask for the principle rather than access to the underlying account. If the task cannot proceed without credentials, it is probably a different task requiring an approved authentication process, not a chat prompt.

A document can also contain secrets less obvious than a password. An exported configuration file might expose an API key, a spreadsheet might contain account numbers, and a screenshot could show a recovery code. Read what you are about to share, not only what you intended to share.

Customer information remains your responsibility

A debtor ledger may include names, contact details, invoice references and payment histories. A complaint may reveal an address, personal circumstances or a conversation never intended for wider circulation. That material may be relevant to your question, but relevance alone does not establish permission to send it to another provider.

In South Africa, the Protection of Personal Information Act makes lawful processing and appropriate safeguards important responsibilities. Whether a particular disclosure is permitted depends on the information, purpose, legal basis and arrangements with those processing it. This is not solved by calling a service intelligent or secure without examining what those words mean in its terms.

Before uploading, establish three things: whether the person must be identifiable, whether this use is authorised, and what the provider will do with the record. Then check retention, human or subcontractor access, any training use, and how deletion or correction works. If you cannot get a sufficiently clear answer, pause the upload.

Removing a name may help, but it is not a guarantee of anonymity. A job title, distinctive event or small group of details can still identify someone. Share the minimum facts the task needs, not the whole file because it happens to be convenient.

Payroll and employee matters need a smaller circle

Payroll files can combine salary information with banking, identity and tax details. Personnel records may also include leave, disciplinary matters, medical information or private performance assessments. A general request to summarise costs rarely requires that entire bundle of information.

For a broad planning question, use roles, ranges or invented figures instead of identifiable employee records. If real records are essential, use a service expressly approved for that type of processing and limit the fields to the specific purpose. Restrict who can access the output as carefully as you restrict the input.

The same care applies to employee conversations. A transcript that seems harmless may contain a confidence shared for one purpose and not another. Anonymising names is useful only when the remaining details do not identify the person.

Contracts and correspondence carry other people's trust

Contracts, tenders and proposals often include negotiated terms, pricing, methods and intellectual property belonging to more than one party. A confidentiality obligation does not disappear because the third party receiving the material is software. Check the permission to disclose before using a tool to interpret a signed agreement.

You can often ask a valuable question without handing over the contract. For example, ask what a small-business owner should examine in a limitation-of-liability clause, then use qualified professional advice for the actual wording and consequences. Understanding a principle and disclosing an entire agreement are different choices.

Email chains and WhatsApp conversations deserve similar restraint. Remove names, signatures, contact details, account numbers and unrelated history, and retain only the passage necessary for the question. People do not automatically agree to a new audience simply because their words already appear in your inbox.

A practical public-tool test is whether disclosure of the prompt would cause harm, embarrassment or a breach of confidence. Stronger contractual safeguards may change what is appropriate, but they should be confirmed rather than assumed. Convenience is not permission.

Choose the service before sharing the information

Not every AI tool has the same purpose, terms or protections. A purpose-built service may operate under agreed confidentiality, access restrictions, retention limits and security controls; a general tool may have different settings or service arrangements. The important distinction is what can actually be verified, not the label on the product.

Ask the provider what information it needs, why it needs it, where it is processed, who may access it and what happens after the task ends. Establish whether it is used for model improvement, how you can export or delete it, and how incidents are handled. Revisit the answer when the service or terms change, because yesterday's permission is not automatically permission for every new use.

This is also a sensible moment to define an internal habit: decide which kinds of business information may be used with which approved services, and who can approve exceptions. That need not become a lengthy policy. A short, clear rule that employees can follow is more valuable than an elaborate document nobody reads.

The objective is not to avoid AI. It is to use it without turning a useful task into an undisclosed transfer of responsibility. AI should reduce what the owner has to carry, not create a risk the owner never agreed to take.

See your own Morning Brief

Send the aged debtors report your accounting system already produces and see who to chase first.

Try it with your report

Keep reading