Skip to content

docs(landing): add privacy policy and terms of use pages#1359

Merged
jcllobet merged 7 commits intodevfrom
docs/terms
Apr 5, 2026
Merged

docs(landing): add privacy policy and terms of use pages#1359
jcllobet merged 7 commits intodevfrom
docs/terms

Conversation

@jcllobet
Copy link
Copy Markdown
Collaborator

@jcllobet jcllobet commented Apr 5, 2026

Summary

  • Privacy Policy (/privacy): comprehensive policy covering Desktop App (no tracking), Cloud Service (operational telemetry only), and Website (PostHog analytics). Includes GDPR legal bases, data retention schedule, named sub-processors (PostHog, Polar, Google, GitHub, Daytona), 72-hour breach notification, cookie categorization, US state privacy rights (consolidated), AI output disclaimer, and no-sensitive-data clause.
  • Terms of Use (/terms): covers AI output disclaimer, IP ownership (user owns output, we don't retain content), export controls/sanctions, no sensitive data, beta features, feedback clause, publicity rights, JAMS arbitration (Delaware), and billing via Polar.
  • Reusable legal page infrastructure: shared LegalPage component and parseLegalDoc utility that parses .txt legal documents into styled React pages with bold definition terms, subheadings, and clickable email links.
  • Footer: added Privacy and Terms links.
  • .gitignore: added .turbo/ to prevent build cache from being committed.

Key decisions

  • Age requirement: 18+ (aligned across both documents)
  • We do not retain user content, do not sell personal data, do not do retargeting
  • LLM providers are NOT listed as sub-processors (users connect with their own API keys)
  • US state privacy rights consolidated into single section with "most protective provision" clause
  • Severability and Entire Agreement clauses in both documents with conflict resolution (Privacy Policy controls on data matters)

jcllobet added 2 commits April 5, 2026 00:08
- Add comprehensive privacy policy covering Desktop App (no tracking),
  Cloud Service (operational telemetry only), and Website (PostHog analytics)
- Add terms of use with AI output disclaimer, export controls, beta features,
  feedback, publicity rights, and JAMS arbitration
- Create reusable LegalPage component and shared parser for .txt legal docs
- Add Privacy and Terms links to site footer
- Both pages render with consistent styling, bold definition terms,
  subheadings for tracking technology categories, and clickable email links
@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Apr 5, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
openwork-app Ready Ready Preview, Comment Apr 5, 2026 7:14am
openwork-den Ready Ready Preview, Comment Apr 5, 2026 7:14am
openwork-den-worker-proxy Ready Ready Preview, Comment Apr 5, 2026 7:14am
openwork-landing Ready Ready Preview, Comment, Open in v0 Apr 5, 2026 7:14am
openwork-share Ready Ready Preview, Comment Apr 5, 2026 7:14am

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 5, 2026

The following comment was made by an LLM, it may be inaccurate:

- Detect definition blocks ("Term" means ...) and render as bulleted
  list with bold terms
- Bold ALL CAPS text (warranty disclaimers, arbitration notices, etc.)
- Make URLs clickable links alongside emails
- Distinguish h2 headings (questions, longer titles) from h3 subheadings
  (short section names like "Our IP", "Billing", "Usage Data")
- Clarify recurring billing cancellation: users can cancel via account
  settings first, contact email as fallback at our discretion
- Fix URL regex to avoid capturing trailing periods/punctuation
- Add proper heading hierarchy (# h1, ## h2, ### h3)
- Bold definition terms, ALL CAPS legal clauses, and sub-processor names
- Convert restriction items into bullet points
- Make all URLs and emails clickable markdown links
- Use blockquote for the API key disclaimer note
- Structure tracking technologies as proper subheadings
- Rename .txt to .md with proper markdown formatting
- Replace txt parser with lean render-markdown.tsx (zero deps, ~120 lines)
- LegalPage handles full page shell — page.tsx files are now 8 lines each
- Add legal-prose CSS for consistent typography
- Delete parse-legal-doc.tsx
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant