Professional indemnity cover applies to all UK and EU engagements, with coverage levels appropriate to the use case — safety-critical engagements carry higher cover. Cyber liability cover applies to all data-handling work. We can provide certificates of insurance and confirm cover levels during procurement. For regulated engagements (healthcare, AV, finance), we agree liability allocation explicitly in the SOW — including indemnification clauses where the workload warrants it. We do not operate without insurance, and we do not push back on procurement teams that ask for proof of cover — it's the right question to ask.

Safety-critical content (autonomous-vehicle incidents, medical imaging with trauma, moderation for harm categories) carries documented wellbeing protocols. Senior specialists hold the safety-critical calls; rotation off distressing content is built into scheduling; psychologist-led support is available for accounts where the content warrants it. The 96% retention number is not just a quality metric — it's evidence that we don't burn annotators out on hard content. Specifically for safety-critical robotics and medical work, we cap exposure-per-day, run regular check-ins, and provide structured debriefs. The team that started on a programme is the team that finishes it.

Standard contracting in GBP for UK engagements, EUR for EU, USD for North America. Other currencies on a case-by-case basis — most enterprise accounts find one of those three works for their AP team. The UK entity (Indivillage UK Pvt Ltd, Companies House 14512282) handles UK and EU billing; US/EU billing routes through the relevant parent entity where preferred for procurement reasons. Net 30 standard terms; longer terms (60/90) available for enterprise accounts with appropriate adjustments. We accept the standard procurement onboarding pack (W-8/W-9, banking details, insurance certificates, modern slavery statements) without friction.

Your data is yours. Labels we produce on your data are yours. We do not reuse client data across other engagements, we do not include client data in any cross-account training set, and we do not retain client data beyond the engagement period without explicit instruction. Data provenance is documented at the batch level — every label carries metadata identifying the annotator, reviewer, taxonomy version, and source asset. For accounts with stringent IP requirements (defence, regulated healthcare, proprietary autonomous systems), we operate inside your environment with no data egress to our infrastructure. All standard NDAs and DPAs signed before engagement; reverse-NDAs accepted where required.