Data protection
PDPA compliant. Data Protection Officer appointed. Client data processed only for the contracted purpose.
Delivery & trust
Your data sits where you put it. The code is yours from the first commit. Every claim on this page is backed by a document we will hand your risk function on request.
Delivery method
The acceptance criteria are written at design, before the build starts, and they are the same criteria your team runs UAT against at the end.
Scope, stakeholders and success criteria agreed.
Architecture, interfaces and written acceptance criteria.
Two-week increments, demonstrated each cycle.
Independent review, automated evaluation, client UAT.
Documentation, training and repository access.
Quality assurance. Independent code review by an engineer outside the build team. Automated evaluation of agent behaviour, not just unit tests. Client-run UAT against the agreed criteria.
Trust & compliance
These are contract terms, not intentions. The corresponding policy documents and certificates are available before you commit to anything.
PDPA compliant. Data Protection Officer appointed. Client data processed only for the contracted purpose.
Singapore or client-nominated region. AWS Bedrock deployments in ap-southeast-1 by default.
All work product assigns to the client on final payment. We retain no rights to client data or bespoke code.
Mutual NDA standard. All personnel including associates under written confidentiality obligations.
Professional indemnity and public liability cover in place. Certificate, with current sums insured, on request.
Every engagement has a named backup lead. All code and documentation in client-accessible repositories from day one.
Where your data sits
Singapore by default — or any AWS region you require. Data never leaves the region you choose, and is never used to train any model.
Singapore · AWS ap-southeast-1
Sub-processors
| Party | Purpose | Region | Trains on your data |
|---|---|---|---|
| Anthropic | Model inference | Region-pinned | No |
| Amazon Web Services | Bedrock inference, compute, storage | ap-southeast-1 | No |
Any additional sub-processor introduced for your engagement is named, with its purpose and region, before it is used.
Retention & exit
Procurement pack
None of this is held back until contract stage. Ask and we send it — most of it goes out the same working day.
Security questionnaires and RFP schedules. Send yours in whatever format your process uses. We complete them ourselves rather than returning a brochure, and we mark anything that is a roadmap item as a roadmap item.
Policy set
Each policy document is available to your risk, legal or procurement function on request.
Next steps
We would rather your compliance function reads the pack before the commercial conversation than after it. Ask and we will send it.