During the build
How we handle your data during a build
Data handling needs an explicit agreement covering access, development environments, hosting, confidentiality and retention. Before a build starts, identify the information the work requires and who may use it. Where AI tools are proposed, confirm their data flows and provider terms as part of that discussion.
Define the information the build needs
An example form and a description of its fields may be enough to map a workflow. Testing an integration may require representative records and access to a test environment. Decide what is necessary for each stage and record who approves it.
Include AI tools in the data discussion
AI-assisted development can involve source code, prompts and contextual material. An AI feature inside an application can involve a different provider and a different data flow. Review each proposed use separately, including account settings, retention terms and the information allowed to leave the agreed environment.
Agree responsibilities before implementation
Specify access, confidentiality, hosting and retention in the engagement arrangements. Cloud services covers infrastructure choices; integration services covers connections to existing systems. Bring the relevant requirements to the discovery discussion.
Related questions
What data should we share for initial scoping?
Start with the workflow, field definitions and representative examples. Discuss whether masked or synthetic records will be enough before sharing production data. The information needed depends on the task being assessed.
How do we agree who can access project data?
List the roles that need access, the purpose of that access and the systems involved. Record approval and removal responsibilities in the project arrangements, including what changes when a person leaves the team.
What should we confirm about AI tools and our data?
Confirm the tool, the information it will receive, its retention and training terms, and the controls available under the selected account. Agree what may be shared before client code or records are submitted.
Where will development and test data be stored?
Agree the environment, hosting location, access and the test records required during scoping. Include any third-party services the application or development process will use.
What happens to data when a project pauses or ends?
The project agreement should state return, retention and deletion requirements, including backup copies and access removal. Resolve those terms before data is shared so both teams know what to do.
Plan your next software project
Tell us which workflow you want to improve and the systems it depends on. We will help define a practical starting point.