Right now, someone on your team is pasting a customer contract into ChatGPT to summarize it. Someone else is asking it to rewrite a sales email that contains your pricing structure. They are not being reckless. They are being productive, and the tool is genuinely useful. The problem is that you do not have a company ai usage policy, so nobody knows where the line is.
I have watched this play out inside several Indonesian SMEs over the past few months. The instinct from management is usually to ban the tools outright. That is the worst option. A ban does not stop usage, it just moves it to personal phones and private accounts where you have zero visibility. The Samsung engineers who leaked internal source code into ChatGPT earlier this year did not do it because there was no ban. They did it because the tool solved their immediate problem faster than any internal process.
So the real job is not prevention. It is drawing a clear, boring, one-page line that people can actually follow. Let me give you the skeleton I hand to clients.
Why a ban backfires
When you forbid a useful tool, three things happen. Usage goes underground, so you lose the ability to guide it. Your best people, the ones who experiment, feel treated like children. And you fall behind competitors who are learning to use the same tools well.
A company ai usage policy is not about control for its own sake. It is about making the safe path the easy path. If staff know exactly what is fine and what is forbidden, they stop guessing, and guessing is where leaks happen.
The framing I use with owners is simple. You are not policing intelligence, you are protecting data. Those are different jobs. Nobody argues that a warehouse should have no rules about what leaves the building. An AI policy is the same idea applied to information.
The one-page policy skeleton
You do not need a legal document. You need one page that a new hire can read in three minutes. Structure it in three buckets.
Allowed without asking. These are low-risk, high-value uses. Drafting and editing general text. Brainstorming ideas. Summarizing public documents. Writing code that touches no proprietary logic. Explaining concepts. Translating marketing copy. Anything where the input contains no confidential data and the output gets reviewed by a human before it ships.
Forbidden, no exceptions. This is the bucket that prevents the Samsung situation. Never paste in the following:
- Customer personal data (names, ID numbers, phone numbers, addresses)
- Financial records, pricing sheets, or internal margins
- Source code from private repositories
- Contracts, legal documents, or anything under an NDA
- Employee records and payroll
- Passwords, API keys, or access credentials
Gray area, ask first. Some cases sit between the two. A marketing draft that mentions an unreleased product. A process document that reveals how your operations work. For these, the rule is one sentence: when in doubt, ask your manager before pasting. Name a specific person who owns the decision, so "ask first" does not become "ask nobody."
Make the safe path the easy path
A policy on paper changes nothing. What changes behavior is giving people a sanctioned way to do the thing they want to do.
If your team needs to summarize customer contracts, that is a signal, not a violation. It means there is real value there. The right response is to find a tool with proper data handling, or to teach people how to anonymize the input first. Strip the names, replace the numbers with placeholders, then paste. The AI still does its job and nothing sensitive leaves the building.
This is also where a little training pays off fast. A thirty-minute session showing your team how to get better results, and how to spot when they are about to paste something they should not, does more than any signed document. People follow rules they understand and ignore rules that feel arbitrary.
The same discipline that protects your data also builds your capability. Treating information carefully is the foundation of using it well, which is exactly the mindset behind Your Business Data Is an Asset. Start Collecting It Now.
Review it, do not freeze it
The tools are changing every month. A policy written today will look dated by year end. Build in a review, once a quarter is enough for most SMEs. Ask three questions each time:
- What new tools has the team started using since last quarter?
- Has anyone hit a gray-area case we should now make explicit?
- Are there approved tools that handle data safely enough to move a forbidden use into the allowed bucket?
Keep the policy in a place people actually see it, not buried in a shared drive nobody opens. Pin it in your team chat. Make it part of onboarding. Review it out loud in a meeting once in a while so it stays alive.
If you want the AI to genuinely help your business rather than just individual staff, the next step is giving it your own information to work from safely, which I cover in RAG Explained: AI That Actually Knows Your Business.
The practical takeaway
Your staff are already using these tools. That decision has been made for you. The only open question is whether they do it inside a clear boundary or in the dark.
Write the one page this week. Three buckets: allowed, forbidden, ask first. Name the person who owns the gray-area calls. Do a thirty-minute training so people understand the why. Review it every quarter. That is a company ai usage policy that actually protects you, and it took an afternoon, not a law firm.
If you would rather have someone map your data risks and set this up alongside your broader tech decisions, that is the kind of work I take on with selected partners. Start with the one page regardless. Underground usage is the risk you cannot see, and it is already happening.