Processing Agreement and Security Policy TablePlay Including sub-processor list, technical and organisational measures, responsible disclosure and accessibility statement

TablePlay by Jimani Jimani B.V. Albert Plesmanweg 122, 4462 GC Goes KvK 91644453 - Btw NL865722729B01 support@tableplay.online

Version 1.0 Last updated: 10 July 2026

Legal review note This document has been prepared for business use by TablePlay. Have the final publication, international application, current suppliers, technical setup and country-specific rules periodically reviewed by legal counsel.

Table of Contents Part A - Processing Agreement Annex 1 - Sub-processors Annex 2 - Technical and organisational measures Part B - Security and Coordinated Vulnerability Disclosure Part C - Accessibility Statement

Processing Agreement and Security Policy TablePlay

Page 2 of 10

Part A - Processing Agreement Article 1 - Parties This processing agreement applies between the business customer of TablePlay as Controller and Jimani B.V., trading under the name TablePlay by Jimani, Albert Plesmanweg 122, 4462 GC Goes, KvK 91644453, as Processor. The parties are jointly referred to as the Parties.

Article 2 - Applicability and formation This agreement applies insofar as TablePlay processes personal data on the instructions of and for the benefit of the Customer and forms an integral part of the main agreement. It comes into being through electronic acceptance, signature, or actual use of the Service. For processing operations for which TablePlay independently determines the purposes and means, TablePlay is the controller and the Privacy Statement applies. In the event of a conflict regarding processing on behalf of the Customer, this Processing Agreement shall prevail over the General Terms and Conditions.

Article 3 - Subject matter, duration and nature TablePlay processes personal data for restaurant-related game, table, QR, score, leaderboard, dashboard, and support functionalities. The processing lasts for the duration of the main agreement and a limited period thereafter for deletion, return, backup rotation, legal obligations, and legal protection. The processing may include collecting, recording, organising, structuring, storing, consulting, calculating, combining within the restaurant context, displaying, transmitting, restricting, deleting, and anonymising.

Article 4 - Purposes • Linking QR codes to a restaurant and table. • Starting and conducting game sessions. • Processing temporary nicknames, game choices, answers, scores, and results. • Facilitating table-versus-table games and temporary leaderboards. • Displaying restaurant-related statistics. • Preventing duplicate, fraudulent, or technically invalid sessions. • Technical support, security, continuity, and recovery. • Deleting or anonymising after retention periods.

Article 5 - Categories of data subjects • Guests and players of the Customer. • Contact persons, users, employees, and auxiliary staff of the Customer. • Persons appearing in a support ticket.

Article 6 - Categories of personal data • Temporary nickname, table number or unique table ID, and restaurant or location ID. • Game session ID, selected game, game mode, answers, actions, score, result, and ranking. • Date, time, and temporary language setting. • Technical session, IP, browser, and device data insofar as present in security logs.

Processing Agreement and Security Policy TablePlay

Page 3 of 10 • Name and business e-mail address of a contact person and content of support enquiries. • Other data entered within the agreed functionality. TablePlay is not intended for special categories of data, criminal, medical, or biometric data or extensive directly identifiable guest profiles. The Customer shall not instruct such processing without a prior written agreement.

Article 7 - Documented instructions The main agreement, this Processing Agreement, customer portal settings, and lawful support requests shall constitute instructions. TablePlay does not process data for other purposes, except for legal obligations, its own independent security and legal protection purposes, or processing after adequate anonymisation. In the event of a suspected unlawful instruction, TablePlay shall inform the Customer, unless prohibited by law, and may suspend performance. Additional extensive instructions may be invoiced separately.

Article 8 - Obligations of the Client The Client is responsible for lawfulness, valid legal basis, information to Guests, lawful instructions, data minimisation, internal security and protection of login credentials. The Client is responsible for accuracy and quality, does not require real names from Guests and does not use Game Data for individual marketing or profiling without an independent legal basis. Security incidents and unlawful instructions shall be reported without delay.

Article 9 - Confidentiality Persons under the authority of TablePlay are granted access only to the extent necessary, are bound by confidentiality obligations and process only in accordance with instructions. This obligation shall remain in force after termination. Disclosure to third parties shall take place solely on the basis of this agreement, the principal agreement or the law.

Article 10 - Security TablePlay shall implement appropriate technical and organisational measures, having regard to the state of the art, costs, nature, scope, context, purpose and risk. The measures are set out in Schedule 2 and may be amended provided the overall level of protection is not materially reduced. No system can guarantee absolute security.

