# Memo for Counsel — Homebuilder Review

**To:** Counsel for Homebuilder Review (HBR)
**From:** HBR product / strategy team
**Re:** Legal posture pre-launch — review request
**Status:** v1 draft · pending counsel review
**Date:** May 2026

---

## What this is

HBR is a homeowner-facing platform that lets new homeowners document defects, file warranty claims, and rate homebuilders during the year-after-move-in window. Builders pay subscriptions for tiered access to data derived from those records. The principal commercial offering — Builder Tiers (S/M/L) plus a five-rung Data Access Ladder — sits inside the same UGC architecture that has supported Yelp, Glassdoor, and TripAdvisor for two decades.

This memo asks counsel to review the legal posture we have architected for. The relevant documents and the rationale behind them are at <https://staas.fund/hbr/trust/>. The four v1 drafts (ToS, Privacy, AUP, DMCA) live alongside this memo. We need your review before public launch.

## What we are asking counsel to confirm or correct

1. **The Section 230(c)(1) posture is correctly scoped.** Specifically, that the homeowner-authored framing of (a) photographs, (b) AI defect verdicts (after homeowner acceptance), (c) drafted warranty letters (template, edited and sent by homeowner from their own email), and (d) reputation-card metrics (derived from objective inputs) all qualify as user-provided content under § 230, not platform-provided content. The relevant carve-outs we have considered: *Roommates.com*, *Force v. Facebook*, *Gonzalez v. Google* (2023).

2. **The anti-SLAPP venue selection holds up.** Our draft Terms forum-select California for any dispute not covered by arbitration. We want counsel's view on whether CCP § 425.16 reliably attaches to platform speech of out-of-state plaintiffs, and whether a different venue (Texas TCPA, D.C., Nevada) would be preferable for first-amendment-shielded UGC defense.

3. **The AAA-arbitration + class-action waiver is enforceable as drafted.** Modeled on currently-enforced Yelp/Glassdoor language. We want confirmation that the 30-day opt-out, the small-claims and injunctive-relief carve-outs, and the consumer-arbitration rules selection are all defensible under recent Supreme Court guidance (*Lamps Plus*, *Viking River*).

4. **The drafted-letter feature does not constitute Unauthorized Practice of Law in the most-restrictive states.** Our architecture (template + homeowner edit + homeowner sends from own email + free of charge on the homeowner side + warranty correspondence rather than litigation document) is designed to be UPL-safe in CA, NY, TX, and FL. We want counsel's review of state-specific carve-outs we may have missed.

5. **The Data Access Ladder (Rungs 03–05) treats anonymized statistics correctly.** Specifically, that aggregation thresholds (k=10 builders, k=100 homes per cell), category-only vendor naming, and the published methodology constitute "non-personal information" under CCPA/CPRA and "non-personal data" under GDPR after transformation. Modeled on Glassdoor's industry-compensation report posture and AvidWarranty's cohort-trend product.

6. **The corporate posture is sufficient at this stage.** Delaware C-Corp, California forum, AAA arbitration, $2–5M E&O + Media Liability, 7-yr retention, registered DMCA agent. We want counsel's view on which of these are launch-blocking vs deferrable to Series A.

## Specific open questions

| # | Question | Why it matters |
|---|---|---|
| 1 | Does the AI verdict need a more explicit "the homeowner is the speaker" framing in the product UI, beyond what we have already (review-and-accept gate, override button, confidence-range display, model-version stamp)? | The biggest § 230 risk in the build is the classifier being recharacterized as HBR speech. |
| 2 | Do we need state-by-state UPL carve-outs in the drafted-letter feature, or is the architectural posture (template, homeowner edits, homeowner sends) sufficient for the most restrictive jurisdictions? | UPL is the second-biggest litigation risk after defamation. |
| 3 | What is the right SLA on builder factual-error flags before the platform incurs duty-of-care exposure? Our draft is 5 business days. | Sets the bar for Trust & Safety staffing. |
| 4 | Does the firsthand-experience verification (closing record, lease, utility bill) need to be a hard gate at sign-up, or can it be a flag-triggered review? | UX vs. liability tradeoff. |
| 5 | Does the Data Access Ladder Rung 04 (Industry Quarterly Report) need additional disclosures beyond methodology transparency to avoid being treated as a "report on a specific builder" if it correlates regional trends with vendor categories? | The vendor-category cuts are commercially valuable; we don't want to compromise them. |
| 6 | What is the most defensible Anti-SLAPP venue? CA is our default; counsel may have a stronger view. | Affects the entire forum-selection strategy. |
| 7 | What is the right E&O / Media Liability policy structure and limits at pre-revenue and at $1M ARR? | We need a quote to budget. |

