Privacy
Privacy Notice
What London One records when you sign in, join, apply or use the member and administration areas.
Information London One currently handles
When you use Discord sign-in, London One can store the Discord account identifier and profile information needed to identify your account, such as your current display name and avatar, together with the authentication and session records needed to keep you signed in.
Joining and application records can include your age-band attestation, microphone and rules acknowledgements, civilian onboarding state, emergency-service application answers, application status and messages sent to you about an application. London One does not ask for or store your full date of birth as part of this launch system.
Staff and security records
Authorised staff accounts can have role assignments. Actions that the platform is designed to audit, including application, recruitment and content changes, can record the staff actor, the target of the change, what changed and when it happened. These records support accountability and platform security.
The website itself does not include an analytics or advertising platform at launch. Hosting, database and application infrastructure may generate technical logs needed to operate and secure the service. The exact production logging configuration will depend on the final hosting setup and will be reflected here before the site accepts live applications.
How the information is used
Information is used to operate your London One account, check joining requirements, process applications, show your application or onboarding status, administer the community and protect the service. Access to member and applicant information is restricted through authenticated, role-based areas of the platform.
London One does not sell member information to advertisers. The platform uses Discord as its sign-in provider, so Discord handles information under its own service and privacy terms when you authenticate there.
Retention, access and contact
London One is still in pre-launch. An operational retention schedule and dedicated privacy contact route must be set before real production applications are accepted. We will update this notice to reflect those arrangements rather than publishing a retention period that is not yet implemented.
Once the production support route is published, you will be able to use it to ask about the information held about your account or request a correction or deletion where appropriate. Some security and audit information may need to be retained where it remains necessary to protect the service or maintain an accountable record of platform actions.