Article 11 - Data Breaches TablePlay shall inform the Client without undue delay after becoming aware of a breach of personal data processed on behalf of the Client. Where possible, the nature, systems, categories of data and data subjects, consequences, measures and contact information shall be provided. Information may be provided in phases. TablePlay shall investigate, limit, retain relevant evidence and carry out remediation. The Client shall assess the statutory notification obligation and TablePlay shall provide reasonable assistance. A notification does not constitute an admission of liability. Work required as a result of circumstances under the responsibility of the Client may be carried out at reasonable cost.

Article 12 - Requests from Data Subjects Direct requests concerning the role of the Client shall in principle be forwarded. TablePlay shall respond independently only on instruction, in its own role or where required by law. TablePlay shall provide reasonable assistance with access, rectification, erasure, restriction, portability and objection.

Data Processing Agreement and Security Policy TablePlay

Page 4 of 10

Because Guests do not have an Account, identification may be limited. Restaurant, table, date, time, nickname and game context may be required. Data shall not be provided if it is not sufficiently established that they relate to the requester.

Article 13 - Support with Compliance TablePlay shall provide reasonable assistance with security, data breach assessments, data protection impact assessments, prior consultation and necessary documentation. Extensive assistance beyond the standard service may be invoiced, unless it results from a default of TablePlay.

Article 14 - Sub-processors The Client grants general authorisation for the sub-processors listed in Schedule 1. TablePlay may add, replace or remove such sub-processors and shall maintain a current electronic list. In the event of a new material sub-processor, TablePlay shall in principle provide notice thirty days in advance. The Client may, within that period, raise a reasoned objection on specific data protection grounds. The parties shall seek additional safeguards, limitation or a technical alternative. If no reasonable solution exists, the Client may terminate the directly affected part prior to deployment. TablePlay shall impose substantially equivalent obligations and shall remain responsible to the extent required by the GDPR.

Article 15 - International Transfer Personal data shall, where possible, be processed within a European region. Sub-processors or group companies may be located outside the EEA or have access thereto. Where required, TablePlay shall use adequacy decisions, standard contractual clauses, additional measures or other valid mechanisms. Upon reasonable request, information shall be provided with due regard to confidentiality.

Article 16 - Requests from Authorities TablePlay shall disclose data only to competent authorities where subject to a lawful obligation. Where permitted, the Client shall be informed in advance. TablePlay shall assess authority, scope and legal validity and shall limit disclosure where possible.

Article 17 - Audits and Information TablePlay shall make reasonable information available, including security documentation, audits, certifications, questionnaires or assurance statements. If this is insufficient, the Client may request an audit no more than once per calendar year, with thirty days' notice, during office hours, by an independent expert bound by confidentiality, without causing damage to security, confidentiality or other clients. The Client shall bear the costs unless a material attributable breach is established. TablePlay may shield source code, other client data, vulnerability details and commercially sensitive information where a sufficient alternative exists.

Article 18 - Return and Deletion After termination, TablePlay shall delete or return, at the Client's choice and insofar as technically and legally possible, data that is processed exclusively on behalf of the Client. The choice shall be communicated no later than within thirty days. In the absence of a choice, TablePlay may delete or anonymise in accordance with the standard policy. Back-ups may contain data for a maximum of one month and shall be used solely for restoration purposes.

TablePlay Data Processing Agreement and Security Policy

Page 5 of 10

Data that is legally required to be retained, necessary for legal protection, or anonymised need not be deleted.

Article 19 - Liability The liability provisions of the General Terms and Conditions shall also apply. Each party is responsible for its own privacy obligations. The Client shall indemnify TablePlay against claims arising from unlawful instructions, absence of a lawful basis, insufficient information, unlawful use of Game Data or the entry of prohibited sensitive data, insofar as permitted by law.

Article 20 - Term and Termination This Data Processing Agreement shall end when TablePlay no longer processes personal data on behalf of the Client. Confidentiality, security, deletion, liability and audits shall remain in effect insofar as their nature so requires.

Article 21 - Governing Law and Disputes This Data Processing Agreement shall be governed by the laws of the Netherlands. Disputes shall be handled in accordance with the General Terms and Conditions.

Appendix 1 - Sub-processors Supplier

Service

Possible Data

Region / Role

Supabase

Database, authentication, storage and backend Accounts, table data, nicknames, sessions, scores Primary and logs EU region insofar as configured; core sub-processor

Vercel

Hosting, runtime, content delivery and IP address, logging request, browser, device and application data EEA and possibly the US; hosting sub-processor

Twilio SendGrid

