Understand purchase terms

Author The Listener Topic Bassilisk First published Last updated 3 min read

Suggest a correction

Access lets your account open a purchased guide. Its licences and recorded purchase permissions describe use of the material. Read the offer's documents before paying and keep the saved agreement for your order.

Why it matters

A guide can contain files with different licences. The purchase also has seller details, included content and an access commitment. Read these together before deciding whether the guide fits your project. A download button does not explain permission to share, modify or publish the material.

The purchase review links the published Build Guide licence. Purchase details shows the purchase permissions and resource licence statements. For the file-level choices, read Licences for guides and files.

How it works

Access and permission are separate

Bassilisk checks your purchasing account before delivering the purchased copy or its files. The licence is a separate record. Read the licence name, full custom text where supplied, and any linked full terms.

When an offer adds no reuse permission, its purchase-permissions wording is: “The published build and resource licences apply. This purchase adds no reuse permission.” Another offer can record additional permission. Read the wording on your own order instead of assuming that every paid guide grants the same uses.

For a resource that follows an external provider's terms, the purchase details say: “the external provider's licence applies; no additional rights are granted by this purchase.” Check the provider's terms for that resource.

The agreement records the purchase

The saved agreement records the guide and order reference, buyer email, seller identity and contact details, acceptance time, total price and tax wording. It includes the content description, language, requirements, delivery, access commitment and support information accepted for that order.

It also records the approved build revision, protected content scope, published build licence, resource licence statements, purchase permissions, document versions and declaration text. The confirmation adds the payment-verification time. Later edits to the public build or seller details do not rewrite that stored agreement.

Where to read the documents

Use the links on the purchase you are reviewing to check its documents and versions. For an earlier purchase, use the saved agreement when comparing terms with a current page. If a required document cannot be read, resolve that with the seller before continuing to payment.

Immediate supply and withdrawal

The purchase form separates licence acceptance from these two declarations:

I expressly consent to the seller supplying the digital content before the 14-day withdrawal period ends.

I acknowledge that, when supply begins, I lose my right of withdrawal, provided the required contract confirmation has been supplied.

Read the complete Withdrawal notice in Purchase details and your agreement. Use Withdraw from contract to prepare a statement. The form works without sign-in and has a separate Confirm withdrawal step. Its receipt states: “This receipt acknowledges receipt; it does not decide your legal rights or confirm a refund.”

What to check

Match the guide, seller, price, included files and requirements to the order you intend to place. Read the access commitment and resource licences. Keep the agreement and purchase reference together so you can identify the accepted offer when asking for help.

Common mistakes

  • Reading only the Build Guide licence and skipping file-specific terms.
  • Treating licence acceptance as the separate immediate-supply declaration.
  • Using the current offer as the only record of an older purchase.
  • Treating a request receipt as a refund decision.

Follow Buying a build guide for checkout and Purchase and access help for missing access or a purchase request.

First published

Last updated

The author maintains this document. Contributors can suggest corrections.

Discussion

No linked discussion yet. Ask a question or add context from your own work.