No final-action approval needed.
Draft message, quote preview, calendar proposal, report, checklist, template draft, or plan.
Safety and approvals
LoopSuite can prepare the work. Approval protects the risky step.
Drafts, previews, plans, reports, and checklists are preparation. Sending, publishing, spending, deleting, booking, and changing records are final actions.
Boundaries
The approval line should be obvious to a non-technical owner.
Approval, saved authority, or a block.
Send, share, publish, delete, buy, spend, book, submit, or change customer, accounting, CRM, access, or account records.
Mac data stays Mac-local unless shared.
Raw local paths, bookmarks, screenshots, permission state, and logs stay local unless the user shares, stages, uploads, or syncs safe context.
Source reality
LoopSuite should say what it can use and what is missing.
Private account data needs a connection.
If Gmail, QuickBooks, Xero, Stripe, Shopify, Meta, Google Ads, Drive, or another service is not connected and authorized, LoopSuite should not pretend it can read or change it.
Stable facts are useful. Secrets are not memory.
Memory is for stable useful context. It should not store API keys, one-time codes, passwords, or payment details.
Trust model
Helpful does not have to mean reckless.
LoopSuite is built around drafts, visible work, source checks, and approvals before important external change.