# Atmosphere white-labelling information

Version 1.0 | Published 12 August 2026

## Overview

Atmosphere may support programme-specific or partner-facing identity where this is agreed as part of a deployment. White-labelling is not a single visual switch: it affects ownership, support, domains, identity, communications, legal copy, and operational accountability.

## Configurable surfaces for review

- Programme or partner name and approved visual identity.
- Application domain and email communications.
- Navigation labels, help content, and support routes.
- Role names and organisation-specific workflow terminology.
- Approved reports, exports, and customer-facing notices.

## Responsibilities that remain explicit

- Which organisation is the service owner and data controller.
- Who manages user support, access recovery, and incident communications.
- Which party approves device commands and operational changes.
- Which legal, privacy, accessibility, and market notices must be shown.
- How Atmosphere and participating partners are identified where required.

## Delivery process

1. Define audiences, ownership, and the intended service boundary.
2. Agree the identity hierarchy and non-configurable trust information.
3. Review domains, authentication, communications, and support workflows.
4. Validate responsive, accessible, and operational states.
5. Approve the configured experience before deployment.

Availability is subject to technical discovery and commercial agreement. Contact hello@myatmosphere.co.uk for a scoped review.