Systems notice draft

The public page should clearly explain price, product scope, tax, provider, and what happens after payment.

• State that purchases require a customer account and an active login.
• Explain whether the customer receives the download on-page, by email, or both.
• Link privacy, terms, withdrawal, and imprint directly from the payment entry page.

The payment provider stores and processes the billing data needed for the transaction.

• Keep your provider-specific data transfer description consistent with the actual Stripe or payment account setup.
• Document transaction identifiers that return to your systems after successful payment.
• Clarify whether invoices, taxes, refunds, and disputes are handled by the provider or by you.

• Store only the minimum needed for entitlement, activation, fraud prevention, and support.
• Prefer pseudonymous customer references over names or emails inside machine-readable license payloads.
• Separate public verification keys from secret signing material.

• Track only the version, channel, entitlement check, and download events required for delivery and security.
• Document if update access expires after a term while the base license remains active.
• Add checksum and integrity information to the delivery terms and support policy.

• An embedded public key is normally acceptable; never embed secret provider credentials.
• A support string should be opaque and pseudonymous, not a clear email or customer name.
• Explain how customers can request add-ons, support, or re-delivery using the purchase reference.