Section 10: Legal, IP & Compliance
1. Business Structure Recommendations
β Recommended: Delaware C-Corp
Rationale: RecipeRoots is pursuing $400K pre-seed funding with VC interest potential (genealogy acquisition targets like Ancestry). Delaware C-Corps offer investor-friendly structure with standardized governance, stock options for team (engineer hires), and favorable tax/liquidation preferences. Enables scalable equity for 14-month milestones. Avoids LLC tax complexities for multi-investor rounds. Formation protects personal assets amid data risks. Industry reports (e.g., Carta data) show 80%+ of VC-backed SaaS use Delaware C-Corps.
| Structure | Best For | Pros | Cons | Recommendation |
|---|---|---|---|---|
| Sole Proprietorship | Testing phase | Simple, cheap | Personal liability | Not recommended |
| LLC | Bootstrapped | Liability protection, tax flexibility | Less investor-friendly | If no funding |
| C-Corp (Delaware) | Venture-backed | VC-friendly, stock options | More complexity, double taxation | β Primary |
| S-Corp | Profitable small business | Tax advantages | Shareholder restrictions | Later stage |
- Formation Cost: $500-$1,500 (use Stripe Atlas/Clerky for $500)
- Annual Maintenance: $800/year (franchise tax $400+, agent $300, filings)
- Timeline: 1-2 weeks
Incorporate before funding close or MVP launch (Month 4 milestone) to sign investor docs, hire contractors.
2. Intellectual Property Strategy
| Asset | Status | Priority | Cost | Timeline |
|---|---|---|---|---|
| Product Name (RecipeRoots) | π΄ Not protected | High | $500-$1,500 | 8-12 months |
| Logo | π΄ Not protected | Medium | $500-$1,500 | 8-12 months |
| Tagline (e.g., "Culinary Family Trees") | π‘ Consider | Low | $500-$1,500 | 8-12 months |
| Domain (reciperoot.com) | β Assumed secured | Critical | $10-$50/year | Immediate |
Trademark Action Items:
- USPTO + state search (DIY: $50 via USPTO.gov)
- Secure .com/.app domains
- File intent-to-use app ($350/class DIY)
- Monitor via Trademarkia
Patent Considerations: Maybe (Provisional Recommended)
Potentially Patentable: AI photo-to-recipe extraction (handwritten OCR + semantic parsing), voice-to-structured recipe conversion. Novel for heritage preservation.
Strategy: File provisional patent ($2,000) pre-MVP (Month 4) for 12-month runway to full utility. Trade secrets for fine-tuned models/prompts (NDA-protected). Rationale: Defends vs. copycats in genealogy space; low cost vs. $15K full patent.
Trade Secrets: AI models, prompt templates, recipe standardization algos, user datasets. Protect via NDAs, repo access controls, inventor logs.
Copyright: Auto-protects app code, UI, cookbook templates. Add Β© notices; track OSS (React Native deps) in LICENSE.md.
3. Data Privacy & Protection
Family recipes/stories are highly personal (photos, audio, genealogy tags)βtreat as sensitive PII.
| Regulation | Applies? | Why | Key Requirements |
|---|---|---|---|
| GDPR | Maybe | EU expansion (Phase 3) | Consent, DPA, rights |
| CCPA/CPRA | Yes | CA users, monetizing data | Opt-out, disclosures |
| COPPA | No | No <13 users primary | N/A |
| HIPAA | No | No health data | N/A |
| SOC 2 | Later | Enterprise/genealogy partners | Security audit |
| PCI-DSS | Via Stripe | Subscriptions | Stripe handles |
Required Docs (Launch Critical):
- Privacy Policy: Detail recipe data, AI use (no training w/o consent), exports. Template: FreePrivacyPolicy.com ($0) + attorney review ($1,500).
- Terms of Service: Liability caps, IP grants. Same cost.
- Cookie Banner: For analytics (e.g., GA).
| Data Type | Collected? | Stored? | Shared? | Retention | Encryption |
|---|---|---|---|---|---|
| Yes | Yes | No | Deletion req | At rest/transit | |
| Recipes (text/img/audio/video) | Yes | Yes (archive-grade) | No (family only) | User-controlled | AES-256 |
| Payment | Via Stripe | No | Stripe | N/A | Stripe |
| Family tags/genealogy | Yes | Yes | Partners (consent) | User-controlled | At rest |
AI-Specific:
- Providers (e.g., AWS Transcribe, Google Vision): Confirm no user data training.
- Disclose AI in Policy: "AI aids extraction; human review available."
- Data residency: US-only initially.
4. Terms of Service Key Provisions & 5. Regulatory Compliance
Critical ToS Clauses:
- Limitation: Cap at 12x fees paid
- Indemnity: User for content
- IP: Retain app IP; user licenses input
- AUP: No illegal recipes/content
- Disclaimers: "AI not infallible; preserve at own risk"
- Payments: 30-day notice changes
- Arbitration: Delaware law
Regulations: FTC (truthful heritage claims), CAN-SPAM (newsletters), ADA (app accessibility). AI: EU AI Act low-risk; disclose AI gen content.
6. Contracts & Insurance
| Agreement | Purpose | Priority | Cost |
|---|---|---|---|
| IP Assignment | Own contractor work | Critical | $100 |
| Privacy Policy/ToS | Launch req | Critical | $1,500 review |
| Contractor NDA | ML engineer | High | $200 |
| DPA | Ancestry partners | Medium | Template |
| Insurance | Purpose | Cost/Year | Priority |
|---|---|---|---|
| Cyber Liability | Breaches (recipes) | $2,000-$4,000 | High |
| Professional (E&O) | AI errors | $1,500 | High |
| D&O | Funding protection | $3,000 | High |
8. Compliance Checklist & 9. Legal Budget
Pre-Launch
- β C-Corp formation
- β EIN/Bank
- β Privacy/ToS live
- β TM search
- β IP assignments
Launch/Post-Launch
- β Insurance (Cyber/E&O)
- β TM filing
- β Incident plan
- β SOC 2 prep
| Item | DIY | Attorney | Recommended ($30K Budget Fit) |
|---|---|---|---|
| Formation | $500 | $1,500 | $500 (Atlas) |
| Policy/ToS | $100 | $3,000 | $2,000 |
| TM/Patent Prov. | $400 | $3,000 | $2,500 |
| Year 1 Total | $1,500 | $12,000 | $7,000 |
Approach: Templates (Termly.io) + 5hr attorney ($2K). Fits $30K funding ask.
10. Legal Risks & Mitigations
| Risk | Description | Mitigation | Severity |
|---|---|---|---|
| #1 Data Breach | Exposed family stories | Encryption, cyber ins., plan | π΄ High |
| #2 AI Inaccuracy | Bad recipe extraction sued | Disclaimers, E&O, review opt | π‘ Medium |
| #3 TM Infringement | Name conflict | Search/file early | π‘ Medium |
| #4 Privacy Claims | CCPA violation | Policy compliance, audits | π’ Low |
Next Steps: Form entity Week 1, docs by Month 2, insurance pre-launch.