The Gymnast Portal / Legal

Approved
Version 1.4Effective 29/10/2026
Document ID
TGP-EXT-DPA-001
Version
1.4
Effective date
29/10/2026
Last updated
2026-10-29
Audience
Authorised club representative
Treatment
Contractual acceptance

The Gymnast Portal — Club Data Processing Agreement

Document ID: TGP-EXT-DPA-001 Version: 1.4 Status: Approved. Effective 29 October 2026. Version note: Version 1.3 was never approved, published or accepted; version 1.4 replaces it. Version 1.2 must not be reused. The application previously recorded version 1.2 against older wording. Historical DPA acceptance rows are kept and are not rewritten. Controller: The club identified in the electronic acceptance record (the “Club”). Processor: The Gymnast Portal Ltd (“TGP”), company number 17513228, registered office 3 Ridge Crescent, Hawk Green, Marple, Stockport, Cheshire, SK6 7JA, United Kingdom. ICO registration number (TGP): ZC272180 (data protection fee register). Incorporated by: Club SaaS Terms TGP-EXT-SAAS-001.

This agreement is the documented processing contract required by UK GDPR Article 28. It is not legal advice.

1. Parties and roles

1.1 The Club is the controller of Club personal data that it, or its authorised users, enter or instruct TGP to process for the Club’s gymnastics activities.

1.2 TGP is the processor of that data, except for the separate purposes described in the Operator Privacy Notice, where TGP is an independent controller (for example the security of the service, its contracting and acceptance records, minimum usage metadata for quota and abuse control, and its own legal duties). Those purposes do not allow TGP to use Club athlete records for its own marketing, product experiments or model training.

1.3 TGP will process Club personal data only on documented instructions from the Club, including for transfers outside the UK, unless UK law requires otherwise. If UK law requires processing, TGP will tell the Club first unless the law prohibits that notice.

1.4 If TGP considers an instruction unlawful, it will tell the Club promptly and will not follow that instruction until it is withdrawn or confirmed in a way TGP can lawfully carry out.

2. Subject matter, nature, purpose and duration

2.1 Subject matter: Hosting and operating The Gymnast Portal so the Club can administer athletes, guardians, staff and related club records.

2.2 Nature: Storage, retrieval, display, access control, transmission to authorised subprocessors, backup (section 14.9), support, and, only where the Club has asked for an AI feature and it has been activated under Schedule 4, the AI processing described in that schedule.

2.3 Purpose: The Club’s gymnastics administration, including accounts; groups, extra groups and one-off session drop-ins; attendance across all of an athlete’s groups; coaching progression, levels achieved, certificates and levels-achieved reports (including CSV export by authorised staff); competition results and routine deductions; short-lived training video and photo highlights; communications the product provides; and optional staff assistance. TGP does not decide selection, progression, medical care or safeguarding outcomes.

2.4 Duration: For the term of the Club SaaS Terms and afterwards only as section 14 (deletion or return) and any legal hold require.

3. Data subjects and categories

3.1 Data subjects may include child and adult athletes, parents and guardians, coaches and other club staff, and the Club’s administrators.

3.2 Categories may include identity and contact data, role and account data, staff permission settings, group membership (main group, extra groups and session drop-ins), attendance, squad and progression records, levels achieved and certificates, competition results and routine deductions, guardian relationships, media the Club chooses to upload (profile photos and short-lived training video and photo highlights), booking references where that module is used, erasure request records, and audit events.

3.3 Special-category data may exist in Club records. It includes medical notes, injury records, menstrual information and additional support needs (special educational needs, “SEN”) markers and notes, which are treated as special-category data (data concerning health). Safeguarding case narratives and individual sensitive welfare information may also exist in Club records and are handled with the same restrictions. None of it is sent to an AI provider, except the energy and soreness trend bands described in Schedule 4 for AI Insights, under the conditions set out there. The Club remains responsible for its Article 9 conditions and safeguarding duties. TGP does not choose those conditions for the Club.

4. Controller rights and obligations

4.1 The Club will:

  • make sure it has a lawful basis, and an Article 9 condition where one is required;
  • collect, classify and submit personal data and media to the service lawfully, including any media permissions it relies on;
  • give people the privacy information that applies to them, including parent and child layers where children are involved;
  • keep its instructions lawful and within what the product can actually do;
  • authorise only the staff who should use each AI feature;
  • respond to data-subject requests, using TGP’s assistance under section 11.

