Notice
Privacy notice, trademark disclaimer, and legal terms
This page is the full legal text for the unofficial World Cup 2026 generative match-centre case study. It explains what personal data is processed when you use the chat, who receives it, and that this site is not an official FIFA product.
Last updated 16 September 2026. Effective date 16 September 2026.
1. Introduction
This Privacy and Legal Notice (“Notice”) describes how this website (the “Site”) processes information when you visit the generative match centre, send a chat message, select teams, players, or matches, or open the export view. It also records the trademark, warranty, and liability terms that apply to this unofficial case study.
By using the Site you acknowledge this Notice. If you do not agree, do not use the chat and do not send messages to the Site. This Notice is provided for transparency around a public product-design experiment. It is not legal advice and does not create an attorney–client relationship.
2. Who is the controller
For the purposes of applicable data-protection law, including the EU and UK GDPR where they apply, the controller of personal data processed through this instance of the Site is the publisher of the case study, Agustín Burgos López (“we”, “us”, “our”).
This is a personal, unofficial experiment. It is not operated by FIFA, a FIFA member association, a World Cup organising committee, ESPN, Groq, or any official tournament broadcaster. Contact details are in section 20.
3. What this site is
The Site is an unofficial generative-UI case study. You can ask questions in plain language about World Cup 2026 fixtures, groups, knockout rounds, squads, and related football topics. The interface composes designed product widgets. Match facts are loaded from a public ESPN soccer feed. A language model may classify your question and write a short grounded reply.
The Site is provided for demonstration, portfolio, research, and educational purposes only. It is not a consumer product, not an official results service, and not a source of betting or editorial advice. Scores, line-ups, and news may be incomplete, delayed, or wrong.
4. Personal data we process
We do not require an account, email address, or profile. We do not ask you to identify yourself. Depending on how you use the Site, the following categories of data may still be personal data:
- Chat content. The text you type, suggested prompts you click, and the conversation history sent with later turns so the assistant can resolve follow-up questions.
- In-session picks. Teams, favourite players, and up to three matches you select in the chat. These live in browser session state for this visit. They are not written to a first-party database.
- Technical and log data. Internet protocol (IP) address, date and time of the request, requested URL, user-agent string, and similar HTTP metadata necessarily processed to deliver the Site, call third-party APIs, and keep the service available.
- Derived data. Intent labels, team or player names extracted from your question, and compact match facts assembled so the language model can write a reply without inventing scores.
Do not submit special-category data, passwords, payment details, or information about other people. The chat is not a confidential channel.
5. How we use personal data
We use the data described above only to:
- receive your question and stream a reply in the match-centre interface;
- classify the question onto fixtures, groups, teams, news, or a text-only answer;
- query the ESPN soccer feed for the widgets that answer the question;
- ask a language-model provider to classify intent and write a short commentary;
- remember your picks until you reset the chat, reload, or leave the session;
- operate, debug, and protect the Site, including diagnosing failed streams.
We do not use chat content to build marketing profiles, serve third-party advertising, sell data, or train a first-party model. We cannot control whether a third-party processor uses prompts under that processor’s own terms.
6. Legal bases
Where the GDPR or UK GDPR applies, we process personal data on these bases:
- Legitimate interests (Article 6(1)(f)): operating a public case study, answering the questions you send, securing the Site, and keeping logs needed to run HTTP services. We have balanced those interests against your right to visit a demo without creating an account.
- Consent (Article 6(1)(a)), where you choose to type a message or click a prompt. You can stop at any time by not sending further messages and by using New chat or closing the browser.
You are not obliged to provide chat content. If you do not send a message, we do not process conversation text.
8. Recipients and third parties
We do not sell personal data. The following categories of recipient may process data as independent controllers or as processors, depending on their role:
- Groq, Inc. If an API key is configured, chat history, compact ESPN facts, and related prompts are sent to Groq’s API so a model can classify the question and write a short reply. Groq processes that content under its own Privacy Policy and product terms. If no key is configured, classification falls back to local catalog and pattern matching and Groq is not called.
- ESPN / The Walt Disney Company group. The Site queries the public ESPN soccer API (
site.api.espn.com, leaguefifa.world) with request parameters such as date windows, team names, and event identifiers. We do not forward your raw chat transcript to ESPN. ESPN may still receive your IP address and standard request metadata. See ESPN’s Privacy Policy. - Google LLC. Font files are requested from Google Fonts, as described in section 7.
- Hosting and network providers. Whoever hosts or transmits this instance (including local development on your machine, a platform-as-a-service host, a CDN, or a reverse proxy) may process IP addresses and request logs under that provider’s terms.
9. International transfers
Groq, ESPN, Google, and many hosting providers are established in, or operate infrastructure in, the United States and other countries outside your country of residence. If you access the Site from the EEA, UK, or Switzerland, your personal data may be transferred to those countries. Those transfers, where they occur, rely on the third party’s published transfer tools (for example Standard Contractual Clauses) and on the fact that you chose to use a public internet demo that calls those services.
10. Retention
We do not operate a first-party user database for this case study. Chat messages and picks are kept in your browser session until you reset, reload, or leave. Server-side, a request exists for as long as it takes to classify the question, fetch ESPN data if needed, call Groq if configured, and stream the reply. We do not intend to store conversation archives after the response is sent.
Third parties retain data under their own policies. Host access logs, if enabled by the environment that serves this instance, are kept only as long as that environment’s default logging requires. If you need a processor to delete data they hold, you must also use that processor’s own request channels.
11. Your rights
Depending on where you live, you may have the right to request access, rectification, erasure, restriction, objection, and portability, and the right to withdraw consent. Because this demo does not keep a user account, the practical way to erase first-party chat and picks is to use New chat or close the site.
To exercise rights against us, use the contact route in section 20. We may need enough information to locate a request in logs, if any exist. You may also lodge a complaint with your local supervisory authority. In the EEA that is your national data-protection authority; in the UK, the Information Commissioner’s Office.
12. Children
The Site is a technical case study aimed at adults working in design, engineering, and product. It is not directed at children under 16. We do not knowingly collect personal data from children. If you believe a child has submitted personal data through the chat, contact us and we will delete any first-party copy we still control.
13. Security
We use ordinary web security measures appropriate to a small public demo, including transport encryption when the host provides HTTPS, typed request validation, and no first-party account store. No method of transmission or storage is completely secure. Do not send secrets, health information, or anything you would not want a language-model provider or HTTP log to see.
14. Trademarks and FIFA disclaimer
FIFA, the FIFA logo, FIFA World Cup, FIFA World Cup 2026, World Cup, the FIFA World Cup trophy, related emblems, mascots, look-and-feel, and all related names, marks, and trade dress are trademarks, service marks, or registered trademarks of Fédération Internationale de Football Association (FIFA) or its affiliates (collectively, “FIFA Marks”). Other names, including national-team names, club names, ESPN, Groq, and product names, are trademarks of their respective owners.
This Site is an unofficial case study. It is not affiliated with, associated with, authorised by, endorsed by, or sponsored by FIFA, any FIFA member association, any 2026 host organising committee, or any official broadcast partner. Nothing on the Site should be read as an official FIFA communication, ticket offer, hospitality programme, or licensed product.
Use of FIFA Marks, tournament imagery, and a community-inspired visual language is solely for nominative and descriptive reference to the 2026 tournament in a design and engineering experiment. No licence is granted to you to copy, sell, or commercially exploit FIFA Marks. If FIFA or another rights holder asks us to change or remove material, we will review that request promptly.
15. Third-party scores and content
Fixtures, scores, standings, squads, kits, venues, and headlines are requested from a public ESPN soccer feed and then normalised before they reach the interface. ESPN is not a partner of this case study. ESPN content remains subject to ESPN’s terms. The language model is instructed not to invent scores; if the feed is empty, delayed, or a request fails, the Site may show an empty state or a fallback message rather than official FIFA statistics.
News headlines, player names, and match events are reproduced for the limited purpose of demonstrating generative UI. They may be incomplete. They are not our editorial content and are not an official World Cup report.
16. Design and content credits
The visual language is inspired by the community FIFA World Cup 2026 Figma kit (CC BY 4.0, Cammy Hogg). This Site does not use FIFA’s proprietary FWC2026 event typeface. The kit author’s licence is not a FIFA endorsement. Fonts are provided by Google Fonts as described above.
17. Disclaimer of warranties
THE SITE IS PROVIDED “AS IS” AND “AS AVAILABLE”, WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. We do not warrant that scores are official, that the language model will classify every question correctly, that the service will be uninterrupted or error-free, or that the Site is appropriate for betting, journalism, or safety-critical use.
Some jurisdictions do not allow certain warranty exclusions. In those places, the exclusions apply to the maximum extent permitted by law. Nothing in this Notice limits non-waivable consumer rights.
18. Limitation of liability
To the maximum extent permitted by applicable law, we are not liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of data, profits, goodwill, or other intangible losses, arising out of or related to your use of the Site, third-party APIs, trademark references, or reliance on scores or commentary shown in the interface.
Our aggregate liability for claims relating to the Site will not exceed fifty euros (EUR 50) or the amount you paid us to use the Site in the twelve months before the claim, whichever is greater. You have not paid us to use this case study. These limits do not apply to liability that cannot be limited under applicable law, including liability for death or personal injury caused by negligence, or for fraud.
19. Changes to this notice
We may update this Notice when the case study changes — for example if we add analytics, accounts, a new model provider, or a different host. The “Last updated” date at the top of this page will change. The revised Notice applies from that date. Continued use of the Site after an update constitutes acknowledgement of the revised text.
20. Contact
For privacy requests, trademark complaints, or questions about this Notice, contact Agustín Burgos through the contact form on agustinburgos.com. Please mention “Privacy” or “Legal” in your message so the request can be routed.
If you are FIFA or another rights holder and believe this case study infringes your rights, use the same contact form. We will review good-faith notices and, where appropriate, modify or remove material.