Follow the evidence. Keep control of the decision.

From a finding to its source

Origin connects a reading or result to its supporting material. In the public Library, this includes the publisher, publication, reporting period, source excerpt and inputs behind a calculation. Source dates stay separate from the date we captured or reviewed them.

Human responsibility stays explicit

A surfaced issue or model answer supports a review; it does not itself approve a design, establish compliance or authorise a commercial decision. PromptStacks connect checks and supporting evidence to the responsible reviewer and next action.

Marketing demonstrations use labelled fictional examples. Public Library reports use reviewed public sources. Neither implies access to a client’s confidential records.

Agree the controls for your environment

Deployment, integrations and model-provider choices depend on the agreed solution. Before processing customer information, establish the required environment and responsibilities with the BuildPrompt team.

• Which data may be processed, by whom, and for which workflows.
• Access permissions, authentication and reviewer responsibilities.
• Hosting location, model providers and any data transfer requirements.
• Retention, deletion, logging and evidence-export requirements.
• Contractual terms, the data processing agreement and the scope of relevant assurance evidence.

Do not infer a deployment’s controls from a marketing demonstration. Request current certification documents and their scope during procurement.

This public website

The marketing website and public Library are separate from customer platform environments. The Library publishes selected public evidence; it does not provide access to customer systems.

Optional website analytics and advertising are controlled through Cookie preferences. The Microsoft enquiry form opens only when requested.