4.2 The Club may request the information needed to show compliance with Article 28, as set out in section 15.

5. Documented instructions

5.1 The Club’s instructions are: these clauses and their schedules, the Club SaaS Terms, the settings the Club chooses in the product, a recorded request by an authorised Club representative to activate an AI feature (Schedule 4), and written instructions from an authorised Club representative to privacy@thegymnastportal.com or support@thegymnastportal.com.

5.2 A setting or prompt typed by a user is not an instruction to ignore this agreement. Staff prompts cannot authorise prohibited data to be sent to an AI provider.

5.3 TGP will not follow an instruction that would send another club’s records, or that would treat a descriptive role marker as a grant of club-wide access.

5.4 Staff permissions. Each staff role (club administrator, head coach, coach and assistant coach) has default permissions. A Club administrator may grant or withdraw individual permissions for one staff member; each change is recorded in the audit log. These settings are the Club’s instructions on staff access. By default, assistant coaches have read-only access to medical notes, first-aid information and SEN support for the athletes they can see, and cannot change them; the Club may withdraw that access. Staff see athletes in their own groups (main and extra groups) and athletes added to their sessions as drop-ins; drop-in access ends automatically after the session day. The service enforces these permissions on the server.

6. Confidentiality

6.1 TGP will make sure that people it authorises to process Club personal data are under a confidentiality duty, by contract or by law.

6.2 Access is limited to people who need it for the instructed service, security, or a legal duty.

7. Article 32 security

7.1 TGP will implement measures appropriate to the risk, including:

  • encryption in transit and encryption at rest provided by the production cloud service;
  • access control based on authentication, club tenancy, role and, where the product applies it, assignment;
  • least privilege for operator access;
  • separation between clubs so one club’s users are not authorised to read another club’s records;
  • audit of sensitive administrative actions, including every AI feature activation and deactivation;
  • a process to restore availability after an incident, within the limits of the cloud service actually configured;
  • review of these measures when a material supplier or feature change occurs.

7.2 These measures are not a statement that a particular penetration test or uptime percentage has been achieved. The backup arrangement is described in section 14.9. TGP will tell the Club, on request, which backup and recovery configuration is in place for the production service at that time.

8. Subprocessors and change notification

8.1 The Club gives a general written authorisation for the subprocessors in Schedule 2, on the conditions stated there.

8.2 TGP will give the Club at least 30 days’ written notice before adding or replacing a subprocessor that will process Club personal data, except where an emergency replacement is needed to keep the service secure. In an emergency, TGP will tell the Club as soon as it reasonably can and explain why. The Club may object on reasonable data-protection grounds within the notice period; the parties will then discuss the concern in good faith and, if it cannot be resolved, the Club may end the affected service without penalty.

8.3 The Club may object on reasonable data-protection grounds within the notice period. If the objection cannot be resolved, the Club may stop the affected processing or end the pilot. TGP will not treat silence as a waiver of the right to object.

9. Equivalent subprocessor terms

9.1 TGP will impose data-protection obligations on each subprocessor that are the same in substance as those in this agreement, as required by Article 28(4).

9.2 TGP remains fully liable to the Club for the subprocessor’s performance of those obligations.

10. International transfers

10.1 Some subprocessors process personal data outside the UK. Schedule 2 states, for each service, where processing takes place.

