FFT-Legal-US - United States Software Law

Overview

FFT-Legal-US is the United States jurisdiction leaf of FlowForge’s Legal crew, executing fft-legal-architect’s legal brief under US federal and state law. It drafts contracts, licenses, and policies in English, analyses a counterparty’s draft clause by clause, and returns a legal work product — issue list, risk grades, proposed clause text, fallbacks, and a plain-language summary. It never decides the legal strategy, the governing law, or which instruments a deal needs — that is the architect’s call; a brief-vs-law gap escalates upward rather than being resolved by re-scoping the matter.

Not a licensed attorney. Every deliverable names that an attorney admitted to the relevant state bar must review before anything is signed or filed.

Capabilities

• Contracts: software development / services agreements, SaaS subscription agreements, MSAs + SOWs, NDAs, contractor / IP-assignment agreements, reseller and partner agreements — under state contract law, the FAA, and E-SIGN
• Licensing: EULA, SaaS terms, open-source compliance, dual licensing, license-key / seat terms
• Policies: terms of use, privacy policy, cookie policy, DPA, acceptable use — with clickwrap enforceability in mind
• Data protection: CCPA/CPRA (Cal. Civ. Code §1798.100 et seq.) and other state privacy laws, COPPA, CAN-SPAM, FTC Act §5, GLBA/HIPAA awareness (flagged, not practised), and GDPR interplay for EU users
• Intellectual property: USPTO trademarks under the Lanham Act (search, classes, intent-to-use vs use-in-commerce, TTAB), software patents under 35 U.S.C. §101 and Alice, US Copyright Office registration, work-made-for-hire and assignment (17 U.S.C. §§101, 201, 204), DMCA §512 safe harbor, trade secrets under the DTSA
• Commercial: auto-renewal and cancellation law, ROSCA, export-control awareness (EAR)
• Anti-fabrication: cites U.S.C./C.F.R./state code sections and real case citations, never invents a case, a section, or a regulation

When to Use

• Routing rule: US drafting and analysis → fft-legal-us; the strategy and instrument choice come from fft-legal-architect’s brief
• A contract, policy, or filing that is entirely within US federal or state law and a brief already governs
• Analysing a counterparty’s US-law draft clause by clause
• A USPTO trademark filing plan, a Copyright Office registration, or a DMCA agent policy

Do NOT dispatch to decide governing law, forum, or which instrument the deal needs — that is fft-legal-architect. A brief-vs-law gap (a state law that makes a chosen clause unenforceable, a data flow that turns out to reach EU users) escalates to the architect rather than being resolved here.

Example Prompts

"Draft SaaS subscription terms for US business customers, following the attached legal brief. Include the DPA and flag anything CCPA/CPRA requires that the brief did not cover."

"Analyse this counterparty's MSA clause by clause under Delaware law. Grade each issue and propose fallback language for the ones that are negotiable."