Idea or playbook

Keeping Your Business Safe with AI Agents

Level: Beginner · Path: Fundamentals

A plain-English safety checklist for small business owners: what to ask before you connect an AI agent to your email, files, or customers, and what the tools say they offer.

So you're about to give an AI agent access to your email, your files, or your customers. Should you be nervous? A little careful is good. Here's the thing: most of the risk comes down to a few simple choices you control.

Five questions to ask before you connect anything: First, what will it be able to see? List every app and folder it can reach. Less is better. Next, what will it be able to do? Reading is low risk. Sending, buying, and deleting are high risk. Then, where does my data go? Check whether the company uses your data to train its AI, and whether you can turn that off. After that, who else can use it? If you have a team, make sure only the right people can run each agent. And last, how will I know what it did? Make sure there's a history or log you can check.

Here's what some of the tools say on their own pages (checked Oct 28, 2026 or Oct 27, 2026):

  • Grok Bot: uses Cursor sign-in (SSO) and privacy mode, encrypts its cloud computer in transit and at rest, offers a training opt-out, and can send sensitive actions through Auto Review before they run.
  • Lindy: says your data is never sold or used to train models, and that actions that write or send can wait for your approval.
  • Dust: describes permissions that separate what agents can access from who can use them, plus audit logs. It says it's SOC 2 Type II certified.
  • Zapier: in AI by Zapier, you can require approval before running, set per tool.
  • Claude Agent SDK: lets builders choose which tools run on their own and which need approval.

A few habits that keep you safe:

  • Use a separate login for the agent where you can, so you can switch it off without changing your own password.
  • Never paste passwords, card numbers, or private customer data into a chat or instructions.
  • Start with read-only access, and add more only when you need it.
  • Keep approval on for anything that sends, spends, or deletes.
  • Check the history once a week, at least at first.
  • Remove access from tools you stop using.

Of course, we're not your lawyer, and every business has its own rules to follow, especially around customer data. But ultimately, you control the yes. Keep it that way.

Sources

Where each fact came from