# Customer terms review checklist

This checklist is input for qualified counsel, not customer terms and not legal
advice. Seller-specific terms must not be published until the seller identity,
jurisdictions, price, support service, privacy behaviour, and consumer-law
requirements are known and independently reviewed.

## Terms must say clearly

- SmartCut64 is free software under GPL-3.0-or-later; the complete GPL controls
  software-copying, modification, and redistribution rights.
- The customer may run, inspect, modify, reverse engineer as necessary to
  exercise open-source rights, and redistribute the software and modifications.
- Payment is for the delivered copy and any separately described convenience,
  update, or support service. It does not buy exclusivity or prevent another
  recipient from redistributing the software without payment.
- FFmpeg, Qt, and other components are owned by their respective copyright
  holders and retain their own notices and licence terms.
- Contractual support, service levels, paid updates, and any commercial
  warranty are separate from the GPL licence and do not reduce GPL/LGPL rights.
- The seller's official binaries use a locally verified, signed,
  installation-bound entitlement for clean video output. Without a valid paid
  token, official-binary video output is visibly marked and fully re-encoded.
  This controls only the seller's official binary service and does not prevent
  a recipient from modifying, rebuilding, or redistributing the GPL source.
- State the purchase/update/support duration, two-machine activation and
  transfer process, refund effect, and the fact that an already-issued
  perpetual machine-bound token cannot be remotely revoked. Explain that
  webhooks block future activation, transfer and support-assisted reset, while
  continued clean export on an activated computer is service-independent.
- Explain that the Installation ID is a local hash-derived identifier; disclose
  that the purchase email, raw Lemon key, and Installation ID are sent over
  HTTPS; explain local DPAPI storage; identify Cloudflare/Lemon processors and
  seller-side customer/licence records; and publish concrete retention,
  deletion, security, and data-subject request procedures.
- Mandatory statutory consumer rights, cancellation rights, and remedies are
  not excluded. Governing-law, jurisdiction, tax, refund, and delivery clauses
  must be written for the seller and actual sales territories.

## Terms and distribution controls must not

- prohibit copying, modification, redistribution, reverse engineering, or
  replacement/relinking of dynamically linked LGPL libraries;
- impose confidentiality on source code or prohibit publication of modified
  source;
- require downstream recipients to pay the original seller;
- use activation, DRM, account termination, or store terms to prevent exercise
  of GPL/LGPL rights;
- claim that the seller can technically or contractually prevent recipients
  from removing or changing the entitlement mechanism in their own GPL builds;
- call an Evaluation watermark a restriction on copying or redistribution, or
  imply that redistributed modified builds must retain the seller's commercial
  entitlement policy;
- claim ownership of FFmpeg, Qt, or other third-party code;
- imply VideoReDo, Dolby, DTS, codec-pool, hardware-vendor, or other third-party
  sponsorship, certification, affiliation, or endorsement;
- promise support for every stream/profile merely because the underlying codec
  family appears in product marketing.

## Documents counsel must review together

1. Checkout/download page and all advertisements.
2. Installer licence page and About dialog.
3. GPL, copyright, third-party notices, SBOM, and corresponding-source offer.
4. Privacy/cookie/crash-reporting statement and update behaviour.
5. Support, paid-update, warranty, refund, cancellation, and acceptable-use
   terms.
6. Patent-licence agreements and reporting terms, specifically for compatibility
   with unrestricted GPL redistribution.

Record the lawyer, client entity, territories, version and SHA-256 hashes of
the reviewed release, date, assumptions, required changes, and written approval
in the release evidence. A checklist marked by project developers is not an
independent review.
