Data 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 Companies Registration No. 91644453 - VAT 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. The definitive publication, international application, current suppliers, technical set-up and country-specific rules should be periodically reviewed by legal counsel.

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

Data Processing Agreement and Security Policy TablePlay

Page 2 of 10

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

Article 2 - Applicability and formation This agreement applies to the extent that TablePlay processes personal data on the instructions and on behalf of the Customer and forms an integral part of the principal agreement. It comes into existence through electronic acceptance, signature or actual use of the Service. For processing in respect of which TablePlay independently determines the purposes and means, TablePlay is controller and the Privacy Statement applies. In the event of any inconsistency concerning processing on behalf of the Customer, this Data 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 continues for the duration of the principal agreement and for a limited period thereafter for deletion, return, back-up rotation, statutory 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 restaurant and table. • Starting and running 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. • Deletion or anonymisation after retention periods.

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

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.

Data 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 category, 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 principal agreement, this Data Processing Agreement, customer portal settings and lawful support requests constitute instructions. TablePlay shall not process data for other purposes, save for statutory obligations, its own independent security and legal protection purposes, or processing after adequate anonymisation. If an instruction is suspected to be unlawful, TablePlay shall inform the Customer, unless this is prohibited by law, and may suspend performance. Additional extensive instructions may be invoiced separately.

Article 8 - Obligations of the Client The Client warrants 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 given access only to the extent necessary, are bound by confidentiality and process only in accordance with instructions. This obligation shall remain in force after termination. Disclosure to third parties shall only take place on the basis of this agreement, the principal agreement or the law.

Article 10 - Security TablePlay shall take 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 Annex 2 and may be adjusted provided that the general 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 it has become aware of a breach of personal data being processed on behalf of the Client. Where possible, the nature, systems, categories of data and data subjects affected, consequences, measures and contact information shall be provided. Information may be provided in phases. TablePlay shall investigate, mitigate, retain relevant evidence and carry out remediation. The Client shall assess the statutory notification obligation and TablePlay shall provide reasonable support. A notification does not constitute an admission of liability. Work carried out due to circumstances within the Client's responsibility may be carried out at reasonable cost.

Article 12 - Requests from data subjects Direct requests concerning the Client's role shall in principle be forwarded. TablePlay shall only respond independently on instruction, in its own role or in the event of a statutory obligation. TablePlay shall provide reasonable support with access, correction, 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 it relates to the requester.

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

Article 14 - Sub-processors The Client grants general authorisation for the sub-processors listed in Annex 1. TablePlay may add, replace or remove these and shall maintain an up-to-date electronic list. In the event of a new material sub-processor, TablePlay shall in principle inform the Client thirty days in advance. The Client may raise a reasoned objection within that period on specific data protection grounds. The parties shall seek additional safeguards, restriction 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 that the GDPR so provides.

Article 15 - International transfers Personal data shall, where possible, be processed within a European region. Sub-processors or group companies may be established outside the EEA or have access from outside the EEA. 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 only provide data to competent authorities in the event of a lawful obligation. Where permitted, the Client shall be informed in advance. TablePlay shall assess competence, scope and legal validity and shall limit disclosure where possible.

Article 17 - Audits and Information TablePlay shall make available reasonable information, including security documentation, audits, certifications, questionnaires or assurance statements. Where 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 obligations, without damage to security, confidentiality or other clients. The Client shall bear the costs unless a material attributable breach is established. TablePlay may withhold source code, other client data, vulnerability details and commercially sensitive information where a sufficient alternative exists.

Article 18 - Return and Deletion Following termination, TablePlay shall delete or return, at the Client's discretion and to the extent technically and legally possible, data that is processed solely 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 legal basis, insufficient information, unlawful use of Game Data or the input of prohibited sensitive data, to the extent 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 to the extent required by their nature.

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

Annex 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 where configured; core sub-processor

Vercel

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

Twilio SendGrid

Transactional and operational email Name, email address, account information, content and International; email delivery statusemail sub-processor

OpenAI / other AI provider Only where AI features are activated

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

Stripe

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

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 r

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

Annex 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. • Restricted 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 anomalous 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. Secure development and supplier 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 suppliers, 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 retention periods. • Internal escalation process, investigation, registration, breach notification assessment and remedial measures.

Part B - Security and Coordinated Vulnerability Disclosure 1. Purpose and reporting address TablePlay attaches importance to the security of website, Platform, infrastructure and data. Possible technical vulnerabilities can be reported confidentially via support@tableplay.online with the subject 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, if applicable, a proposal for secure communication.

3. Permitted actions • Only actions that are necessary to establish the existence. • Keep impact and data access as limited as possible. • Do not alter, delete or download data of third parties. • Do not affect availability and stop as soon as sufficient evidence exists. • Investigate only 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 suppliers without their consent. • Burdensome automated scans. • Disclosure before reasonable investigation and remediation time has been provided. • Extortion or coercing payment through threats.

5. Response and disclosure TablePlay aims to confirm receipt within five working days, to assess the report, to ask questions where necessary, to inform the reporter on the main points and to remediate a verified vulnerability as soon as reasonably possible. The remediation time depends on severity, complexity, suppliers and necessary testing. TablePlay does not guarantee a fixed time limit. Details will not be disclosed before TablePlay agrees, a reasonable date has been agreed, 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, engagement or publicity. TablePlay may, at its own discretion, provide an acknowledgement 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 undertaking does not apply in cases of evidently 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 at /.well-known/security.txt a technical file containing reporting address, policy link, languages, expiry date and, where applicable, an encryption key. This file must be checked and renewed periodically.

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 group 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 element 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 conformity. Possible limitations concern real-time game elements, 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 text for informative images. • No essential information conveyed solely through colour. • Comprehensible error messages and consistent navigation. • Clear buttons and links. • Support for common browsers and screen sizes. • Limitation of unnecessary animation. • Comprehensible 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 alongside 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 customer The Customer 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 shall be placed so as to be accessible and visible, and where reasonably possible an alternative shall be offered to Guests who are unable to scan independently.

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

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

8. Contact TablePlay by Jimani - Jimani B.V. - Albert Plesmanweg 122 - 4462 GC Goes - The Netherlands - Company Registration No. 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 Security Policy of TablePlay. The current list may change where 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 where AI functions are activated. Possible data: limited data necessary for the function. Region / role: dependent on configuration; potential sub-processor. TablePlay does not provide identifiable guest data to any AI supplier for general model training, unless this is later expressly, lawfully, and transparently arranged otherwise.

Supplier: Stripe Service: payments, invoicing, and fraud prevention. Possible data: business data, invoices, transactions, and payment status. Region / role: international; role varies 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.