# DRAFT — The Small Business Guide to Using AI Safely
**ACR Business IT & AI** | A division of Anywhere Computer Repair
**Subtitle:** Save time with AI without putting customer information at risk.
**Editorial draft — not final designed PDF.** Intended for approximately 10–12 illustrated pages, minimum 13-point body text, generous spacing, colorful icons, short paragraphs, examples, worksheets, and a friendly tone. Brand palette: logo blue, bright green, orange. No customer records or identifying details in illustrations.

---
## Page 1 — Cover
**The Small Business Guide to Using AI Safely**
Save time. Protect your customers. Stay in control.

A practical guide for Southwest Florida business owners, with examples, exercises, and a printable staff checklist.

**FREE RESOURCE** | ACR Business IT & AI

## Page 2 — AI can help. But use it wisely.
Imagine a busy office. Someone needs a polite email, a summary of a long document, or a spreadsheet formatted for accounting. AI may turn an hour-long chore into a few minutes. That is exciting—but the information you give an AI tool matters just as much as the answer you get.

**Three simple rules:**
1. Start with a task, not with confidential files.
2. Know what data is going into the tool and what protections apply.
3. Keep a person responsible for reviewing important results.

**TRY THIS:** Write down one repetitive task that does *not* require private customer information: ____________________

## Page 3 — ⚠ SHOCKER! The bank statement conversation
During an interview, I spoke with a financial professional who told me they had put client bank statements into an online AI service to convert the information into a file for their accounting software.

**My reaction: That is exactly the kind of workflow where privacy questions must come first.** Bank statements may include names, account details, balances, and transaction histories. Uploading them into an AI service can create exposure depending on the product, account, contract, retention settings, permissions, and client authorization.

This story does **not** establish that a breach occurred or that the professional violated a particular rule. It illustrates why a useful AI workflow needs a privacy check *before* documents are uploaded.

**A better first question:** “Can we transform this file with a local spreadsheet tool, approved accounting integration, or private processing workflow instead?” Sometimes AI is not necessary at all.

**DISCUSS:** What kinds of files would your team be uncomfortable sending to an outside company? ____________________

## Page 4 — The stoplight test: What can I share?
🟢 **GREEN — Usually safer:** Public marketing text, fictional examples, generic job descriptions, blank templates, and invented sample data.

🟡 **YELLOW — Check first:** Internal procedures, nonpublic prices, vendor details, staff schedules, business forecasts, and anything covered by confidentiality agreements.

🔴 **RED — Do not paste into unapproved AI:** Client bank statements, passwords, Social Security numbers, medical records, tax returns, full customer lists, account credentials, confidential legal material, or private financial records.

**Remember:** A business AI account is not automatically permission to upload every sensitive document. Review the provider's actual terms, settings, and your obligations.

**WORKSHEET:** List three kinds of information your business handles, then label each GREEN, YELLOW, or RED.
1. __________ / ______
2. __________ / ______
3. __________ / ______

## Page 5 — Redaction: Take out what identifies someone
Redaction means removing or replacing information that identifies a person or business. It can lower risk, but it is not a magic privacy shield.

**Unsafe example:** “Write a collection reminder for Jane Smith at 145 Palm Street, account 44781, who owes $1,842.32 for invoice 00914.”

**Safer example:** “Write a polite payment reminder for a customer with an overdue invoice. Use placeholders [CUSTOMER], [AMOUNT], [INVOICE], and [DUE DATE].”

**Then:** Fill in the real details yourself in your approved email or CRM system—not in the public AI prompt.

**WATCH OUT:** A combination of job dates, unusual amounts, locations, and circumstances can still identify someone even after you remove their name.

## Page 6 — A practical redaction checklist
Before submitting a prompt, check for:
- Names, initials, photographs, signatures, addresses, email addresses, and phone numbers.
- Account numbers, invoice numbers, customer IDs, bank routing details, and login credentials.
- Unique dates, unusual transactions, location clues, and document metadata.
- Hidden spreadsheet tabs, PDF comments, tracked changes, filenames, and image text.

**Important:** Merely drawing a black rectangle over a PDF or screenshot may not remove the underlying text. Use a real redaction tool, export a clean copy, and verify the sensitive material cannot be recovered.

