Legal
Research and compliance notes for running AI-powered services at ChurchWiseAI. Everything here is a reference document for a solo founder, not legal advice from a lawyer. When a real decision is on the line — bringing a new state online, answering a regulator, drafting terms — consult an actual attorney.
Current docs
| File | Covers |
|---|---|
ai-disclosure-regulations-2026-03.md | AI disclosure requirements across US states + Canadian provinces as of March 2026. Caller-facing "you're speaking with an AI" disclosure rules, bot-law compliance, recording-consent patterns. |
Related compliance surfaces
Legal research on this side ties into operational patterns enforced elsewhere:
- CASL/CAN-SPAM — covered in outreach campaigns; see
../processes/outreach-campaign-send.mdand ADR../decisions/2026-04-09-casl-can-spam-footer.md. - HIPAA / pastoral confidentiality — the HEAR protocol is intentionally a caring bridge, not a counseling surface. See
memory/project_caring_bridge_philosophy.mdand the crisis-call journey. - Terms of Service / Privacy Policy — derived from
knowledge/data/policies.yamlinto the live pages at churchwiseai.com/terms and /privacy. Source of truth is the YAML, not the page. - Stripe billing policy — refund rules, cancellation UX, non-refundable setup fees. See
../data/policies.yamland../runbooks/customer-ops/refund.md.
When to add a doc here
- New regulatory regime (GDPR, new state AI law, new province rule)
- Disclosure requirement that affects voice or chatbot copy
- Contract-level obligation (e.g., "retain call logs 90 days")
- DPIA / risk assessment that needs to persist beyond one session
Date-stamp the filename (YYYY-MM-<topic>.md) so future-you can see how old the research is. Regulations move; notes from 2026 should not silently govern a 2027 decision.