Transactional and operational e-mail Name, e-mail address, account information, content and International; delivery statuse-mail sub-processor

OpenAI / other AI supplier Only when AI functions are activated

Limited data necessary for the function Depending on configuration; potential sub-processor

Stripe

Business data, invoices, transactions and payment status International; role varies per processing operation

Payments, invoicing and fraud

Google / Meta / LinkedIn Analytics and marketing following consent Website, device, advertising and conversion data International; generally not a sub-processor for re

The current list is made available via the website or the client portal. In the case of a material new sub-processor, the notification and objection procedure set out in Article 14 shall apply. TablePlay shall not provide any identifiable guest data to an AI supplier for general model training, unless this is later explicitly, lawfully and transparently arranged otherwise.

Appendix 2 - Technical and Organisational Measures 1. Access Security • Unique user accounts and secure authentication. • Hashed passwords and restriction of administrative rights. • Access based on role and necessity. • Revocation of access when no longer required. • Additional authentication measures where appropriate.

2. Logical Data Separation • Separation between business Accounts and tenant-bound authorisation.

TablePlay Data Processing Agreement and Security Policy

Page 6 of 10 • Supabase Row Level Security where technically applicable. • Restriction of access to other Clients' data. • Unique table identifiers.

3. Transport and Storage • HTTPS- and TLS-secured connections. • Secure communication between browser, application, backend and APIs. • Storage with selected cloud providers. • Limited employee access and contractual confidentiality. • No storage of passwords in directly readable form.

4. Availability, Logging and Recovery • Back-ups and recovery facilities where appropriate. • Monitoring of technical errors and relevant login attempts. • Detection and investigation of abnormal use. • Back-ups in principle for a maximum of one month. • Logs in principle for a maximum of one year, unless longer retention is required for an incident or dispute.

5. Secured Development and Vendor Management • Version control, code review and controlled deployment where appropriate. • Restriction of secrets and keys in source code. • Timely updates of relevant components. • Assessment and remediation of reported vulnerabilities. • Selection of professional vendors, contractual arrangements and transfer mechanisms.

6. Data Minimisation and Incident Management • No mandatory real names, email or telephone number for Guests. • Temporary nicknames and limited leaderboard visibility. • Deletion or anonymisation after specified periods. • Internal escalation process, investigation, registration, assessment of notification obligations and remedial measures.

Part B - Security and Coordinated Vulnerability Disclosure 1. Purpose and Reporting Address TablePlay attaches importance to the security of the website, Platform, infrastructure and data. Possible technical vulnerabilities can be reported confidentially via support@tableplay.online with the subject line Security Report - confidential.

2. Content of a Report • Clear description of the vulnerability. • Domain, endpoint, screen or system involved.

Data Processing Agreement and Security Policy TablePlay

Page 7 of 10 • Reproducible steps and possible impact. • Limited screenshots or technical evidence. • Browser, device or environment used. • Contact details and, where applicable, a proposal for secure communication.

3. Permitted Actions • Only actions necessary to establish the existence [of the vulnerability]. • Keep impact and data access as limited as possible. • Do not alter, delete or download data belonging to third parties. • Do not affect availability and stop as soon as sufficient evidence exists. • Only investigate systems that are demonstrably under the control of TablePlay.

4. Prohibited Actions • Social engineering, phishing, physical attacks, brute force and credential stuffing. • Account takeovers, denial-of-service, malware or persistent access. • Altering, erasing, copying or disclosing data. • Actual manipulation of payments, invoices, coupons or scores. • Investigation of external vendors without their consent. • Burdensome automated scans. • Disclosure before a reasonable period for investigation and remediation has been provided. • Extortion or coercion of payment by means of threats.

5. Response and Disclosure TablePlay endeavours to confirm receipt within five working days, to assess the report, to ask questions where necessary, to keep the reporting party informed in general terms, and to remediate a verified vulnerability as soon as reasonably possible. The remediation period depends on severity, complexity, vendors and necessary testing. TablePlay does not guarantee a fixed period. Details will not be disclosed publicly until TablePlay has agreed, a reasonable date has been agreed upon, or at least ninety days have elapsed without a reasonable substantive response or remediation attempt. Personal data, authentication data and exploit code will not be published.

6. No General Bug Bounty and Legal Approach TablePlay does not operate a general bug bounty programme and a report does not confer any right to payment, assignment or publicity. TablePlay may, at its own discretion, provide a token of appreciation. TablePlay will, in principle, not take legal action against a researcher who acts in good faith, within this policy, without causing damage, confidentially and without extortion. This commitment does not apply in cases of manifestly criminal, harmful, fraudulent or disproportionate actions and does not bind third parties or authorities.

