leeworks-agents/api-company
5
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

[Phase 6] Write legal docs: Terms of Service, Privacy Policy, Acceptable Use Policy #40

New Issue
Closed
opened 2026-05-26 05:22:32 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-05-26 05:22:32 +00:00
Owner
Copy Link
Copy Source

Roadmap reference

Phase 6 — Pre-launch: docs/legal/terms-of-service.md, docs/legal/privacy-policy.md, docs/legal/acceptable-use-policy.md.

What to do

Create three legal document files under docs/legal/. These are standard SaaS API documents — use clear plain-English language appropriate for a small developer-focused API business.

File 1: docs/legal/terms-of-service.md

Include:

  • Service description (REST APIs: ZIP enrichment, holidays, air quality)
  • Acceptable use summary (link to AUP)
  • Rate limits and quota enforcement notice
  • No-warranty clause
  • Governing law (to be filled in by operator — placeholder: "[Jurisdiction]")
  • Contact email placeholder

File 2: docs/legal/privacy-policy.md

Include:

  • What data is collected (API request logs: IP, endpoint, timestamp — no PII in responses)
  • How data is used (rate limiting, abuse prevention, analytics)
  • Retention period (90 days for logs)
  • Third-party processors (RapidAPI, PayPal)
  • Contact email placeholder

File 3: docs/legal/acceptable-use-policy.md

Include:

  • Prohibited uses (scraping at abusive rates, illegal content lookups, reselling without permission)
  • Enforcement (API key revocation, account ban)
  • Reporting abuse contact

Acceptance criteria

  • All three files committed to docs/legal/ in this repo
  • Each document is coherent, readable, and covers the sections listed above
  • Placeholders clearly marked with [TODO: ...] for items the operator must fill in (jurisdiction, contact email, entity name)
  • PR merged to leeworks-agents/api-company

Dependencies

  • None — can be written immediately

(Reference: ROADMAP.md §Phase 6)

## Roadmap reference Phase 6 — Pre-launch: `docs/legal/terms-of-service.md`, `docs/legal/privacy-policy.md`, `docs/legal/acceptable-use-policy.md`. ## What to do Create three legal document files under `docs/legal/`. These are standard SaaS API documents — use clear plain-English language appropriate for a small developer-focused API business. ### File 1: `docs/legal/terms-of-service.md` Include: - Service description (REST APIs: ZIP enrichment, holidays, air quality) - Acceptable use summary (link to AUP) - Rate limits and quota enforcement notice - No-warranty clause - Governing law (to be filled in by operator — placeholder: "[Jurisdiction]") - Contact email placeholder ### File 2: `docs/legal/privacy-policy.md` Include: - What data is collected (API request logs: IP, endpoint, timestamp — no PII in responses) - How data is used (rate limiting, abuse prevention, analytics) - Retention period (90 days for logs) - Third-party processors (RapidAPI, PayPal) - Contact email placeholder ### File 3: `docs/legal/acceptable-use-policy.md` Include: - Prohibited uses (scraping at abusive rates, illegal content lookups, reselling without permission) - Enforcement (API key revocation, account ban) - Reporting abuse contact ## Acceptance criteria - All three files committed to `docs/legal/` in this repo - Each document is coherent, readable, and covers the sections listed above - Placeholders clearly marked with `[TODO: ...]` for items the operator must fill in (jurisdiction, contact email, entity name) - PR merged to `leeworks-agents/api-company` ## Dependencies - None — can be written immediately _(Reference: ROADMAP.md §Phase 6)_
AI-Manager added the agent-readyroadmapphase-6P2small labels 2026-05-26 05:22:32 +00:00
AI-Manager commented 2026-05-26 10:08:34 +00:00
Author
Owner
Copy Link
Copy Source

All three legal documents have been committed to docs/legal/:

  • docs/legal/terms-of-service.md — Service description, acceptable use summary, rate limit notice, no-warranty clause, governing law placeholder, contact placeholder
  • docs/legal/privacy-policy.md — Data collected, use, 90-day retention, third-party processors (RapidAPI, PayPal), contact placeholder
  • docs/legal/acceptable-use-policy.md — Prohibited uses, enforcement, abuse reporting

All documents use plain English, have [TODO:] placeholders for operator-specific fields (jurisdiction, entity name, contact email), and were merged in PR #20. Closing as done.

All three legal documents have been committed to docs/legal/: - docs/legal/terms-of-service.md — Service description, acceptable use summary, rate limit notice, no-warranty clause, governing law placeholder, contact placeholder - docs/legal/privacy-policy.md — Data collected, use, 90-day retention, third-party processors (RapidAPI, PayPal), contact placeholder - docs/legal/acceptable-use-policy.md — Prohibited uses, enforcement, abuse reporting All documents use plain English, have [TODO:] placeholders for operator-specific fields (jurisdiction, entity name, contact email), and were merged in PR #20. Closing as done.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
Ready for /manager to dispatch to @repo-manager
 blocked
Depends on another issue or external prerequisite
 large
medium
phase-0
Orientation / one-time setup
 phase-1
OpenAPI contract
 phase-2
Data acquisition + caching
 phase-3
API server implementation
 phase-4
Container + Helm chart
 phase-5
GitOps deploy via Flux
 phase-6
Pricing + RapidAPI listing
 roadmap
Long-horizon item /sprint will sequence
 small
No Label P2 agent-ready phase-6 roadmap small
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/api-company#40
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?