Terms of Service Analysis Report Format

When writing the analysis to Terms of Service Analysis Report, use this plain-language markdown structure. The goal is to make complex legal terms understandable to regular users.

# ToS Analysis: [Service Name]

**Reviewed:** [current date]
**Document Type:** [Terms of Service / Terms & Conditions / EULA / Privacy Policy]
**Verdict:** ✅ Fair Terms / ⚠️ Proceed with Caution / 🚨 Significant Concerns

---

## The Bottom Line

[2-3 sentences in plain language: What are you actually agreeing to? Is this standard or concerning?]

---

## What You're Agreeing To

### Your Data
[Plain-language explanation: What data is collected? How is it used? Can you delete it? Is it shared or sold?]

### Your Content
[Plain-language explanation: What happens to things you upload or create? Who owns it? What can they do with it?]

### Your Money
[Plain-language explanation: How does billing work? Auto-renewal? Refunds? Hidden fees?]

### Your Rights
[Plain-language explanation: Can you sue? Class actions? Where are disputes handled?]

---

## Green Flags Found

[List user-friendly terms in plain language]

---

## Yellow Flags Found

[List concerning items with plain-language explanation of what they mean]
[If none found, state "No yellow flags identified."]

---

## Red Flags Found

[List serious concerns with plain-language explanation of real-world impact]
[If none found, state "No red flags identified."]

---

## The Fine Print That Matters

[Quote or summarize 2-3 specific clauses that are most important, with plain-language translation]

---

## Verdict

**Agree** / **Agree but be aware** / **Think twice** / **Avoid if possible**

[Clear recommendation with rationale in everyday language]

Keep language accessible—avoid legalese. Explain impact in real terms (e.g., "This means they can use your photos in ads without paying you" rather than "perpetual sublicensable license").