- Document ID
- TGP-EXT-PRIV-OP-001
- Version
- 1.4
- Effective date
- 29/10/2026
- Last updated
- 2026-10-29
- Audience
- Staff and other adults dealing with TGP
- Treatment
- Notification only
The Gymnast Portal — Operator and Platform Privacy Notice
Document ID: TGP-EXT-PRIV-OP-001 Version: 1.4 Status: Approved. Effective 29 October 2026. This notice is information. It is not a consent form and it is not accepted as a contract. Version note: Version 1.3 was never published; version 1.4 replaces it. Version 1.2 must not be reused. Earlier recorded privacy versions remain historical evidence. Controller for the purposes in section 3: The Gymnast Portal Ltd (“TGP”), company number 17513228, registered office 3 Ridge Crescent, Hawk Green, Marple, Stockport, Cheshire, SK6 7JA, United Kingdom. Website: https://thegymnastportal.com/ Application: https://app.thegymnastportal.com/ ICO registration number: ZC272180 (data protection fee register). Privacy contact: privacy@thegymnastportal.com Complaints: complaints@thegymnastportal.com Director and Privacy Lead: Neil Walker Data protection officer: None appointed. TGP has not appointed a data protection officer under UK GDPR Article 37. The Director and Privacy Lead is responsible for data protection, and privacy questions go to the privacy mailbox.
1. Controller and processor
Your club is normally the controller of athlete, parent, coaching, attendance, welfare and similar club records. TGP processes those records for the club under the Club Data Processing Agreement. The club’s own privacy information describes that processing. TGP does not become the controller of those records merely by hosting them.
TGP is the controller for the activities in section 3, which are TGP’s own purposes.
2. Who this notice is for
Club staff, club administrators, and other adults who deal with TGP directly. Parents and children should read the parent/guardian notice and the child-friendly notice. Those layers match this version’s facts. They do not repeat every clause.
3. TGP’s purposes, information and lawful bases
Each row is one purpose. Bases are not a menu of options.
| Purpose | Information | Lawful basis |
|---|---|---|
| Enter and manage the contract with a club, including the free pilot | Business contact name, email, role, club name, acceptance record (document ID, version, hash, time, user and club) | Article 6(1)(b) — contract, or steps requested before a contract |
| Provide a user account so an authorised person can sign in | Name, email, role, club identifier, authentication events | Article 6(1)(b) where the person is accepting terms with TGP; Article 6(1)(f) where the account exists because the club asked TGP to provision a staff user and TGP must secure that account. The legitimate interest is keeping the service available only to authorised people. |
| Secure the service, investigate misuse and keep audit records of sensitive administrative actions | Log-on events, club and role, security events, limited technical diagnostics | Article 6(1)(f) — legitimate interests in securing a service that holds children’s data. People may object. TGP will stop if the person’s interests override those interests, unless there is a compelling legal ground. |
| Respond to support and privacy requests | Contact details, the request, and the minimum account context needed to answer | Article 6(1)(b) if it is part of the service contract; otherwise Article 6(1)(f) to handle the request the person has made |
| Meet legal duties (tax, accounting, regulatory enquiries, claims) | The minimum records those duties require, which may include acceptance evidence and invoices if billing exists | Article 6(1)(c) where the law requires it |
| Send a service notice about the account, security or a change to terms | Name, email, and the notice | Article 6(1)(b) or, for a legal or security notice, Article 6(1)(c) or 6(1)(f) |
TGP does not use club athlete records for TGP’s own marketing under this notice.
Optional marketing-site analytics are outside this notice. They belong to the marketing-site cookie policy, not the app policy.
4. Special-category data
TGP’s own purposes in section 3 are not intended to use special-category data.
Where a club stores health, welfare or similar information, including medical notes and additional support needs (SEN) markers and notes, which are special-category data, the club is the controller and must have its own Article 9 condition. TGP processes it only on the club’s instruction under the DPA.
No AI feature sends safeguarding narratives, medical, injury or menstrual information, or individual sensitive welfare information to the AI provider. Ask the Portal never sends energy, soreness or check-in wellness information. AI Insights may send pseudonymised energy and soreness trend bands, only as described in section 5. Those exclusions are product rules, not an Article 9 condition chosen by TGP for the club.
5. AI features and Google Cloud
The service has two optional AI features for club staff. Each is off by default. TGP switches a feature on for a club only after an authorised club representative has asked for it in writing, and keeps a record of that request. Each staff user must accept the Staff AI Acceptable Use Terms before their first use of either feature.
- Ask the Portal is a read-only assistant. Authorised staff ask questions about records they may already see. The service sends the question and a minimised, pseudonymised extract of permitted records to Google Cloud Vertex AI. Energy, soreness and check-in wellness information is never sent.
- AI Insights gives a coach or club administrator a short summary about one athlete, or an overview of the athletes they coach. For one athlete, Google receives a temporary reference instead of the name, attendance and progress counts, whether energy and soreness are higher or lower than the athlete's own usual level (only where the club has recorded an Article 9 condition and any permission it needs), the number of check-ins covered, and basic training context. Overviews contain aggregate counts only, with no names, identifiers or wellness information.
For both features:
- Roles. The club is the controller and TGP is its processor. TGP is a controller only for the minimum usage records needed for security, quota and billing.
- Pseudonymised is not anonymous. The information sent can still relate to a child and is personal data. Energy and soreness trends may be data concerning health.
- Never sent. Names, dates of birth, stable identifiers, contact details, medical, injury, menstrual or safeguarding information, free-text notes and media.
- Provider. Google Cloud Vertex AI processes each request as TGP's subprocessor, authenticated with a service identity rather than an API key. Google does not use the requests to train its models. Under its standard terms Google may log prompts for a limited period to detect abuse. TGP will not use either feature with real personal data until Google's processing terms, the region and the provider settings for TGP's project are verified and recorded.
- Staff questions are personal data of the staff member, and of anyone the question identifies.
- Output. AI output can be wrong. It supports staff; a person makes every decision. There is no automated decision-making with a legal or similarly significant effect. AI output is not shared with parents or gymnasts in this version, and they cannot use either feature.
- Storage. TGP does not store AI output, questions or provider payloads after they are shown. A usage record (feature, date, outcome, token counts and a random request ID, with no content) is kept for 6 months.
- Lawful basis. The club decides its lawful basis. A club switching a feature on, or a staff member accepting staff terms, is not consent from athletes or parents.
6. Categories the club asks TGP to host
For transparency, club records may include identity, contacts, roles and staff permission settings, groups (including extra groups and session drop-ins), attendance across groups, progression, levels achieved and certificates (including reports that authorised staff can export as CSV), competition results and routine deductions, guardian links, messages, profile photos, and short-lived training video and photo highlights. Staff access follows role defaults that a club administrator can change for one person; assistant coaches have read-only access to medical and SEN information by default. Welfare and safeguarding records, where the club uses them, are restricted. The club’s notice is the controller’s explanation of those categories. TGP’s DPA limits what may be sent to the AI provider.
7. Recipients and subprocessors
Recipients for the purposes above may include:
- Google Cloud / Firebase, for hosting, authentication, database and file storage;
- Google Cloud Vertex AI, only for a request from an AI feature switched on for the club;
- the email provider used to deliver service email;
- professional advisers or authorities where the law requires it.
Marketing-site Google Analytics 4 and Microsoft Clarity are not recipients of app club records under this notice. Stripe and error-monitoring tools are not described as current recipients of club personal data.
TGP does not sell personal information.
8. International transfers
Google and the email provider may process information outside the UK. The database is in London and the application runs in the Netherlands. Stored files are kept in the United States, and two background functions (the website enquiry handler and an account set-up step) run in the United States. A restricted transfer is made only where a transfer mechanism recognised by UK data-protection law applies to the account and route in use. TGP records which mechanism applies before real personal data uses that route, and will tell you on request.
Questions: privacy@thegymnastportal.com.
9. Retention
TGP keeps information for the category and period in its retention schedule, and not “for as long as useful” as a general rule.
| Category | How long, in this version |
|---|---|
| Terms, privacy-notice and DPA acceptance evidence | 6 years after the club's account is closed. |
| Records of a club's request to switch an AI feature on or off | The end of the club's relationship with TGP plus 7 years. |
| AI usage records (no content) and AI Insights feedback (rating and fixed reason code only) | 6 months, then deleted automatically when the record's expiry date passes. |
| Security and audit events | For the security period in the retention schedule, then deleted or minimised. When a person's records are erased, their identifying details in audit logs are replaced with a pseudonymous reference. |
| Erasure requests and receipts | Kept as evidence of how each request was handled. They contain no erased personal data. |
| Support requests | For the period needed to resolve the request and handle a follow-up or complaint. |
| AI questions, answers and insights | Not stored by TGP after they are shown. Provider-side logging for abuse detection is described in section 5 and is not zero. |
| Backups | Taken daily and kept for 30 days, then deleted. Not used day to day. |
| Club athlete records | Kept on the club’s instruction, then returned or deleted under the DPA. |
A legal hold, security investigation or safeguarding need can keep a restricted copy for longer. That copy is not used for ordinary coaching. Safeguarding, injury and welfare case records are never deleted automatically; a person reviews them first.
Deletion requests are completed within 30 days of a valid request. Each request is tracked against its deadline, and a receipt records what was deleted, what was kept and why. When a club leaves, it is offered an export of its records before they are deleted.
10. Children
Children’s club records are controlled by the club. TGP still designs the service with children’s interests in mind: default access is limited, parents and gymnasts are not in the AI pilot, and prohibited sensitive topics are refused rather than sent to the model.
Read the child-friendly notice and the parent/guardian notice.
11. Rights
Depending on the purpose, a person may ask to access, correct, erase, restrict or receive a copy of their information, and may object to processing based on legitimate interests. Rights are not absolute. Where the club is the controller, TGP will help the club and will usually direct the person to the club.
Email privacy@thegymnastportal.com. TGP may ask for enough information to confirm identity and authority.
12. Complaints
Contact complaints@thegymnastportal.com first if you want TGP to look at the issue.
You can complain to the Information Commissioner’s Office: https://ico.org.uk/make-a-complaint/ and helpline details published by the ICO.
13. Cookies
App storage is described in the App Cookie and Local Storage Policy. That policy does not cover the marketing website.
14. Changes
Material changes to this notice are a new immutable version. People are notified. Notification is not consent. Historical versions stay available for the acceptance or notification record that cited them.
Document control
| Field | Value |
|---|---|
| Document ID | TGP-EXT-PRIV-OP-001 |
| Document type | Privacy notice |
| Jurisdiction | England and Wales; UK GDPR and Data Protection Act 2018 |
| Classification | Public |
| Applicable audience and roles | Club staff, operators and other adults dealing with TGP |
| Acceptance treatment | Notification only |
| Version | 1.4 |
| Effective date | 29 October 2026 |
| Status | Approved |
| Review date | 17 April 2027, or earlier on a material change |
| Public URL once published | https://app.thegymnastportal.com/legal/privacy |
| Material-change classification | Material candidate against earlier recorded versions |
| Reacceptance on publication | No. Notification or information only |
Version history:
| Date | Version | Change |
|---|---|---|
| 8 October 2026 | 1.3 draft | Canonical draft created. |
| 17 October 2026 | 1.3 draft | Organisation identity corrected; AI coaching insights explained. |
| 18 October 2026 | 1.3 draft | Hosting locations, AI supplier and AI controls updated. |
| 19 October 2026 | 1.3 draft | Consolidated after independent review: one AI section for both features; staff terms needed before either feature; region and transfer mechanism no longer stated as verified; retention periods stated; internal identifiers removed. No earlier version has been accepted or relied on, so the version number is kept and the content hash identifies this text. |
| 29 October 2026 | 1.4 draft | Approval line changed to name the Director and Privacy Lead; effective date left to be set at publication. Version 1.4 drafted: new club record categories; SEN as special-category data; acceptance evidence kept 6 years after account closure; erasure process; audit-log pseudonymisation; planned backups; AI usage and feedback expiry |
| 29 October 2026 | 1.4 | Approved by the Director and Privacy Lead and published, effective 29 October 2026. Approval line names The Gymnast Portal Ltd. Backups now enabled (daily, kept 30 days). |
Approved by The Gymnast Portal Ltd (Neil Walker, Director and Privacy Lead).