Clear terms.
Real control.

Before you pay

Before any payment is requested, you receive a written scope that identifies the provider, agreed pages, features, exclusions, price, timeline, delivery route and payment milestones. You can ask questions or decline before accepting the scope.

For standard website projects, the PayPal request is sent only after the written scope and fixed price are accepted. It identifies Shi Lin trading as Linshi Studio, the agreed service, amount and due date.

Our standard business-client project agreement records the contracting correspondence details, formal project-notice route, England and Wales governing law and exclusive jurisdiction of the courts of England and Wales. Your specific written scope identifies the client, work, price and any clearly stated variation before payment.

What you receive

Your project agreement lists the agreed deliverables, including pages, included revision rounds, handover materials and any agreed account access. It also identifies what is outside scope or needs a separate quotation.

Where the relevant service allows it, your domain, hosting, essential third-party accounts and their billing control remain in your name or are transferred to you at handover. You should not send your main password by ordinary email; separate administrator access is preferred.

After final payment, you receive the client-specific source code and editable design files expressly included in your written scope. At handover, the checklist records the live address, agreed source files and asset locations, account roles, transfer or revocation steps, and any known remaining actions. Third-party licences and platform features remain subject to their own terms.

Access, backups and continuity

Access is requested only after scope acceptance, only for the agreed work and only through a client-controlled account or approved access method. Live-site changes require your written instruction. You can remove access when the agreed work is complete.

The final archive is delivered to a client-controlled folder, repository or account agreed in writing. It records the delivered source and design files, available platform export, account roles, third-party licence list and platform-specific restoration route. If a platform does not provide export or restore functionality, the checklist says so rather than implying that a backup exists.

For agreed live changes, a restorable backup is made before the change where the platform permits and this is within the written scope. The handover checklist records the backup or rollback route where one is available; it does not turn a third-party host's own backup service into a Linshi Studio guarantee or an ongoing provider-held backup service.

If the project ends early, the written agreement records what has been completed, what remains, the current project materials that can be handed over, and any proportionate-refund position for genuinely undelivered agreed work.

If something goes wrong

7-day remedy period

For seven days from handover, reported faults that prevent the agreed delivered scope working as specified are reviewed and, where confirmed, repaired at no extra charge.

After the 7-day period

The 7-day remedy period is not an automatic ongoing-maintenance plan. If a problem is reported later, we first identify whether it is a new request, a third-party or hosting change, or a fault in the agreed scope. Any work outside the remedy period is separately scoped, priced and agreed in writing before it begins.

Unable to deliver an agreed part

If Linshi Studio cannot deliver an agreed part of the written scope, the project agreement provides for a proportionate refund of the payment allocated to that undelivered part. Any cancellation, refund and handover position is confirmed in writing for the specific project.

How to raise a concern

Send the concern and relevant evidence to hello@linshistudio.com. We compare it with the written scope and delivery checklist, explain whether it is an agreed-scope fault, a new request or a third-party change, and confirm the next step in writing. This process does not remove any rights available through the agreed contract or PayPal's own procedures.

What delivery evidence looks like

Every paid project is documented with a written scope, delivery checklist, handover record and payment record. The checklist identifies the agreed pages, checks completed, account-access handover and any remaining agreed actions.

Public concept websites are labelled as concepts and are not presented as client projects. Client names, project details and references are shared publicly only with the client's written permission. If useful before a project, you can ask to see a redacted example of the delivery-checklist format and the exact record that will be used for your own project.

A recent paid website-review engagement

Linshi Studio has undertaken a paid engagement for an independent UK service business. The work was agreed in writing before payment and focused on reviewing key website pages and the customer journey.

The client receives a concise, prioritised list of practical recommendations and keeps full control over whether and how to make changes.

To protect client privacy, we do not publish the client's name, website, correspondence or project materials without written permission.

Every paid project uses a written scope, delivery checklist and handover process. Agreed-scope delivery faults reported within 7 calendar days are corrected without an additional fee.

Before paying, ask for these documents

• The written scope, inclusions, exclusions and delivery checklist.
• The agreed price, payment schedule and PayPal payment request details.
• Handover, ownership and account-control arrangements.
• The specific cancellation, proportionate-refund and remedy terms.
• The business-client project agreement template, including ownership, backup, notices and dispute terms.
• Any data-access or third-party-service arrangements relevant to your project.