docs(landing): add privacy policy and terms of use pages#1359
Merged
Conversation
- 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
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
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
…ed, late refunds at our discretion
- 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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/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): 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.LegalPagecomponent andparseLegalDocutility that parses.txtlegal documents into styled React pages with bold definition terms, subheadings, and clickable email links..gitignore: added.turbo/to prevent build cache from being committed.Key decisions