Data Processing Agreement and Security Policy TablePlay

Page 8 of 10

7. security.txt TablePlay may publish a technical file at /.well-known/security.txt containing the reporting address, policy link, languages, expiry date and, where applicable, an encryption key. This file must be periodically checked and renewed.

Part C - Accessibility Statement 1. Ambition and Reference Framework TablePlay strives to make the website, registration, customer portal and guest games usable for a broad range of users, including persons with visual, auditory, motor or cognitive impairments. Where reasonably possible, the principles of WCAG 2.2 level AA are used as a technical and substantive reference framework. This does not constitute a guarantee that every component is fully compliant under all circumstances.

2. Current Status The full environment has not yet been independently and comprehensively audited. TablePlay therefore does not currently claim full formal WCAG 2.2 AA compliance. Possible limitations concern real-time game components, time pressure, drag-and-drop, animations, external payment or authentication pages, translations, older colour displays and touch-oriented functions.

3. Measures • Semantic HTML and usable labels where appropriate. • Keyboard operability of essential functions and visible focus. • Sufficient contrast and scalable text. • Alternative texts for informative images. • No essential information conveyed by colour alone. • Understandable error messages and consistent navigation. • Clear buttons and links. • Support for common browsers and screen sizes. • Limitation of unnecessary animation. • Understandable language in the guest environment. • Automated and manual testing where possible.

4. Games and time pressure Some games are by their nature time-bound. Where technically and content-wise possible, TablePlay may offer alternative play modes, extended time limits, less movement, visual alternatives for sound and text or symbols in addition to colour. Not every game mode is equally suitable for every user. Restaurants are encouraged to offer multiple game types.

Data Processing Agreement and Security Policy TablePlay

Page 9 of 10

5. Responsibility of the business Client The Client remains responsible for the physical and operational accessibility of the Location, including placement of QR codes, legibility of printed materials, alternative assistance, accessibility of screens, support by staff and own content. QR codes are placed in a reachable and visible manner and, where reasonably possible, an alternative is offered to Guests who are unable to scan independently.

6. Reporting and alternative access Accessibility issues can be reported via support@tableplay.online stating the page or game, device, browser, assistive technology, description and desired solution. TablePlay aims to acknowledge receipt within five business days and to provide a substantive response within a reasonable period. Where possible, information may be offered by e-mail, support, an alternative instruction, manual processing or another game option.

7. Disproportionate burden and improvement An adjustment may be postponed where it is technically not feasible, materially compromises security, alters the fundamental nature of a game, is dependent on an external supplier or constitutes a disproportionate organisational or financial burden. TablePlay will then assess an alternative. TablePlay may take accessibility into account in design, testing, prioritisation, user feedback and external audits and update this statement.

8. Contact TablePlay by Jimani - Jimani B.V. - Albert Plesmanweg 122 - 4462 GC Goes - The Netherlands - Companies Registry (KvK) 91644453 - VAT NL865722729B01 - support@tableplay.online.

Data Processing Agreement and Security Policy TablePlay

Page 10 of 10

Additional Sub-processor List This sub-processor list forms part of the Data Processing Agreement and the Security Policy of TablePlay. The current list may change when suppliers, regions or functions change.

Supplier: Supabase Service: database, authentication, storage and backend. Possible data: accounts, table data, nicknames, sessions, scores and logs. Region / role: primarily EU region insofar as configured; core sub-processor.

Supplier: Vercel Service: hosting, runtime, content delivery and logging. Possible data: IP address, request, browser, device and application data. Region / role: EEA and possibly USA; hosting sub-processor.

Supplier: Twilio SendGrid Service: transactional and operational e-mail. Possible data: name, e-mail address, account information, content and delivery status. Region / role: international; e-mail sub-processor.

Supplier: OpenAI / other AI supplier Service: only when AI functions are activated. Possible data: limited data necessary for the function. Region / role: depending on configuration; potential sub-processor. TablePlay does not provide identifiable guest data to an AI supplier for general model training, unless this is later explicitly, lawfully and transparently arranged otherwise.

Supplier: Stripe Service: payments, invoicing and fraud. Possible data: business data, invoices, transactions and payment status. Region / role: international; role differs per processing activity.

Supplier: Google / Meta / LinkedIn Service: analytics and marketing following consent. Possible data: website, device, advertising and conversion data. Region / role: international; generally not a sub-processor for restaurant game data.