Site terms.

getpleach.com — the marketing pages and the rendered documentation. Reading, linking to, or quoting from the site means you accept these terms.

These terms do not govern the @pleach/* packages on npm. Each package ships with its own LICENSE file. See /license for an orientation.

Site copy, layout, and original illustrations are © Pleach, available for quotation and citation under normal fair-use practice. Republishing a full page verbatim, or scraping the site to train a competing documentation surface, isn’t the intended use — email getpleach@protonmail.com first.

Code samples embedded in the documentation are released under the same license as the package they document. Treat a snippet from @pleach/core docs as FSL-1.1-Apache-2.0 code, not as content covered by these terms.

The site is provided as-is. We aim for accuracy — the docs are checked against the package READMEs — but mistakes happen. When the docs and a package’s shipped README conflict, the package wins. File a docs bug on the repo issues.

Pleach makes no warranty about uptime, link permanence, or continued availability of any specific page. URLs may move as the docs evolve; we’ll add redirects when we remember to.

• — Reading, linking, quoting, citing: fine.
• — Mirroring with attribution and a back-link: fine.
• — Automated crawling that respects robots.txt and reasonable rate limits: fine.
• — Republishing pages as your own, scraping for ML training without honoring ai.txt, or impersonating Pleach branding: not fine.

The Pleach name and the pleach mark identify the OSS project. You can refer to the project by name in articles, talks, integrations, and comparisons. Don’t use the mark in a way that implies endorsement of a product that isn’t officially under @pleach/*.

The site links to npm, GitHub, package documentation, and related projects. Those destinations are governed by their own terms — we don’t control their content and don’t warrant it.

Material changes are noted by bumping the “Last updated” date. The page is versioned in the public site repository; the diff is auditable.