Using AI with client files? Check the local/cloud boundary before you install more tools.
A practical readiness snapshot for solo professionals and small teams testing local dictation, local file search, and local email workflows on Mac. It focuses on data boundaries, permissions, rollback, and honest client-facing claims — not legal, medical, compliance, or security certification.
Representative fictional sample: Northstar Consulting
This is a fictional/composite example. It does not describe a real client, device, file set, compliance status, security posture, or commercial outcome.
The team wants local-first AI, but needs a written rule for which notes, email snippets, and files may leave the device.
Microphone, mail, contacts, and folder access should be separated by task. Avoid granting broad access before a workflow is proven.
Local indexes, transcripts, and generated drafts need plain deletion, backup, and export notes before daily use.
Safe wording: “designed to keep selected files local by default.” Unsafe wording: “secure/compliant AI for client files.”
Mac-only first version is manageable if it covers one role, one device profile, and one rollback path.
This is a workflow-readiness snapshot only. It does not certify privacy, security, legal compliance, medical compliance, or professional advice.
Mini-check returned to the buyer
Pricing and safe claims
Free: one workflow description, 3 boundary questions. A$149: 1-page workstation readiness snapshot. A$499: SOP pack with install-plan review, handoff checklist, and rollback notes.
Safe claim: “I will help you define a practical local/cloud boundary for AI workflows.” Unsafe claim: “I will make your AI workflow compliant, secure, or risk-free.”