PurpleCraft / trust

Trust is part of the work

The proposed delivery approach: clear boundaries, sensible data use, visible exceptions, and a handover you can understand.

PRINCIPLE 01

Use only the information the job needs

We will agree the sources and data required for the work, how they will be accessed, and which providers will process them. We will avoid asking for unnecessary personal or confidential information. Sensitive-data use requires a separate suitability and handling review before work begins.

PRINCIPLE 02

Make access explicit

We will document the accounts and permissions needed for the agreed task. Access should be limited to that purpose and removed or transferred when the work ends, following the agreed handover plan. We will not ask you to send passwords through the enquiry form.

PRINCIPLE 03

Agree what the AI may do

Customer-facing responses, booking actions, publishing, record changes, and other external actions will have defined boundaries. Workflows will identify the steps requiring human approval and the situations that need escalation.

PRINCIPLE 04

Treat errors as a design requirement

AI output can be incomplete or wrong. We will test important paths, record known limitations, and explain what the system cannot reliably decide. Where the task needs checked records or source-backed answers, review and source visibility will be part of the agreed design.

PRINCIPLE 05

Be clear about providers and data handling

We will identify relevant third-party services and review their applicable settings and terms with the project requirements in mind. Storage location, retention, deletion, and model-training use will be confirmed for the selected setup. No blanket promise about those matters should be inferred from the use of AI.

PRINCIPLE 06

Give you an operating handover

We will document the agreed ownership, ongoing costs, key controls, known dependencies, and support route. Any monitoring or response commitment will be stated in the service agreement. It should never be assumed to be continuous or unlimited.

Specific promises require a specific setup.

Storage location, retention, model-training settings, access controls, and incident coverage depend on the selected services and contract. This page does not claim a certification, universal zero retention, guaranteed data residency, or continuous monitoring.

One good place to start

What would you love
to take off your plate?

Tell us what’s getting in the way. We’ll start there.

Let’s find your first winClear scope. Real examples. No pressure to buy.