Add TCPA compliance document

[niravcodes]

Description

Add TCPA compliance document

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Code cleanup / refactor

Related Issues

#410

Testing

• Added/updated unit tests
• Tested manually
• Tested with live SignalWire credentials (if applicable)

Checklist

• I have read the CONTRIBUTING guidelines
• My code follows the project's style guidelines
• I have added tests for my changes (if applicable)
• I have updated documentation (if applicable)
• All existing tests pass

Additional Notes

[github-actions]

🌿 Preview

https://signalwire-preview-docs-416.docs.buildwithfern.com/docs

---

View workflow run

[hey-august]

Looks great. I left some notes. In addition to my in-line comments:

• We should definitely ask @jonslomski for his review before this goes out. Never mind, Brian already had him edit the draft.
• There are a lot of dates, outbound links, and "as of X date" references, so this guide will drift quickly. I'd like to setup a system to audit docs like this on a recurring cadence. Perhaps we keep a config file list of docs that are particularly sensitive to drift, and a GitHub Action can raise issues to review them at a set frequency.

Additional, optional, style notes:

• Could use another pass to de-AI the language, lots of em dashes
• Whole paragraphs on single lines. Recommend breaking up lines for readability, and/or semantic line breaks. No end user impact of course so it's really a matter of preference.

[niravcodes]

@hey-august about the dates, I've opened #504. Listing the review-by dates for facts here for future reference. I can do this manually while we finalize a full system.

Review by	What to re-check	Why / trigger
July 31 2026	Colorado AI Act status; the "~95%" litigation stat	CO Act's delayed date (June 30 2026) has passed and it's being reworked (SB 25-189) — confirm the "Transparency variants" cell. Full-year 2025 TCPA-litigation numbers should now exist to replace the mid-2025 figure.
August 2 2026	EU AI Act Art. 50 disclosure	Transparency obligations take effect August 2 2026 — confirm the "parallel disclosure duties" line reflects an in-force rule.
December 1 2026	FCC AI-call rulemaking	Final rule expected late 2026 / early 2027 — update the "Looking ahead" row when it lands (AI-ID at call open, consent naming AI, definition scope). Re-check February 1 2027 if not yet issued.
January 15 2027	Revoke-all rule, 47 CFR § 64.1200(a)(10)	Set to take effect January 31 2027 after two delays, with a pending Further Notice that may narrow/delay it again — confirm the date and scope before it goes live.
October 1 2026, then quarterly	Bradford v. Sovereign Pest Control (5th Cir.)	Feb 2026 decision; watch for en banc, SCOTUS cert, a circuit split, or FCC response — any of these shifts the PEWC-vs-oral-consent framing and the Bradford Note.
October 1 2026, then quarterly	Lamb v. Mortgage One Funding (E.D. Mich.)	Active case filed Feb 2026 — watch for citable rulings (motion to dismiss, class cert) as the vendor-liability example develops.

Stable for now: FCC Feb 2024 AI-voice ruling, 47 U.S.C. § 227 damages, 8 a.m.–9 p.m. calling hours, TX SB 140 (eff. September 1 2025), TX TRAIGA (eff. January 1 2026), CA SB 1001 / AB 3030, FL written-consent rule.

[hey-august]

Looks great!