Publish EULA + LICENSE on swisscairn.ch and link from checkout (pre-launch) #33

Open
opened 2026-09-07 01:12:41 +00:00 by Cordy · 0 comments
Owner

The product-wide EULA now lives in the Cairn repo (EULA.md, draft v0.1, 2026-09-07 — Cairn PR #445). The repo copy stays the source of truth (the EULA's own §10 says the applicable version ships with the software), but it also belongs on the site:

  • A /eula (and /license) page — buyers must be able to read the terms before purchase, and Paddle checkout should link them (Paddle requires linkable terms for the checkout flow; Paddle is merchant of record for the payment, the EULA governs use).
  • Footer links on the main pages.
  • Render from the repo file or copy verbatim with the version/date stamp — no site-only edits, so the two can never drift.

Blocked on: legal review of both EULA.md and LICENSE.md (part of the #26 launch gate on the Cairn side), and the GmbH name swap once the entity is registered (the EULA carries a maintenance note; "GmbH" may not be used before commercial-register entry).

Timing: whenever the next site work session happens — content can go up gated with the rest and un-gate at launch.

The product-wide EULA now lives in the Cairn repo (`EULA.md`, draft v0.1, 2026-09-07 — Cairn PR #445). The repo copy stays the source of truth (the EULA's own §10 says the applicable version ships with the software), but it also belongs on the site: - **A `/eula` (and `/license`) page** — buyers must be able to read the terms *before* purchase, and Paddle checkout should link them (Paddle requires linkable terms for the checkout flow; Paddle is merchant of record for the payment, the EULA governs use). - **Footer links** on the main pages. - Render from the repo file or copy verbatim with the version/date stamp — no site-only edits, so the two can never drift. Blocked on: legal review of both EULA.md and LICENSE.md (part of the #26 launch gate on the Cairn side), and the GmbH name swap once the entity is registered (the EULA carries a maintenance note; "GmbH" may not be used before commercial-register entry). Timing: whenever the next site work session happens — content can go up gated with the rest and un-gate at launch.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/cairn-site#33
No description provided.