Sustainability Policy
Cloud & Culture Ltd · Version 1.1.0 · 30 September 2026
We offset our residual emissions
Registry-retired credits, durable removals preferred, certificate held before the purchase is recorded. Offsets sit outside the account — the reported figure always stands at gross.
Sustainability Policy
Cloud & Culture Ltd
Version 1.1.0 · 30 September 2026
- Baseline2023 → 2025
- AssuranceSelf-reported
- OffsettingResidual only
- Next review2027-09-30
Almost all of our environmental impact is computing: hosting, and the AI inference we use to build software. We state what we count, we say when a number does not exist, and we make no environmental claim we cannot evidence.
activity categories inside the boundary
categories recorded as nil, not omitted
estimated figures in the account
The reporting entity is Cloud & Culture Ltd. Inside the boundary: office energy; computing and hosting; AI inference used in development; hardware; subcontracted work; events and their local travel.
Print and client travel are recorded as nil, not omitted.
Baseline: 2023 to 2025 — our first statutory accounting period, so the carbon baseline shares a boundary with the financial accounts. It was a pre-launch year and may be restated once a representative trading year exists.
Where a figure cannot be obtained we record “no data published” and do not estimate it. The absence is itself the finding.
| Activity | Activity metric | Status |
|---|---|---|
| Hosting | Spend, compute hours | Measured |
| Office energy | kWh | Measured |
| Hardware | Units, purchase date | Measured |
| AI inference (development) | Token volume | No data published |
| Content delivery | Spend | No data published |
| AI inference (in-app) | — | Nil |
| — | Nil | |
| Client travel | — | Nil |
Hosting emissions are taken from our provider's carbon footprint report — a vendor figure, GHG-Protocol aligned, not third-party assured, and open to restatement by the provider.
Hardware is kept for its full supported life; the longest support plan is taken at purchase; faults are repaired in preference to replacement; refurbished handsets are used for testing.
We choose the lowest-carbon cloud region among those meeting data-residency, latency and cost needs. Hosting is migrating towards serverless deployment, and its effect is measured rather than asserted. Air travel is constrained.
AI inference is right-sized: the smallest model capable of the task, with routine and high-volume work routed to smaller, faster models and the largest reasoning model reserved for work that needs it. Extended-thinking and agentic modes are enabled per task rather than by default, and context length is kept to what the task requires. This is evidenced through spend and token-volume records, not asserted as a carbon reduction.
Not set in this version. A target built on a single pre-launch year would not be meaningful. When set: absolute rather than intensity-only, with a target year, at least one interim milestone within the current directors' tenure, and the implied annual reduction rate stated.
We offset residual emissions — what remains after the commitments in chapter 04, never in place of them. Credits are retired on a recognised registry (Gold Standard, Verra VCS or the UK Woodland Carbon Code) and the retirement certificate is held before the purchase is recorded. Durable removals are preferred to avoidance credits, and the credit type is stated alongside the tonnage. Purchases round up to the next whole tonne, and the over-purchase is recorded as an over-purchase.
Offsets are held outside the account as contributions and are never netted against reported gross emissions. Retiring credits does not entitle us to be described as carbon neutral, net zero, climate positive or carbon negative, and we do not use those words about ourselves.
Figures are reviewed once a year on 30 September, matching the accounts and the review cycle. We record adverse results — increases and missed targets — not only improvements.
We make no environmental claims in our own marketing, and we do not reproduce a supplier's characterisation of itself. Any claim must have dated evidence held before publication, and is recorded in a claims log with its source, date and approver.
This version is self-reported and not externally assured. The hosting figure is vendor self-reported, not third-party assured, and may be restated.
One named director is accountable for this policy — not “the company”, not “management”. Next review: 30 September 2027.