Clear principles for generation credits.

1. What a credit represents

A LamSnap credit represents eligibility to submit a supported generation request. It does not purchase a particular design outcome and does not guarantee that the AI result will match a user's preference, physical material or intended installation.

2. When a credit may be consumed

Where credits are enabled, the applicable interface should disclose when a credit will be used. A credit may be consumed when LamSnap accepts an eligible request for processing and the configured generation workflow performs the chargeable work.

Repeated button presses that resolve to the same active request should not intentionally create duplicate charges. Technical records may be reviewed where duplicate processing is suspected.

3. Successful and failed generations

A generation recorded as successfully completed may consume the applicable credit even if the user dislikes the creative result. AI variation, input quality and subjective preference are not by themselves technical failures.

A request recorded as failed before a usable result is produced may qualify for automatic or manual credit restoration according to the implemented credit system. Restoration is not promised until the production billing and credit rules are approved and displayed.

4. Duplicate or technical-error review

LamSnap may review project identifiers, timestamps, generation status, retry history and sanitised technical diagnostics to determine whether a duplicate request, provider failure or platform error occurred.

A review may result in credit restoration where the records support it. It does not guarantee a cash refund or a particular resolution.

5. Situations that may not qualify

Subject to applicable law and the final commercial terms, restoration or refund may not apply where:

• A generation completed and produced an accessible result, but the user prefers a different style or interpretation.
• The request relied on unclear, obstructed, unsupported or unauthorised input.
• The user repeated a request after a result was already available.
• Access was affected by the user's device, browser, network, deleted local data or unverified third-party service.
• Credits were obtained or used through abuse, fraud, automation or violation of the Terms.

6. Requesting review

A verified support channel, required evidence, submission deadline and expected review time have not yet been approved. Those details must be published before paid credits are offered.

When available, a request should identify the relevant project or generation without sharing passwords, API keys, full payment details or unnecessary private images.

7. Misuse

LamSnap may deny restoration, suspend credit access or investigate activity where there is reasonable evidence of duplicate claims, manipulated records, abusive automation, payment fraud or attempts to bypass service controls.

8. Policy updates and founder decisions

Credit price, validity, expiry, included allowances, cash-refund eligibility, request deadline, review time, payment-provider rules and jurisdiction-specific consumer rights remain subject to founder and legal approval.

No paid credit should be sold on the basis of this draft until those commercial decisions, the verified support channel and an effective date are published.