Accessibility / Code of Conduct

GETC 2027 — ACCESSIBILITY / CODE OF CONDUCT

Working draft for external legal review — not for publication in this form Applies to: GETC 2027 website (getc2027.eu) and the GETC 2027 participant app Version 0.3 (working draft)

GDPR & DATA PROTECTION AT A GLANCE

An accessibility request may involve data revealing health or disability status — a "special category" of personal data under Art. 9 of Regulation (EU) 2016/679 (GDPR). Such data is processed only for the purpose of accommodating the request, on the basis of explicit consent (Art. 9(2)(a)) or another applicable Art. 9(2) condition, is shared only with the personnel who need it to arrange the accommodation, and is retained only as long as necessary. See Article 9 of the Privacy & Cookie Policy for the full provision.

ARTICLE 1 — PURPOSE AND SCOPE

1.1 This document sets out the conduct, safety, and accessibility commitments that apply to every Participant, exhibitor, speaker, sponsor, accredited media representative, volunteer, and staff member at the Congress, on the website, and within the app ("this Code"). 1.2 This Code operates alongside, and does not replace, Article 9 (Code of Conduct) of the Terms & Conditions of Attendance, the venue's own house rules, and applicable law.

ARTICLE 2 — DIGITAL ACCESSIBILITY STANDARD

2.1 The website and the app are intended to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, level AA, as the working accessibility benchmark, consistent with the requirements of Directive (EU) 2019/882 (the European Accessibility Act) as implemented in Spain, to the extent that Act applies to the Platform. 2.2 An accessibility statement will be published on the website and in the app, identifying known accessibility limitations, the standard applied, and a contact route for reporting a digital accessibility barrier, consistent with Article 7 below.

ARTICLE 3 — PHYSICAL AND ON-SITE ACCESSIBILITY

On-site accessibility (venue access, seating, signage, assistance services) is governed by the venue's own accessibility documentation, to be published once the venue is confirmed, and by applicable Spanish accessibility legislation for public and commercial buildings; this Code sets the minimum commitments GETC will require of the venue and will publish the detail once available.

ARTICLE 4 — RESPECTFUL CONDUCT AND ANTI-HARASSMENT

4.1 Anti-harassment and respectful-conduct expectations apply on-site, on the website and within the app — including networking messages, meeting requests, comments and any public profile content. 4.2 Harassment includes, without limitation: offensive comments or imagery; unwelcome attention or contact; intimidation, stalking, or following; non-consensual photography of another attendee (see the Privacy & Cookie Policy, Part III, Article 32); and discriminatory conduct related to race, gender, gender identity, sexual orientation, disability, religion, nationality, or any other protected characteristic under applicable law. 4.3 This prohibition applies equally to conduct directed at GETC staff, volunteers, and venue personnel.

ARTICLE 5 — SECURITY AND CREDENTIALS

Security and credential rules apply equally to the physical badge and to the QR Credential issued in the app. Sharing, duplicating, or misusing a Credential is a breach of this Code and of the Terms & Conditions of Attendance (Article 5.3).

ARTICLE 6 — VENUE RESTRICTIONS AND PROHIBITED ITEMS

Weapons, hazardous materials, and other dangerous or prohibited items identified in the venue's house rules may not be brought onto the venue, regardless of ticket tier or app Role Flags. Security screening may be carried out at venue entrances.

ARTICLE 7 — EMERGENCY PROCEDURES

Emergency compliance and evacuation instructions issued on-site by venue staff or security personnel take precedence over any in-app agenda or navigation guidance at all times. Emergency exits, assembly points, and accessible-evacuation provisions will be communicated on-site and, where practicable, summarised in the app.

ARTICLE 8 — ACCESSIBILITY REQUESTS

8.1 How to request. Reasonable accessibility requests (e.g. mobility assistance, sign-language interpretation, dietary requirements linked to a medical condition, accessible seating) can be made through the website contact route or the app's support/help section, ideally with reasonable advance notice ahead of the Congress, though on-site requests will also be accommodated where feasible. 8.2 How the request is handled. Requests are routed only to the personnel responsible for arranging the accommodation, in line with Article 9 of the Privacy & Cookie Policy, and are not shared more broadly than necessary. 8.3 Response. GETC will make reasonable efforts to accommodate requests submitted with reasonable advance notice, subject to venue and operational constraints, and will communicate to the requester what can and cannot be accommodated before the Congress where possible.

ARTICLE 9 — DEMONSTRATIONS, MACHINERY AND LIVE TECH

Specific safety rules apply to demonstrations, machinery, and Live Tech exhibits on the exhibition floor, published alongside exhibitor guidelines and enforced by on-site exhibition staff; exhibitors are responsible for ensuring their demonstrations comply with applicable health-and-safety law and venue requirements.

ARTICLE 10 — REPORTING A CONCERN

10.1 A person who experiences or witnesses conduct that may breach this Code can report it via the website contact route, the app's support/help section, or directly to on-site security/staff. 10.2 Reports are handled confidentially to the extent operationally possible, and personal data collected in the course of investigating a report is processed under the Privacy & Cookie Policy on the basis of GETC's legitimate interest in maintaining a safe event, or another applicable basis. 10.3 A person who makes a good-faith report under this Article will not be penalised for doing so, even if the underlying concern is not ultimately upheld.

ARTICLE 11 — CONSEQUENCES AND ESCALATION

Depending on severity, a breach of this Code may result in, in increasing order of severity: (a) a verbal warning; (b) removal from a specific session or area; (c) removal from the venue for the remainder of the Congress; (d) suspension of the app account; (e) revocation of the Credential without refund. This is in line with Article 15 (Suspension, Removal and Revocation) of the Terms & Conditions of Attendance. Serious or unlawful conduct will additionally be referred to venue security or the relevant authorities. Where operationally feasible, the person affected will be given an opportunity to be heard before a sanction beyond a verbal warning is applied.

ARTICLE 12 — GENERAL PROVISIONS

12.1 Severability. If a provision of this Code is held invalid or unenforceable, that provision is severed and the remainder continues in full force and effect. 12.2 Language. This Code is drafted in English; a Spanish version will be published for on-site use. 12.3 Governing law. This Code is governed by Spanish law, on the same jurisdiction basis as the Terms & Conditions of Attendance.

LEGAL REVIEW NOTE

This page should be finalised alongside the venue's own safety/ accessibility documentation once the venue is confirmed, and alongside the app's reporting/blocking features for networking abuse, before being published as binding rules. The digital-accessibility conformance claim in Article 2 should not be published until an actual accessibility audit of the website and app has been carried out, and the confidentiality commitment in Article 10 and the special-category-data handling referenced above should be reviewed by counsel together with the Privacy & Cookie Policy.

Source: GETC 2027 Legal Pages Master v1, section 16, expanded using standard event code-of-conduct drafting practice: a digital-accessibility standard (WCAG 2.1 AA / European Accessibility Act), a concrete accessibility-request process, a reporting/escalation route with a non-retaliation commitment, and the GDPR special-category-data cross-reference the master document flagged as needed but did not draft in full. Final sign-off from Spanish counsel is still required before publication.