10.2 TGP will make a restricted transfer only where a transfer mechanism recognised by UK data-protection law applies to the account and route in use, and will record which mechanism applies. Until that record exists for a route, TGP does not rely on that route for real Club personal data. On request, TGP will give the Club the current record. TGP uses Google Cloud and Firebase under the Google Cloud Platform Terms of Service (https://cloud.google.com/terms) and the Firebase terms (https://firebase.google.com/terms), together with Google's Cloud Data Processing Addendum (https://cloud.google.com/terms/data-processing-addendum) and the Firebase Data Processing and Security Terms (https://firebase.google.com/terms/data-processing-terms). For a UK billing address, Google's contracting entity is Google Cloud EMEA Limited, Dublin, Ireland (https://cloud.google.com/terms/google-entity), and the UK recognises Ireland as adequate. For the processing in the United States listed in Schedule 2 (stored files, the two named functions and any Google support access), Google relies on the UK Extension to the EU-US Data Privacy Framework (https://cloud.google.com/terms/alternative-transfer-solution), with the standard contractual clauses in Google's terms as the fallback. Google's subprocessors are listed at https://cloud.google.com/terms/subprocessors and https://firebase.google.com/terms/subprocessors, and its locations at https://cloud.google.com/about/locations.

10.3 TGP will not describe a transfer as covered by UK adequacy regulations unless that position is recorded against the route actually used.

11. Rights-request assistance

11.1 Taking into account the nature of the processing, TGP will assist the Club by appropriate technical and organisational measures, so far as possible, to respond to requests to access, correct, erase, restrict, port or object. This includes recording each erasure request and its deadline in the service, and finding the AI usage records, AI Insights activation and Ask the Portal activation records, and wellness permission records that relate to a person.

11.2 TGP will pass on a request it receives directly about Club personal data without undue delay, unless the law requires otherwise. TGP does not decide the Club’s response.

12. Breach assistance

12.1 TGP will notify the Club without undue delay after becoming aware of a personal-data breach affecting Club personal data.

12.2 The notice will include, so far as it is known, the nature of the breach, categories and approximate numbers of people and records, likely consequences, and measures taken or proposed. TGP may send this in stages if facts are still being established.

12.3 The Club decides whether to notify the ICO or data subjects, except where TGP has its own legal duty as a controller for its independent processing.

13. Articles 32 to 36 assistance

13.1 TGP will assist the Club in meeting its obligations under Articles 32 to 36, taking into account the nature of processing and the information available to TGP.

13.2 That assistance includes reasonable help with security questions, breach notifications, data-protection impact assessments (including for the AI features in Schedule 4), and prior consultation with the ICO where Article 36 applies to the Club’s processing.

13.3 TGP’s internal assessments are evidence for TGP. They are not a substitute for the Club’s own assessment where the Club must complete one.

14. Deletion or return

14.1 At the end of the service, the Club may choose return of an agreed export and then deletion, or deletion without return.

14.2 TGP will complete deletion of the Club personal data from active production systems within 30 days of a valid written instruction from the Club, subject to any UK law that requires storage and to documented legal, safeguarding or security holds. Where a hold applies, TGP will tell the Club which category of records is held and why, unless the law prevents it. TGP will confirm in writing when deletion from active production systems is complete.

14.3 Individual erasure requests. Where the Club instructs TGP to erase an individual’s records (for example after a request from a parent, athlete or staff member), the same 30-day period applies from the valid instruction.

14.4 Request tracking. Each erasure instruction is recorded in the service with the date received, the 30-day deadline and its current status. TGP monitors open requests and is alerted before a deadline is reached.

14.5 Receipts. When an erasure is completed, TGP produces a receipt recording what was deleted, what was kept and why, and when. The receipt does not contain the erased personal data. The Club may ask for a copy.

14.6 Records held for manual review. Safeguarding records, injury records and welfare or case records are never deleted automatically. They are held, with restricted access, and reviewed by a person against the Club’s safeguarding and legal duties before any deletion. Section 14.2 applies to the notice the Club receives about the hold.

14.7 Audit logs. Audit logs are not deleted as part of an erasure. The erased person’s identifying details in them are replaced with a pseudonymous reference, so the log still shows what happened without identifying the person.

14.8 Club offboarding. When the Club’s service ends, TGP first offers the Club an export of its records. Deletion of the Club’s records goes ahead after the export has been provided, or after the Club confirms in writing that it does not want one. Records of legal acceptances (terms, DPA and privacy acceptance evidence) are kept for 6 years after the Club’s account is closed and are then deleted.

14.9 Backups. Backups are not used for ordinary access. Backups of the production database are taken daily and kept for 30 days, after which they expire. Personal data that remains in a backup after deletion from active production systems stays protected, is not restored into ordinary use, and expires with that backup. If a backup is ever restored, the Club’s deletion instructions are reapplied before the restored data is used.

14.10 Acceptance evidence, AI feature activation records, security logs and records under a legal hold may be kept in restricted form for the periods in Schedule 3. They are not a copy of the live club database for continued coaching use.

15. Audit and compliance information

15.1 TGP will make available to the Club all information necessary to demonstrate compliance with Article 28 and will allow for and contribute to audits, including inspections, conducted by the Club or an auditor it mandates.

15.2 TGP will meet the Club's audit rights by providing, on request, the documents and written information reasonably needed to show compliance with this Agreement (for example policies, records and independent reports). The Club may make such a request at most once in any 12-month period, except where a personal data breach has occurred or where the law or a regulator requires more. Requests must be reasonable in scope and timing, protect other clubs' data and TGP's security, and must not require disclosure of another customer's records.

15.3 The Club will give reasonable notice unless a breach investigation makes notice unsafe.

16. Term

16.1 This agreement starts when an authorised Club representative accepts this version and continues while the Club SaaS Terms are in force, and afterwards for deletion, return and legal holds.

17. Liability

17.1 Each party's liability arising under or in connection with this agreement is subject to clause 13 of the Club SaaS Terms and counts towards the caps in that clause. The caps are mutual: they apply equally to each party's aggregate liability to the other arising under or in connection with this agreement. This agreement does not create a separate or additional cap.

17.2 Claims for breach of this agreement, of applicable data-protection obligations, of confidentiality or of information-security obligations are Enhanced Claims under clause 13.7 of the Club SaaS Terms. They are subject only to the Enhanced Cap: the greater of £10,000 and 200% of the Charges paid or payable by the Club during the 12 months immediately preceding the event giving rise to the claim. They are not subject to, and do not count towards, the General Cap in clause 13.6 of those Terms (the greater of £5,000 and 100% of those Charges). During a free pilot the Charges are nil, so the Enhanced Cap is £10,000.

17.3 Liability follows each party's own breach (clause 13.3 of the Club SaaS Terms). The Club is responsible for its obligations as controller under sections 1.1, 3.3 and 4, including the lawful collection, classification and submission of personal data and media. TGP is responsible for its processor obligations under sections 1.3, 1.4 and 5 to 15, including the security measures in section 7, and for its obligations as an independent controller for the purposes in section 1.2. The Club is not liable merely because a claim involves personal data or media uploaded to the service.

17.4 Clauses 13.1 (liability that cannot be limited, for both parties), 13.5 (breach-response costs), 13.8 (how the caps apply, including the rule that a claim is not recovered under both caps and that any contractual indemnity falls within the relevant cap), 13.9 (only Charges properly due, VAT or taxes on them, contractual interest properly due on overdue Charges and repayment of a clearly identified accidental overpayment are outside the caps; damages, compensation, indemnity, reimbursement, breach-response costs and other sums arising from a claim or breach stay within the applicable cap), 13.10 (Charges) and 13.11 (ceilings, not payments) of the Club SaaS Terms apply to this agreement. The caps are maximum limits of liability, not payments due because an incident occurs.

17.5 These caps limit only the parties' liability to each other and do not alter either party's statutory responsibilities as controller or processor. They do not limit or affect any data subject's rights, including compensation under Article 82 UK GDPR, the powers of the Information Commissioner or any other regulator or court, or any regulatory fine or penalty to the extent it cannot lawfully be limited by contract.

18. Governing law

18.1 This agreement is governed by the law of England and Wales. The courts of England and Wales have exclusive jurisdiction, subject to any non-excludable data-protection right to complain to the ICO.

19. Electronic acceptance

19.1 An authorised Club representative accepts this agreement for the Club. The server stores a new acceptance row. It does not overwrite earlier rows. Privacy information is not this acceptance.

Schedule 1 — Contacts

RoleContact
TGP privacyprivacy@thegymnastportal.com
TGP securitysecurity@thegymnastportal.com
TGP safeguarding mailboxsafeguarding@thegymnastportal.com
TGP supportsupport@thegymnastportal.com
TGP complaintscomplaints@thegymnastportal.com
Director and Privacy LeadNeil Walker
Data protection officerNot appointed

The Club’s privacy and safeguarding contacts are the contacts the Club records on its account. They are not written into this agreement as if every club shared one address.

Schedule 2 — Authorised subprocessors

SubprocessorWhat it may processWhereConditions
Google Cloud / Firebase (Authentication, Firestore, Cloud Storage, App Hosting, Cloud Functions and related service logs)Club personal data stored in the production serviceDatabase: London, United Kingdom. Application hosting: the Netherlands (EU). Stored files (photos, video and documents): United States. Two background functions (website enquiry handling and an invitation identity mirror): United States. Other background functions: London, United KingdomProcessing in the United States is a restricted transfer. Section 10.2 applies: the route is not used for real Club personal data until the transfer mechanism and the Google data-processing terms that apply to TGP’s account are recorded
Google Cloud Vertex AI (Gemini models)Only the minimised, pseudonymised AI payloads described in Schedule 4, and only for a Club where that feature has been activatedRequired configuration: a Vertex AI regional endpoint in the European Union (europe-west4, the Netherlands). This configuration must be verified on the live service before any real Club personal data is sentAuthenticated with a service identity, never with a static API key. The consumer Gemini Developer API and any static-key fallback are prohibited for Club personal data. Not used for real personal data until the conditions in Schedule 4, paragraph 4.9 are met
Email delivery provider (Resend, Plus Five Five, Inc., United States)Name, email address and the message content needed to send service emailUnited StatesRestricted transfer; section 10.2 applies. Not a store of athlete records or special-category data

The following are not authorised subprocessors for Club personal data: marketing-site analytics (Google Analytics 4 and Microsoft Clarity, which are not loaded in the application), Stripe, Sentry (unless a later version adds it after configuration evidence), and device speech-recognition services. Browser dictation, where offered, is not a TGP subprocessor unless audio leaves the device. Users are told not to dictate safeguarding narratives.

Schedule 3 — Retention

CategoryPeriod
Club operational records (identity, membership, groups and drop-ins, attendance, progression, levels achieved and certificates, competition results and routine deductions, messages, media)As the Club instructs while the service is in use, then deleted or returned under section 14
Medical notes and SEN markers and notes (special-category data)Kept with the athlete’s record for as long as the Club keeps that record, and removed sooner when the Club removes them
Training video and photo highlightsA short period set by the Club, between 14 and 45 days (45 days unless the Club chooses less), then deleted automatically
AI usage records (metadata only: date, feature, outcome, token counts, a random request ID; no prompts, responses or wellness information)6 months from the event. Each record carries an expiry date and is deleted automatically once it expires
AI Insights feedback (a coach’s rating of an insight and, optionally, one fixed reason code; no free text, prompt, AI output or wellness information)6 months from the feedback. Each record carries an expiry date and is deleted automatically once it expires
AI feature activation and deactivation records (both features)The end of the Club’s relationship with TGP plus 7 years, as evidence of the Club’s instruction
Wellness permission records and their history (granted, refused, withdrawn)While the athlete is registered with the Club; then 6 years after the permission ended or the athlete left, unless the Club instructs a different period
AI Insights output, prompts and provider payloadsNot stored by TGP. Shown only for the current view
Ask the Portal questions and answersNot stored by TGP after the conversation ends
Acceptance and notification evidence6 years after the Club’s account is closed (section 14.8)
Security and audit logsAs set in TGP’s internal retention schedule, and no longer than needed for security and accountability. On erasure, identifying details are pseudonymised (section 14.7)
Erasure requests and receiptsKept as evidence of how the request was handled; they contain no erased personal data
Safeguarding, injury and welfare case recordsHeld for manual review; never deleted automatically (section 14.6)
BackupsTaken daily and kept for 30 days (section 14.9)

Training video and photo highlights are short-lived. The period is set by the Club’s configuration of that feature and is shown in the product.

Schedule 4 — AI processing

4.1 Scope. This schedule covers two separate AI features that TGP runs as the Club’s processor. The Club is the controller for both.

ItemA. Ask the PortalB. AI Insights (coach insights and squad overviews)
PurposeRead-only answers for authorised staff about records they are allowed to seeShort coaching decision-support summaries about one athlete, or a squad overview, for the requesting coach or club administrator
Who may use itStaff in eligible roles, for athletes they are currently authorised and, where assignment applies, assigned to accessThe same
Sent to the providerThe staff question and pseudonymised operational evidence the product allowsAthlete insight: a temporary per-request reference; attendance and progress counts; energy and soreness trend bands relative to the athlete’s own baseline, only under paragraph 4.5; the observation period and count; a completeness warning; minimal training context. Squad overview: aggregate counts only, with no names, identifiers or wellness information
Never sentName, date of birth, stable identifiers, contact and payment data, safeguarding narratives, medical, injury or menstrual information, individual sensitive welfare information, free-text and unrestricted notes, media, other clubs’ records, and any individual energy, soreness or check-in wellness dataThe same, except the trend bands permitted by paragraph 4.5
OutputNot stored by TGP after the conversationNot cached or stored by TGP; shown only for the current view; never written to the athlete’s record
DecisionsDecision support only. No automated decision-makingThe same

4.2 Separate controls. The following controls are separate. None stands in for another, and none is consent from an athlete, parent or staff member.

ControlWho sets itEffect
System-wide AI availabilityTGP, through server settings: a master AI switch and a separate switch for each featureWhen a switch is off, no AI request of that kind is made for any club
Per-club activation of Ask the PortalA TGP system administrator, only after a recorded request from an authorised Club representative (paragraph 4.3)Lets the Club’s eligible staff use Ask the Portal. Off by default. Does not affect AI Insights
Per-club activation of AI InsightsA TGP system administrator, only after a recorded request from an authorised Club representative (paragraph 4.3)Lets the Club’s eligible staff use AI Insights. Off by default. Does not affect Ask the Portal
Staff AI terms acceptanceEach staff user, before first use of either featureRecords that the user accepts the Staff AI Acceptable Use Terms (TGP-EXT-AUP-001). Without it, neither feature runs for that user
Lawful basis and Article 9 conditionThe Club, as controller, recorded in the Club’s AI settingThe Club’s Article 6 basis for each feature and, for wellness trend bands, its Article 9 condition
Athlete wellness permissionRecorded by a Club administrator where the Club relies on explicit consentAllows trend bands for that athlete only. Refusal or withdrawal stops future use

4.3 Activation request. Each feature is off by default for every club. A TGP system administrator switches a feature on only after an authorised Club representative has asked for it in writing (email, signed letter, in-app message or minuted meeting). TGP keeps an activation record that cannot be edited or deleted through the application. It holds: the requesting representative; the Club; the representative’s authority or role; the versions of the Club SaaS Terms, this agreement and the Club AI Enablement Information that apply; when the request was made; when the feature was switched on; the TGP administrator who did it; and the feature state before and after. The Club may ask TGP to switch a feature off at any time. Switching off does not need a formal request and is recorded in the same way.

4.4 Staff acceptance. Each staff user must accept the Staff AI Acceptable Use Terms before their first use of either feature. Acceptance is a condition of use. It is not the Club’s instruction and not consent from athletes or parents.

4.5 Wellness trend bands (AI Insights only). Energy and soreness trend bands are personal data and may be data concerning health. They are pseudonymised, not anonymous. They are sent only if the Club has recorded an Article 9 condition in its AI setting. If the Club relies on explicit consent, they are sent only for athletes with a current granted permission record. If no condition is recorded, or permission is absent, refused or withdrawn, the bands are withheld and the rest of the insight runs without them; the model is told not to mention or infer wellness. Withdrawal stops future AI wellness processing.

4.6 Server-side minimisation. The browser sends only the athlete reference. TGP’s server checks the user’s identity, club membership, role and current assignment before it reads any record. It builds the minimised payload itself and rejects any field outside the allow-list, and any value that looks like a name, date, email address, phone number or free text.

4.7 Use of output. Outputs can be incomplete, wrong or biased. Club staff remain responsible for every decision. Outputs must not be used as the only basis for progression, selection, training-load, injury, medical, safeguarding, disciplinary or performance decisions. In this version, AI outputs must not be shared with, shown to or sent to parents or gymnasts.

4.8 Logs and caching. Prompts, responses and wellness information are not written to application logs, error monitoring, analytics or AI usage records. TGP does not cache athlete AI output in server memory, the database or the browser, and never creates a provider-side context cache. Google’s provider-side implicit caching for the Vertex AI project must be disabled before real Club personal data is sent.

4.9 Conditions before real Club personal data is used with either feature. TGP will not activate either feature for a Club’s real personal data until all of the following are recorded: (a) the Vertex AI project, model, regional endpoint and runtime identity verified on the live service as stated in Schedule 2; (b) Google’s data-processing terms and the transfer mechanism that apply to TGP’s account; (c) provider-side implicit caching disabled; (d) Google’s abuse-monitoring position for the model in use, including whether prompts may be logged and whether an exception has been requested or granted; (e) the Club’s recorded activation request under paragraph 4.3.

4.10 No training and no other use. TGP does not use Club personal data, prompts or outputs to train or fine-tune models, and does not permit Google to do so under the terms that apply to TGP’s account.

4.11 TGP as independent controller. TGP is an independent controller only for the minimum usage metadata needed for security, quota and billing, as described in the Operator Privacy Notice.

4.12 Material change. Widening the data sent to the provider, adding another AI feature, changing the AI provider or region, or giving parents or gymnasts access to AI features or outputs is a material change. It requires a new version of this agreement and fresh acceptance.

Document control

FieldValue
Document IDTGP-EXT-DPA-001
Document typeContract (UK GDPR Article 28 processing agreement)
JurisdictionEngland and Wales; UK GDPR and Data Protection Act 2018
ClassificationContractual
Applicable audience and rolesClub authorised representative
Acceptance treatmentClub representative accepts electronically
Version1.4
Effective date29 October 2026
StatusApproved
Review date17 April 2027, or earlier on a material change
Public URL once publishedhttps://app.thegymnastportal.com/legal/dpa
Material-change classificationMaterial against every earlier recorded version
Reacceptance on publicationYes, for the exact version and content hash once approved

Version history:

DateVersionChange
8 October 20261.3 draftCanonical draft created.
17 October 20261.3 draftOrganisation identity corrected; AI Insights added as a separate purpose; wellness controls described.
18 October 20261.3 draftHosting locations, AI provider, AI controls and liability added.
19 October 20261.3 draftConsolidated after independent review into one current text: a single AI processing schedule (Schedule 4) for Ask the Portal and AI Insights; per-feature activation by recorded Club request for both features; staff acceptance required before either feature; required Vertex AI region stated as a condition, not as a verified fact; retention periods set (Schedule 3); subprocessor notice period, deletion timing, audit and transfer clauses tightened. Final consistency corrections: deletion from active production systems completed within 30 days of a valid written instruction, subject to law and documented holds; backup wording made conditional on backups being enabled; AI Insights feedback limited to a rating and a fixed reason code; liability section 17 aligned with the Club SaaS Terms (Enhanced Cap the greater of £10,000 and 200% of Charges; not counted towards the £5,000 General Cap; no separate DPA cap; caps mutual and cover each party's aggregate liability under or in connection with this agreement; narrowed payment carve-out cross-referred; liability follows each party's own breach, consistent with the roles in sections 1 to 4; section 4.1 states the Club's duty to collect, classify and submit personal data and media lawfully). No earlier version has been accepted, so the version number is kept and the content hash identifies this text.
29 October 20261.4 draftApproval line changed to name the Director and Privacy Lead; effective date left to be set at publication. Version 1.4 drafted: processing added since 19 October 2026 (photo highlights, extra groups and drop-ins, attendance across groups, certificates and levels-achieved reports, competition results and routine deductions, staff permissions including assistant coaches' read-only access to medical and SEN); SEN stated as special-category data; erasure process in section 14 (30-day deadline, request tracking, receipts, manual review of safeguarding, injury and case records, pseudonymised audit logs, acceptance records kept 6 years after closure, export before club offboarding); planned daily backups kept 30 days, once enabled; AI usage and feedback expiry. Three open Director decisions are marked in sections 8.2, 10.2 and 15.2
29 October 20261.4Approved by the Director and Privacy Lead and published, effective 29 October 2026. Approval line names The Gymnast Portal Ltd. Decisions on Google terms (10.2), subprocessor notice (8.2) and audits (15.2) confirmed; backups now enabled (daily, kept 30 days).

The detailed internal change record is kept in TGP’s change register.

Approved by The Gymnast Portal Ltd (Neil Walker, Director and Privacy Lead).