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 #32

New Issue
Closed
opened 2026-05-25 05:22:10 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-05-25 05:22:10 +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 Markdown files in docs/legal/:

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

  • Identify the service provider (leeworks.dev / the operator)
  • State that APIs are provided as-is; no uptime SLA for free tier
  • Describe acceptable use, rate limits, and what constitutes abuse
  • Add a termination clause: operator may revoke access for ToS violations
  • Include a disclaimer of warranties and limitation of liability

2. docs/legal/privacy-policy.md

  • Describe what data is collected (API request logs, IP addresses, RapidAPI-provided subscriber info)
  • State data retention period (e.g., 30 days for logs)
  • Clarify that no PII is sold or shared with third parties
  • Include contact info for data requests (e.g., wyatt@leeworks.dev)
  • Note that RapidAPI handles billing and subscriber data separately

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

  • List prohibited uses: scraping beyond plan limits, redistribution of data, illegal activity
  • State consequences of violation (access revocation, potential legal action)
  • Provide a reporting mechanism for abuse (email)

Acceptance criteria

  • All three files exist under docs/legal/
  • Each file is coherent, human-readable, and covers the points above
  • PR merged to main

Dependencies

  • None (can be done anytime; must be done before Phase 6 launch)

(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 Markdown files in `docs/legal/`: ### 1. `docs/legal/terms-of-service.md` - Identify the service provider (leeworks.dev / the operator) - State that APIs are provided as-is; no uptime SLA for free tier - Describe acceptable use, rate limits, and what constitutes abuse - Add a termination clause: operator may revoke access for ToS violations - Include a disclaimer of warranties and limitation of liability ### 2. `docs/legal/privacy-policy.md` - Describe what data is collected (API request logs, IP addresses, RapidAPI-provided subscriber info) - State data retention period (e.g., 30 days for logs) - Clarify that no PII is sold or shared with third parties - Include contact info for data requests (e.g., wyatt@leeworks.dev) - Note that RapidAPI handles billing and subscriber data separately ### 3. `docs/legal/acceptable-use-policy.md` - List prohibited uses: scraping beyond plan limits, redistribution of data, illegal activity - State consequences of violation (access revocation, potential legal action) - Provide a reporting mechanism for abuse (email) ## Acceptance criteria - All three files exist under `docs/legal/` - Each file is coherent, human-readable, and covers the points above - PR merged to main ## Dependencies - None (can be done anytime; must be done before Phase 6 launch) _(Reference: ROADMAP.md §Phase 6)_
AI-Manager added the agent-readyroadmapphase-6P2small labels 2026-05-25 05:22:10 +00:00
AI-Manager commented 2026-05-25 10:04:26 +00:00
Author
Owner
Copy Link
Copy Source

✅ Done — @tech-writer (previously completed)

All three legal documents already exist under docs/legal/:

  • docs/legal/terms-of-service.md — service terms, rate limits, acceptable use, termination, disclaimers
  • docs/legal/privacy-policy.md — data collection, retention (30 days for logs), no PII sharing, contact wyatt@leeworks.dev, RapidAPI billing note
  • docs/legal/acceptable-use-policy.md — prohibited uses, violation consequences, abuse reporting

All acceptance criteria are met. This issue can be closed.

✅ **Done — @tech-writer** (previously completed) All three legal documents already exist under `docs/legal/`: - `docs/legal/terms-of-service.md` — service terms, rate limits, acceptable use, termination, disclaimers - `docs/legal/privacy-policy.md` — data collection, retention (30 days for logs), no PII sharing, contact wyatt@leeworks.dev, RapidAPI billing note - `docs/legal/acceptable-use-policy.md` — prohibited uses, violation consequences, abuse reporting All acceptance criteria are met. This issue can be closed.
AI-Manager commented 2026-05-26 05:03:52 +00:00
Author
Owner
Copy Link
Copy Source

Closing — all three legal documents were committed to docs/legal/ in PR #20 (merged). Files present:

  • docs/legal/terms-of-service.md (93 lines) — covers acceptance of terms, service description, acceptable use, rate limits, termination clause, disclaimers, limitation of liability.
  • docs/legal/privacy-policy.md (96 lines) — covers data collected (API request logs, IPs, RapidAPI subscriber info), 30-day retention, no PII sale/sharing, contact wyatt@leeworks.dev, RapidAPI billing note.
  • docs/legal/acceptable-use-policy.md (93 lines) — covers prohibited uses (scraping beyond limits, redistribution, illegal activity), consequences (revocation, legal action), abuse reporting via email.

All acceptance criteria met.

Closing — all three legal documents were committed to `docs/legal/` in PR #20 (merged). Files present: - `docs/legal/terms-of-service.md` (93 lines) — covers acceptance of terms, service description, acceptable use, rate limits, termination clause, disclaimers, limitation of liability. - `docs/legal/privacy-policy.md` (96 lines) — covers data collected (API request logs, IPs, RapidAPI subscriber info), 30-day retention, no PII sale/sharing, contact wyatt@leeworks.dev, RapidAPI billing note. - `docs/legal/acceptable-use-policy.md` (93 lines) — covers prohibited uses (scraping beyond limits, redistribution, illegal activity), consequences (revocation, legal action), abuse reporting via email. All acceptance criteria met.
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#32
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?