## Documents to review

All v1 drafts. None are operative until counsel approves.

- **Terms of Service** — <https://staas.fund/hbr/trust/terms.html>
- **Privacy Policy** — <https://staas.fund/hbr/trust/privacy.html>
- **Acceptable Use Policy** — <https://staas.fund/hbr/trust/acceptable-use.html>
- **DMCA Procedure** — <https://staas.fund/hbr/trust/dmca.html>

## Architectural choices that flow from the legal posture

These are choices we have already made in the product, derived from the posture above. Flag any that would weaken the posture:

1. **Reputation cards display objective metrics only** — no 1–5 star score, no editorial summary. Response rate, resolution rate, time-to-acknowledge, documented defect rate.

2. **AI verdicts require homeowner acceptance before saving.** The "accept and save" button is the moment of authorship transfer; provenance stamps record this.

3. **Warranty letters are sent from the homeowner's email account,** not from an HBR address, and signed in the homeowner's name. HBR provides the template, not the sender identity.

4. **Builder response is free, structural, and always available** at every paid tier and the unpaid verified-builder tier.

5. **Paid tiers buy data access, not content control.** No builder paid tier conveys edit, suppression, or curation rights over user content tied to their license.

6. **Aggregation thresholds are documented and audit-checkable.** k≥10 builders, k≥100 homes per cell; cells under threshold are suppressed.

7. **Cross-border data transfer relies on SCCs** for EU users; EU representative to be designated before EU launch.

## What we need from counsel

1. **Confirm or correct** the posture above and the v1 drafts.
2. **Resolve the seven open questions.**
3. **Mark up the four document drafts** with redlines or proposed substitutions.
4. **Recommend a DMCA-agent registration timeline** and a designated entity for the registration.
5. **Provide an indicative E&O / Media Liability quote** or a referral to a specialty broker (Hiscox, Beazley, Coalition).
6. **Identify any state-specific filing or registration required** before we accept the first paying builder customer.

## Scope, timing, and budget

We anticipate three weeks for counsel review (the four documents + this memo + redlines). We are open to either (a) a fixed-fee package for the launch document set or (b) hourly billing under a not-to-exceed cap. The product is ready to launch on the marketing side; only counsel sign-off blocks moving the homeowner-side from `noindex` to public.

Please confirm scope, timeline, and budget. We're glad to do an intake call.

---

## Citations and source material

The legal posture relies on:

- **47 U.S.C. § 230(c)(1)** — interactive computer service immunity for user content
- **47 U.S.C. § 230(e)** — carve-outs (federal criminal, IP, ECPA, FOSTA-SESTA)
- **17 U.S.C. § 512** — DMCA safe harbor, notice and counter-notice procedure
- **Zeran v. America Online, Inc.,** 129 F.3d 327 (4th Cir. 1997)
- **Fair Housing Council v. Roommates.com, LLC,** 521 F.3d 1157 (9th Cir. 2008)
- **Force v. Facebook,** 934 F.3d 53 (2d Cir. 2019)
- **Gonzalez v. Google LLC,** 598 U.S. 617 (2023)
- **Twitter, Inc. v. Taamneh,** 598 U.S. 471 (2023)
- **Cal. Code Civ. Proc. § 425.16** — California Anti-SLAPP
- **Tex. Civ. Prac. & Rem. Code § 27** — Texas Citizens Participation Act
- **Uniform Public Expression Protection Act** (UPEPA, 2020) — model anti-SLAPP statute
- **AT&T Mobility LLC v. Concepcion,** 563 U.S. 333 (2011) — class-waiver arbitration enforceability
- **Lamps Plus, Inc. v. Varela,** 587 U.S. ___ (2019) — arbitration ambiguity resolution
- **Cal. Civ. Code § 1798.100 et seq.** — CCPA / CPRA
- **U.S. Copyright Office, DMCA Designated Agent Directory** (current registration guidance)
- **Levitt v. Yelp! Inc.,** 765 F.3d 1123 (9th Cir. 2014) — neutral moderation and pay-for-curation distinction

Citations were current as of May 2026. Counsel review will include verification against any post-revision case law.

---

**HBR / 04** — Memo for Counsel — Last revised May 2026

This memo is a working document, not a binding instruction or representation. Final operative language for all referenced documents will be set by counsel.