**PRACTICE:** Rewrite this unsafe request using placeholders: “Summarize the complaint from customer Maria Lopez at maria@example.com about her order #87234.”

Your safer prompt: ____________________________________________

## Page 7 — Five ways to use AI without client secrets
**1. Draft a first version of an email:** Ask for a friendly appointment reminder with placeholders.
**2. Brainstorm marketing ideas:** Ask for ten educational post topics for your industry.
**3. Explain a concept:** Ask for a plain-English explanation of a business term.
**4. Create a checklist:** Ask for a generic opening or closing procedure for a small office.
**5. Improve a process:** Describe a fictional version of a repetitive workflow and ask where steps could be simplified.

**TRY THIS PROMPT:** “I run a small [TYPE OF BUSINESS]. Suggest five ways to reduce repetitive office work without using real customer data. Explain each in plain English.”

## Page 8 — Know the three broad ways to run AI
**Business cloud AI:** AI hosted by an outside provider, with business-oriented administrative and contractual protections. Review specific terms and settings.

**Filtered cloud AI:** A workflow removes or substitutes sensitive information before sending a task to an outside provider. This requires careful engineering and testing; redaction can miss context.

**Private/local AI:** Models run on computers under the business's control. This can reduce exposure to external AI providers, but network connections, logs, backups, software updates, and connected tools still need security review.

**KEY IDEA:** “Private” is a design and operations question—not just a label on a product.

## Page 9 — Keep a human in charge
AI can make mistakes, invent details, or misunderstand instructions. Never allow an AI-generated result to become an unchecked commitment.

**Require human approval before:** Sending money; signing contracts; making promises to customers; hiring or firing; changing security settings; or giving medical, legal, or tax advice.

**WORKSHEET:** Pick one task your business might automate.
Task: __________
What can AI draft or prepare? __________
What must a person check? __________
Who approves the final action? __________

## Page 10 — Your one-page staff AI safety checklist
☐ We know which AI tools and accounts are approved.
☐ We do not paste client records or passwords into unapproved AI tools.
☐ We use fictional examples or placeholders whenever possible.
☐ We review documents for hidden information before sharing.
☐ We check provider privacy terms, settings, and retention rules.
☐ We verify AI output before using or sending it.
☐ We ask a supervisor when a request involves confidential information.
☐ We report mistakes promptly so they can be contained.

**Team discussion:** Who decides whether a new AI tool is approved? ____________________

## Page 11 — Find your first safe AI opportunity
**AI Opportunity Worksheet**
1. What task takes too much time each week? ____________________
2. How often do you do it? ____________________
3. Roughly how many minutes does it take? ____________________
4. Does it involve customer or employee information? ____________________
5. Could the task be demonstrated with fictional data? ____________________
6. What would a successful result look like? ____________________
7. Who would review the output? ____________________

**Small wins count.** The best first project is often a narrow, repetitive task with a clear result and limited data exposure.

## Page 12 — Your next step
**You do not need to choose between useful AI and responsible data handling.** Start with one practical task, clear rules, and a person in control.

**Want help choosing a safe first AI project?** Request a no-obligation business consultation with **ACR Business IT & AI**, a division of Anywhere Computer Repair.

**Call:** 239-287-2430
**Website:** anywherecomputerrepair.net (planned)
**Serving businesses and nonprofit organizations across Southwest Florida.**

*Educational information only. Not legal, financial, cybersecurity-certification, or compliance advice. Specific data-handling requirements depend on your industry, contracts, and applicable laws.*

---
## Editorial and design notes (not part of the final guide)
- Confirm the exact wording of the financial-professional anecdote with the business owner; do not identify the professional or claim a breach.
- Use a visually striking orange ⚠ SHOCKER callout on page 3; keep tone educational rather than shaming.
- Use logo-derived colors (blue/green/orange), friendly icons, checkboxes, ample white space, 13-point minimum body text, and short paragraphs.
- Include an illustrated redaction before/after and editable worksheet fields in the designed PDF.
- Validate any provider-specific privacy statements and current terms before publication.
- The guide is the free lead magnet; do not pitch the intrusive AI Safety Check as a primary offer.
- Email collection: deliver guide immediately; separate optional consent for future marketing; integrate with SuiteCRM.
