UK-hosted operations
Primary application and operational database infrastructure is located in the United Kingdom, with Cloudflare providing connectivity and network-level protection.
How hosting worksSwimming clubs rely on accurate, secure information to manage their members, volunteers, competitions and day-to-day operations.
SwimNexus provides specialist management software for swimming clubs and competition organisers. We design for data protection, controlled access and clear operational responsibilities, so clubs can manage their information responsibly while maintaining control over who can access it.
Protecting club information depends on how the platform is hosted, how records are separated, who can reach them and how they can be recovered. These are the controls behind SwimClubOS today.
Primary application and operational database infrastructure is located in the United Kingdom, with Cloudflare providing connectivity and network-level protection.
How hosting worksSwimClubOS uses separate operational databases and private storage for individual clubs, helping prevent one customer reaching another's records.
How records are separatedClubs assign permissions for administrators, committee members, coaches, team managers, volunteers and families. Access follows a person's role and relationship with the club.
How access is controlledAutomated backup files are encrypted before upload to Microsoft OneDrive and Google Drive. Recovery from cloud backups has been successfully tested.
How recovery worksSwimNexus operates its primary application and database infrastructure in the United Kingdom. The platform runs on Windows server infrastructure using Apache/PHP and MariaDB.
We use Cloudflare Tunnel to securely connect the hosting infrastructure to Cloudflare's global network. This encrypted connection lets the website operate without publicly exposing the hosting server's inbound application ports.
Cloudflare provides connectivity and network-level security services, including traffic processing and edge protections. Cloudflare may process technical information such as IP addresses, HTTP traffic and security events. We do not claim that it stores no personal data or that it cannot inspect application traffic.
SwimNexus's operational databases and application files remain on SwimNexus-controlled infrastructure. Cloudflare Tunnel is not our primary database or file-storage service, and the primary databases are not hosted in Cloudflare D1, R2 or Workers.
Cloudflare's network is global. The location of SwimNexus's primary infrastructure should not be read as a promise that every technical service stays within the United Kingdom.
Diagram simplified. It does not show internal network details or public server ports.
SwimClubOS is built as a multi-tenant platform. Each club's operational records are kept apart through separate infrastructure boundaries and controlled access.
Each provisioned SwimClubOS customer is resolved to its own database, with tenant-specific credentials and configuration.
Club files and private documents use the customer's storage boundary rather than a shared, unscoped upload area.
Club identity, settings and public-site details are resolved for that tenant. An unknown or incomplete tenant fails closed.
Administration and family access are limited to authorised users. Public pages expose only deliberately published information.
This approach helps keep each organisation's membership records, financial information and other operational data separate from those belonging to other customers.
Separation reduces the risk of cross-club access; it is not a claim that a breach is impossible. SwimMeetOS meets are scoped to the host organisation within the platform and are not described as separate per-host databases.
SwimClubOS uses authentication and role-based permissions to control access to club information. Clubs can assign access appropriate to each person's responsibilities, helping ensure that sensitive information is available only to authorised users.
Staff roles start with a permission preset that can then be adjusted feature by feature. Family Portal access follows linked swimmers and households rather than granting a general view of the club.
The permission model is designed around responsibilities such as:
Multi-factor authentication protects the Microsoft and Google backup-storage accounts. It is not currently enforced for every SwimClubOS or platform user account, and this page does not suggest otherwise.
Encryption protects information as it moves between services and adds a further layer to encrypted backups. These protections work alongside access control; they do not replace it.
Public website connections use HTTPS/TLS. TLS protects the connection through each hop; it is not a claim of a single end-to-end encrypted session directly between the visitor and the Windows origin.
The tunnel carries traffic over an encrypted connection between the hosting infrastructure and Cloudflare's network, without publishing the origin's inbound application ports.
SwimNexus encrypts backup files locally before they leave the hosting PC. Microsoft OneDrive and Google Drive then provide encryption in transit and at rest for those copies.
We do not currently claim that every operational database field or the live hosting disks are independently encrypted. The confirmed encryption described here applies to website and tunnel connections and to the backup files.
SwimNexus maintains automated encrypted backups to support recovery in the event of data loss or system failure.
Backup files are encrypted before leaving our hosting infrastructure and are stored using Microsoft and Google cloud services. Both cloud-storage accounts are protected by multi-factor authentication.
Our backup and recovery process has been tested, including successful restoration of data from cloud backups.
These controls were confirmed by the system operator. They are not an independent certification, an availability guarantee or a fixed recovery time.
Backups run automatically to support recovery from data loss or system failure.
Files are encrypted locally before they leave the hosting PC.
Copies upload to Microsoft OneDrive and Google Drive, which provide encryption in transit and at rest.
Both cloud-storage accounts are protected by multi-factor authentication.
Data has been successfully restored from cloud backups, with copies recoverable for up to 30 days after deletion.
Backup locations, encryption key-management details and internal recovery procedures are not published here.
SwimNexus and the clubs that use it have different responsibilities for personal information. Understanding that split helps a club answer questions from its members and families.
The club determines why member information is collected, how it is used and what is published. It is normally responsible for its privacy notices, lawful bases and member requests.
SwimNexus processes club information to provide the contracted software services and acts in accordance with the applicable processing arrangements and the club's documented instructions.
SwimNexus may separately control information about its accounts, business relationships, support enquiries, security and service administration.
The system can hold information associated with adult swimmers, children, parents and guardians, coaches, volunteers and club officials. Depending on how a club uses SwimClubOS, this may include contact details, membership records, medical information, attendance, financial information, competition entries and performance records.
Clubs should collect only what they need and handle children's and health information with particular care. A Data Processing Agreement supports the contractual relationship; it is not consent from every club member.
Customer organisations are provided with data-processing agreements covering their use of SwimNexus services. Clubs can ask us for the current processing, security and subprocessor schedules.
For a privacy question about your own information, start with the club that holds your records. If you need SwimNexus's help or have a question about our own processing, contact [email protected].
SwimNexus aims to handle information in line with applicable UK data-protection law. This page explains the controls and responsibilities in place; it is not a legal opinion or an unqualified certification of compliance.
SwimNexus uses selected external providers to support hosting, connectivity, backup and service communication. Their roles are narrower than “everything the platform does”.
SwimNexus-controlled services and integrations chosen by a club are different arrangements. A club's own payment provider, Microsoft 365 account or email service is not automatically a SwimNexus subprocessor.
The contractual subprocessor schedule is the authoritative list for a customer agreement. It identifies which suppliers are approved for club personal data and which are pending or club-controlled.
Ask for the current processing schedules| Provider | Role in the service |
|---|---|
| Cloudflare | Website connectivity, traffic processing and network-level security. It is not the primary database or file-storage service. |
| Microsoft OneDrive | Encrypted backup storage. Microsoft provides encryption in transit and at rest. |
| Google Drive | Encrypted backup storage. Google provides encryption in transit and at rest. |
| mailbox.org | SMTP delivery of SwimNexus service email, such as account and onboarding messages. |
A provider named on this page is not necessarily a subprocessor for every category of club data. Club-connected integrations remain the club's arrangement unless the contractual schedule says otherwise.
SwimNexus is independently developed and operated.
Our security arrangements include customer data separation, controlled application access, encrypted offsite backups and tested recovery procedures.
We do not currently hold ISO 27001 or Cyber Essentials certification, and we have not yet commissioned an independent application penetration test.
We are committed to maintaining and improving our security arrangements as the platform develops.
Cloudflare, Microsoft and Google operate their own security programmes. Their certifications do not certify SwimNexus.
Prospective and existing customer organisations can request further information about the platform's security and privacy measures. We will share what is relevant and available, subject to appropriate confidentiality.
This page records the current controls, verification position and known limitations.
The controller and processor terms for a customer organisation.
The controls in place and those still unverified.
Data categories, purposes, people and controller responsibilities.
Approved providers, their roles and the status of any candidates.
How club data is exported and what happens at the end of service.
Availability depends on the current agreement and the organisation's access. Internal security procedures and confidential infrastructure details are not published.
Contact us about a suspected vulnerability, a security incident, a privacy concern, data processing or a request for security documentation. Reports will be reviewed and handled appropriately.
Use the subject line Security Report – SwimNexus when reporting a suspected vulnerability. Please avoid including passwords, encryption keys or unnecessary personal information.
Each SwimClubOS customer is resolved to its own operational database and private storage, with tenant-specific configuration and controlled user permissions. This helps keep club records separate and limits access to the people authorised for that club.
Public website connections use HTTPS/TLS, and Cloudflare Tunnel carries traffic over an encrypted connection to the hosting infrastructure. SwimNexus encrypts backup files locally before they are uploaded to Microsoft OneDrive and Google Drive, which also provide encryption in transit and at rest. We do not claim that every live database field or hosting disk is independently encrypted.
Yes. SwimClubOS uses individual accounts and role-based feature permissions. Clubs assign access according to each person’s responsibilities and can adjust permissions when those responsibilities change. The club remains responsible for keeping roles accurate and protecting account credentials.
SwimNexus maintains automated encrypted backups to support recovery. Backup files are encrypted before leaving the hosting infrastructure, both cloud-storage accounts use multi-factor authentication, and data has been successfully restored from cloud backups. These are operator-confirmed controls, not a guarantee of uninterrupted service or a fixed recovery time.
Not currently. SwimNexus does not hold ISO 27001 or Cyber Essentials certification, and an independent penetration test of the complete SwimClubOS application has not yet been commissioned. We describe the controls we operate without implying external accreditation.
We can explain the controls behind SwimClubOS, the current assurance position and the data arrangements to agree before your club moves live.
SwimNexus is still in testing. Clubs and meet hosts who help us test can get reduced pricing. Use the contact form to ask.